Emergency access (break-glass) accounts in Microsoft Entra ID: a practical checklist

Last reviewed: November 20, 2026 · 8 min read · Based on Microsoft Learn: "Manage emergency access admin accounts"

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

RequirementWhy
At least two emergency access accountsRedundancy if one credential is lost or fails.
Cloud-only accounts on the *.onmicrosoft.com domain, not federated or synchronizedThey 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 methodSatisfies mandatory MFA requirements while avoiding a shared point of failure.
Global Administrator assigned as permanent active (not eligible) in Privileged Identity ManagementActivation 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 locationsAvailable to the team, not one person.
Credentials and devices don't expire and aren't removed by automated cleanupThe account must still work after months of non-use.
Alerts on every sign-in; validation at least every 90 daysAny use is either a drill, an emergency, or an incident.

Step-by-step

  1. Create two cloud-only users, for example ea-admin-01@yourtenant.onmicrosoft.com, and assign Global Administrator as active permanent.
  2. Register a FIDO2 security key (passkey) for each account. Use different keys and store them separately.
  3. 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.
  4. 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.
  5. Document the process: who may use the accounts, where the keys are, how to report use.
  6. 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

This control is item ID-04 and LM-05 in our Tenant Security Audit Kit.

Source: Microsoft Learn, "Manage emergency access admin accounts - Microsoft Entra ID" (reviewed November 2026). Always follow the current version of that article.

This guide was drafted with AI assistance and checked against public Microsoft documentation. How we use AI. Spotted an error? Email support@adminkitlab.com.