Manage emergency access accounts in Azure AD
It is important that you prevent being accidentally locked out of your Azure Active Directory (Azure AD) organization because you can't sign in or activate another user's account as an administrator. You can mitigate the impact of accidental lack of administrative access by creating two or more emergency access accounts in your organization.
Emergency access accounts are highly privileged, and they are not assigned to specific individuals. Emergency access accounts are limited to emergency or "break glass"' scenarios where normal administrative accounts can't be used. We recommend that you maintain a goal of restricting emergency account use to only the times when it is absolutely necessary.
This article provides guidelines for managing emergency access accounts in Azure AD.
Why use an emergency access account
An organization might need to use an emergency access account in the following situations:
- The user accounts are federated, and federation is currently unavailable because of a cell-network break or an identity-provider outage. For example, if the identity provider host in your environment has gone down, users might be unable to sign in when Azure AD redirects to their identity provider.
- The administrators are registered through Azure AD Multi-Factor Authentication, and all their individual devices are unavailable or the service is unavailable. Users might be unable to complete Multi-Factor Authentication to activate a role. For example, a cell network outage is preventing them from answering phone calls or receiving text messages, the only two authentication mechanisms that they registered for their device.
- The person with the most recent Global Administrator access has left the organization. Azure AD prevents the last Global Administrator account from being deleted, but it does not prevent the account from being deleted or disabled on-premises. Either situation might make the organization unable to recover the account.
- Unforeseen circumstances such as a natural disaster emergency, during which a mobile phone or other networks might be unavailable.
Create emergency access accounts
Create two or more emergency access accounts. These accounts should be cloud-only accounts that use the *.onmicrosoft.com domain and that are not federated or synchronized from an on-premises environment.
When configuring these accounts, the following requirements must be met:
- The emergency access accounts should not be associated with any individual user in the organization. Make sure that your accounts are not connected with any employee-supplied mobile phones, hardware tokens that travel with individual employees, or other employee-specific credentials. This precaution covers instances where an individual employee is unreachable when the credential is needed. It is important to ensure that any registered devices are kept in a known, secure location that has multiple means of communicating with Azure AD.
- Use strong authentication for your emergency access accounts and make sure it doesn’t use the same authentication methods as your other administrative accounts. For example, if your normal administrator account uses the Microsoft Authenticator app for strong authentication, use a FIDO2 security key for your emergency accounts. Consider the dependencies of various authentication methods, to avoid adding external requirements into the authentication process.
- The device or credential must not expire or be in scope of automated cleanup due to lack of use.
- In Azure AD Privileged Identity Management, you should make the Global Administrator role assignment permanent rather than eligible for your emergency access accounts.
Exclude at least one account from phone-based multi-factor authentication
To reduce the risk of an attack resulting from a compromised password, Azure AD recommends that you require multi-factor authentication for all individual users. This group includes administrators and all others (for example, financial officers) whose compromised account would have a significant impact.
However, at least one of your emergency access accounts should not have the same multi-factor authentication mechanism as your other non-emergency accounts. This includes third-party multi-factor authentication solutions. If you have a Conditional Access policy to require multi-factor authentication for every administrator for Azure AD and other connected software as a service (SaaS) apps, you should exclude emergency access accounts from this requirement, and configure a different mechanism instead. Additionally, you should make sure the accounts do not have a per-user multi-factor authentication policy.
Exclude at least one account from Conditional Access policies
During an emergency, you do not want a policy to potentially block your access to fix an issue. If you use Conditional Access, at least one emergency access account needs to be excluded from all Conditional Access policies.
Some organizations use AD Domain Services and AD FS or similar identity provider to federate to Azure AD. The emergency access for on-premises systems and the emergency access for cloud services should be kept distinct, with no dependency of one on the other. Mastering and or sourcing authentication for accounts with emergency access privileges from other systems adds unnecessary risk in the event of an outage of those system(s).
Store account credentials safely
Organizations need to ensure that the credentials for emergency access accounts are kept secure and known only to individuals who are authorized to use them. Some customers use a smartcard and others use passwords. A password for an emergency access account is usually separated into two or three parts, written on separate pieces of paper, and stored in secure, fireproof safes that are in secure, separate locations.
If using passwords, make sure the accounts have strong passwords that do not expire the password. Ideally, the passwords should be at least 16 characters long and randomly generated.
Monitor sign-in and audit logs
Organizations should monitor sign-in and audit log activity from the emergency accounts and trigger notifications to other administrators. When you monitor the activity on break glass accounts, you can verify these accounts are only used for testing or actual emergencies. You can use Azure Log Analytics to monitor the sign-in logs and trigger email and SMS alerts to your admins whenever break glass accounts sign in.
- Send Azure AD sign-in logs to Azure Monitor.
Obtain Object IDs of the break glass accounts
Select Azure Active Directory > Users.
Search for the break-glass account and select the user’s name.
Copy and save the Object ID attribute so that you can use it later.
Repeat previous steps for second break-glass account.
Create an alert rule
- Sign in to the Azure portal with an account assigned to the Monitoring Contributor role in Azure Monitor.
- Select All services", enter "log analytics" in Search and then select Log Analytics workspaces.
- Select a workspace.
- In your workspace, select Alerts > New alert rule.
Under Resource, verify that the subscription is the one with which you want to associate the alert rule.
Under Condition, select Add.
Select Custom log search under Signal name.
Under Search query, enter the following query, inserting the object IDs of the two break glass accounts.
For each additional break glass account you want to include, add another "or UserId == "ObjectGuid"" to the query.
Under Alert logic, enter the following:
- Based on: Number of results
- Operator: Greater than
- Threshold value: 0
Under Evaluated based on, select the Period (in minutes) for how long you want the query to run, and the Frequency (in minutes) for how often you want the query to run. The frequency should be less than or equal to the period.
Select Done. You may now view the estimated monthly cost of this alert.
- Select an action group of users to be notified by the alert. If you want to create one, see Create an action group.
- To customize the email notification sent to the members of the action group, select actions under Customize Actions.
- Under Alert Details, specify the alert rule name and add an optional description.
- Set the Severity level of the event. We recommend that you set it to Critical(Sev 0).
- Under Enable rule upon creation, leave it set as yes.
- To turn off alerts for a while, select the Suppress Alerts check box and enter the wait duration before alerting again, and then select Save.
- Click Create alert rule.
Create an action group
Select Create an action group.
Enter the action group name and a short name.
Verify the subscription and resource group.
Under action type, select Email/SMS/Push/Voice.
Enter an action name such as Notify global admin.
Select the Action Type as Email/SMS/Push/Voice.
Select Edit details to select the notification methods you want to configure and enter the required contact information, and then select Ok to save the details.
Add any additional actions you want to trigger.
Validate accounts regularly
When you train staff members to use emergency access accounts and validate the emergency access accounts, at minimum do the following steps at regular intervals:
- Ensure that security-monitoring staff are aware that the account-check activity is ongoing.
- Ensure that the emergency break glass process to use these accounts is documented and current.
- Ensure that administrators and security officers who might need to perform these steps during an emergency are trained on the process.
- Update the account credentials, in particular any passwords, for your emergency access accounts, and then validate that the emergency access accounts can sign-in and perform administrative tasks.
- Ensure that users have not registered Multi-Factor Authentication or self-service password reset (SSPR) to any individual user’s device or personal details.
- If the accounts are registered for Multi-Factor Authentication to a device, for use during sign-in or role activation, ensure that the device is accessible to all administrators who might need to use it during an emergency. Also verify that the device can communicate through at least two network paths that do not share a common failure mode. For example, the device can communicate to the internet through both a facility's wireless network and a cell provider network.
These steps should be performed at regular intervals and for key changes:
- At least every 90 days
- When there has been a recent change in IT staff, such as a job change, a departure, or a new hire
- When the Azure AD subscriptions in the organization have changed
- Securing privileged access for hybrid and cloud deployments in Azure AD
- Add users using Azure AD and assign the new user to the Global Administrator role
- Sign up for Azure AD Premium, if you haven’t signed up already
- How to require two-step verification for a user
- Configure additional protections for Global Administrators in Microsoft 365, if you are using Microsoft 365
- Start an access review of Global Administrators and transition existing Global Administrators to more specific administrator roles