Design Conditional Access around AI identity types
Separate human, service-principal, managed-identity, and preview agent policy boundaries; validate token acquisition and resource enforcement independently.
Explore the topic
Separate user, service-principal and managed-identity coverage; investigate policy outcomes without assuming universal enforcement.
Questions this collection helps you answer
Build your understanding
Separate human, service-principal, managed-identity, and preview agent policy boundaries; validate token acquisition and resource enforcement independently.
Separate user delegation from application authority, validate token boundaries, and prevent an agent from turning an authorized session into an unauthorized action.
Move from control to evidence
Use these as investigation leads. Table coverage and context determine what the results can establish.
Expand failed policy results from interactive sign-ins and retain policy IDs, user populations and sign-in outcomes for investigation.
Review sign-in outcomes for legacy client-app labels before changing authentication policy, including failures and unknown outcomes.
Compare reported authentication requirements by application and client while preserving the limits of MFA and policy interpretation.
Review successful policy creation, update and deletion with actor and raw before/after evidence instead of inferring weakening from a generic write.
Follow the connections