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
Constrain federation, credential lifetime, resource scope and the behavior of nonhuman principals.
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.
Design issuer, subject, audience, and resource-permission boundaries so secretless deployment and runtime identities remain narrowly authorized.
Choose the right Foundry identity and role, remove credential fallbacks, and test the boundaries of keyless access.
Move from control to evidence
Use these as investigation leads. Table coverage and context determine what the results can establish.
Compare successful application sign-ins with a separate 14-day source-IP baseline, excluding principals without previous history.
Compare managed-identity token activity with prior resource relationships while keeping workload attachment and downstream authorization as separate evidence.
Compare successful workload resource identifiers against a prior baseline without treating token issuance as proof of new permissions or data access.
Map service-principal authentication to reported credential types, key IDs and federation IDs without exposing credential material.
Find failed managed-identity sign-in records without confusing token acquisition with downstream service authorization.
Group application identity sign-in failures by principal, resource, source IP and reported result.
Follow the connections