Conditional Access Framework (2026.6.1)
I few weeks ago (June 11th), I have launched an updated version of my Conditional Access Framework. Version 2026.6.1 includes one updated policy and multiple new policies designed specifically for Agents. Consequently, a completely new persona has been created, which currently holds only one policy.
Note: The complete framework, with downloadable policies and instructions on how to import these can be found in my Github.
Table of Contents
Changelog
- CA100/CA105: Admin persona’s have been updated to include additional administrator roles: Agent ID Administrator, Agent Registry Administrator, AI Administrator, Entra Backup admin, Windows 365 Administrator, Microsoft 365 Backup Admin, Dragon Admin
- CA502: New Conditional Access policy introduced to block all agent identities, except those explicitly excluded.
- CA503: New Conditional Access policy introduced to require agent user identities to access resources only from compliant devices.
- CA504: New Conditional Access policy introduced to block all risky agent user identities with a medium or high risk level.
- CA505: New Conditional Access policy introduced to block agent user sessions from all locations except Global Secure Access Network.
Persona’s
Global
Global is a persona/placeholder for policies that are general in nature or do not only apply to one persona. So it is used to define policies that apply to all personas or don’t apply to one specific persona. The reason for having this persona is to be able to have a model where we can protect all relevant scenarios. It should be used to hold policies that apply to all users or policies that enforce protection on scenarios not covered by policies for other personas
Admins
We define admins in this context as any non-guest identity (cloud or synced) that have any Azure AD or other Microsoft 365 admin Role (like in MDCA, Exchange, Defender for Endpoints or Compliance). As guests who have such roles are covered in a separate persona, guests are excluded from this persona.
Internals
Internals cover all users who have an AD account synced to Azure AD who are employees of the company and work in a standard end-user role.
Guests
Guests holds all users who have an Azure AD guest account that has been invited into the customer tenant
Agents
Agents covers all agent related resources which can be managed through Conditional Access
Conditional Access policies
The entire baseline documentation, screenshots, and implementation steps are available in the GitHub Repository: https://github.com/j0eyv/ConditionalAccessBaseline
Caution: Be careful activating the policies! Make sure you have decent exclusions and/or a break the glass account in place. Enable the policies one by one or start with report-only.
Written by Joey Verlinden
Back to all articles