Emergency access (break-glass) accounts in Microsoft Entra ID: a practical checklist
An emergency access account is the key you keep in a safe for the day your normal admin accounts can't sign in: an MFA outage, a federation failure, a broken Conditional Access policy, or the only Global Administrator leaving.
What Microsoft recommends
| Requirement | Why |
|---|---|
| At least two emergency access accounts | Redundancy if one credential is lost or fails. |
Cloud-only accounts on the *.onmicrosoft.com domain, not federated or synchronized | They keep working when on-premises AD or a federation service is down. |
| Phishing-resistant authentication (passkey/FIDO2 recommended, or certificate-based authentication), different from your normal admin method | Satisfies mandatory MFA requirements while avoiding a shared point of failure. |
| Global Administrator assigned as permanent active (not eligible) in Privileged Identity Management | Activation may itself be what is broken during an emergency. |
| Excluded from Conditional Access policies that block or restrict sign-in (report-only policies don't need an exclusion) | A policy mistake must not lock out the recovery path. |
| Not tied to any individual or personal device; credentials stored in secure, separate, fireproof locations | Available to the team, not one person. |
| Credentials and devices don't expire and aren't removed by automated cleanup | The account must still work after months of non-use. |
| Alerts on every sign-in; validation at least every 90 days | Any use is either a drill, an emergency, or an incident. |
Step-by-step
- Create two cloud-only users, for example
ea-admin-01@yourtenant.onmicrosoft.com, and assign Global Administrator as active permanent. - Register a FIDO2 security key (passkey) for each account. Use different keys and store them separately.
- Create a security group such as EmergencyAccess, add both accounts, and exclude the group from every Conditional Access policy that blocks or restricts sign-in.
- Send Microsoft Entra sign-in logs to a Log Analytics workspace and create an alert rule that fires when either account's object ID appears in
SigninLogs. - Document the process: who may use the accounts, where the keys are, how to report use.
- Every 90 days (and after IT staff changes), run a drill: sign in, perform an admin task, confirm the alert fired, review the authorized-user list.
Test Conditional Access changes in report-only mode and confirm your emergency accounts can still sign in afterward. Microsoft suggests testing at least quarterly.
Common mistakes
- Only one emergency account, or both keys stored in the same place.
- Using SMS or a personal phone app for MFA on the emergency account.
- Forgetting to exclude the accounts from a new Conditional Access policy.
- No alert, so nobody notices if the account is misused.
This control is item ID-04 and LM-05 in our Tenant Security Audit Kit.