<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conditional Access on AlvenTech</title>
    <link>https://alven.tech/tags/conditional-access/</link>
    <description>Recent content in Conditional Access on AlvenTech</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>© 2026 Stein-Erik Alvestad</copyright>
    <lastBuildDate>Tue, 10 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://alven.tech/tags/conditional-access/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Agent 365: an approval lifecycle for agents in Entra Agent ID</title>
      <link>https://alven.tech/posts/2026-11-10-agent365-approval-lifecycle/</link>
      <pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://alven.tech/posts/2026-11-10-agent365-approval-lifecycle/</guid>
      <description>Conditional Access for agents only has one grant: Block, so the pattern is an allow-list driven by a custom security attribute. Microsoft documents the mechanism. What I couldn&amp;rsquo;t find was the lifecycle around it: who moves an agent from New to IT_Approved, what takes it back, and how it relates to the other approvals and lifecycle features in Entra and Agent 365. Here&amp;rsquo;s the map I drew, the approval lifecycle behind the attribute, and how I built it in my lab.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://alven.tech/posts/2026-11-10-agent365-approval-lifecycle/feature.webp" />
    </item>
    
  </channel>
</rss>
