Microsoft recommends two or more break glass accounts with permanent admin rights
Microsoft recommends two cloud-only emergency access accounts permanently assigned the Global Administrator role. 507
Microsoft wants at least two cloud-only accounts
Create two or more emergency access accounts on your onmicrosoft.com domain. They should be cloud-only and never federated or synced from an on-premises directory. 143
If you use Privileged Identity Management, make the accounts' Global Administrator assignment active and permanent. 143
Passkeys or certificates protect the accounts
Sign them in with a passkey (FIDO2), which Microsoft recommends, or with certificates if you already run a PKI. Use a different method from your other admin accounts. 143
The device used for their second factor should reach the internet through at least two network paths that don't share a common failure mode. 143
Conditional Access has to leave these accounts out
Exclude the emergency accounts from Conditional Access policies that block or restrict sign-in. Report-only policies don't block access, so they don't need the exclusion. 143
Microsoft suggests keeping emergency Conditional Access policies ready in report-only mode, switched on only when needed. 507
The credentials belong in separate fireproof safes
Store the credentials in fireproof safes in separate, secure locations, and never connect the accounts to staff-supplied phones. 143
Every sign-in to a break glass account should raise an alert
Alert on every sign-in to the emergency accounts, and test that they work at least every 90 days. 143
Microsoft's example sends sign-in logs to a Log Analytics workspace and raises a severity 0 (Critical) alert when sign-ins are greater than 0. 143
After an emergency, reset the accounts and revoke tokens
After a disruption, Microsoft says to revoke all refresh tokens issued during it and to regenerate the emergency account credentials if they were used. 507
While controls are relaxed, Microsoft says to assume attackers will try to harvest passwords through password spray or phishing. 507
This is one step in the free outage playbook.