Protego field desk
Identity & Access · 30% of exam

L5. Break Glass & Emergency Access

Course outlineLesson 5 of 18

Configure independent emergency access to Microsoft Entra ID with phishing-resistant authentication, verified Conditional Access exclusions and tested monitoring.

Course context: AZ-500 retired on August 31, 2026. Use these Azure security concepts for operational practice and continue with the current SC-500 course for certification preparation.

Why Emergency Access Accounts Exist

Emergency accounts preserve tenant administration when normal sign-in or PIM activation is unavailable. They still authenticate to Microsoft Entra ID and must satisfy mandatory MFA.

Configure Independent Access

  • Create two or more cloud-only accounts in the tenant's onmicrosoft.com domain, independent of federation and on-premises synchronization.
  • Assign Global Administrator as active permanent, not eligible through PIM.
  • Register phishing-resistant authentication: Microsoft recommends a passkey (FIDO2); certificate-based authentication is another option for an organization with PKI. Use a different method from everyday administrators.
  • Secure credentials for authorized administrators, avoid personal-device dependencies, and prevent credential expiry or automated cleanup.
  • Use a designated secure administrative workstation.

Conditional Access

Exclude emergency accounts from enforced Conditional Access policies that block or restrict sign-in. Report-only policies do not require exclusions. Verify the effective exclusions and sign-in path during drills; an exclusion does not exempt an account from mandatory MFA.

Monitor and Test

Alert on every sign-in and audit event involving these accounts. Send Entra logs to Log Analytics or Microsoft Sentinel and test alert delivery. Validate sign-in and administrative functionality at least every 90 days, and after relevant staff or subscription changes. Investigate each use and record a post-incident review.

References

Continue Learning

Exam Focus Points
  • ✓Two or more cloud-only onmicrosoft.com accounts avoid federation and synchronization dependencies
  • ✓Emergency Global Administrator assignments are active permanent rather than PIM eligible
  • ✓Use phishing-resistant MFA, preferably a FIDO2 passkey, independent of everyday admin authentication
  • ✓Exclude from enforced Conditional Access policies that restrict sign-in; report-only policies need no exclusion
  • ✓Alert on sign-in and audit activity and test sign-in plus administrative functionality at least every 90 days
Knowledge Check

1. Why should emergency access accounts be cloud-only rather than federated?

2. How should emergency account activity be monitored?

3. Which authentication approach follows current Microsoft emergency access guidance?