Require phishing-resistant multifactor authentication for Microsoft Entra administrator roles - Microsoft Entra ID (original) (raw)

Overview

Accounts with privileged administrative roles are frequent targets of attackers. Requiring phishing-resistant multifactor authentication (MFA) for these accounts reduces the risk of compromise.

Microsoft recommends requiring phishing-resistant multifactor authentication for at least the following roles:

Global Administrator
Application Administrator
Authentication Administrator
Billing Administrator
Cloud Application Administrator
Conditional Access Administrator
Exchange Administrator
Helpdesk Administrator
Password Administrator
Privileged Authentication Administrator
Privileged Role Administrator
Security Administrator
SharePoint Administrator
User Administrator

Organizations can include or exclude roles based on their requirements.

Organizations can use this policy with features like Privileged Identity Management (PIM), which lets you require MFA for role activation.

Authentication strength

This article helps your organization create an MFA policy for your environment using authentication strengths. Microsoft Entra ID offers three built-in authentication strengths:

Multifactor authentication strength (less restrictive)
Passwordless MFA strength
Phishing-resistant MFA strength (most restrictive), recommended in this article

Use one of the built-in strengths or create a custom authentication strength based on the authentication methods you want to require.

For external user scenarios, the MFA authentication methods that a resource tenant accepts vary depending on whether the user completes MFA in their home tenant or in the resource tenant. For more information, see Authentication strength for external users.

User exclusions

Conditional Access policies are powerful tools. We recommend excluding the following accounts from your policies:

Emergency access or break-glass accounts to prevent lockout due to policy misconfiguration. In the unlikely scenario where all administrators are locked out, your emergency access administrative account can be used to sign in and recover access.
- More information can be found in the article, Manage emergency access accounts in Microsoft Entra ID.
Service accounts and Service principals, such as the Microsoft Entra Connect Sync Account. Service accounts are noninteractive accounts that aren't tied to any specific user. They're typically used by backend services to allow programmatic access to applications, but they're also used to sign in to systems for administrative purposes. Calls made by service principals aren't blocked by Conditional Access policies scoped to users. Use Conditional Access for workload identities to define policies that target service principals.
- If your organization uses these accounts in scripts or code, replace them with managed identities.

Template deployment

Organizations can deploy this policy by following the steps outlined below or by using the Conditional Access templates.

Create a Conditional Access policy

Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator.
Browse to Entra ID > Conditional Access > Policies.
Select New policy.
Name your policy. Create a meaningful naming standard for your organization's policies.
Under Assignments, select Users or workload identities.
1. Under Include, select Directory roles and choose at least the previously listed roles.
2. Under Exclude, select Users and groups, and choose your organization's emergency access or break-glass accounts.
Under Target resources > Resources (formerly cloud apps) > Include, select All resources (formerly 'All cloud apps').
Under Access controls > Grant, select Grant access.
1. Select Require authentication strength, then select Phishing-resistant MFA strength from the list.
2. Select Select.
Confirm your settings, and set Enable policy to Report-only.
Select Create to enable your policy.