Case 2A8718 · Identity & AD · L3 Applied
Conditional Access Design
- 01 Context
- 02 Mechanism
- 03 Lessons
What a strong answer covers
Try it out loud first. Then check yourself:
- Entra Conditional Access is an if-then engine run at token issuance: signals in, then block, grant or session controls
- Signals: user, app, device platform and compliance, location, client app, sign-in and user risk; block always wins
- Common gaps: broad exclusions, legacy auth left open, device code flow allowed, policies stuck in report-only
- Baseline: MFA for all, phishing-resistant MFA for admins, block legacy auth, compliant device for sensitive apps
- Lessons: existing tokens live until expiry unless CAE applies; test with What If; keep two monitored break-glass accounts
If the interviewer pushes back
- A user passes Conditional Access on a compliant laptop, then the token is stolen. Which features limit replay, and how far?