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
Trace delegated authority, token audiences, privileged access and federation trust.
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.
Design PIM activation, resource scope, approval evidence, and emergency recovery around the permissions that can change models, data, identities, and telemetry.
Design issuer, subject, audience, and resource-permission boundaries so secretless deployment and runtime identities remain narrowly authorized.
Move from control to evidence
Use these as investigation leads. Table coverage and context determine what the results can establish.
Keep home and resource tenant identifiers alongside the recorded cross-tenant access type when reviewing external access.
Join credential additions to later successful sign-ins by directory and service-principal object ID without claiming the new credential was used.
Separate direct, eligible, scoped and completed PIM role changes while retaining the full target payload for authoritative interpretation.
Follow the connections