How to Require MFA for Administrator Roles with Microsoft Entra Conditional Access

November 21, 2026

Privileged Microsoft Entra accounts are high-value targets. A Conditional Access policy that requires multifactor authentication (MFA) for administrator roles adds an important control without forcing the same policy design on every user.

This guide shows the safer deployment pattern: scope the policy to built-in directory roles, exclude emergency access accounts, test in Report-only, review the impact, and only then enable it. Microsoft now recommends phishing-resistant MFA for administrators where possible; the policy below uses the standard MFA grant control because it is the most broadly understood starting point.

Before you begin

  • Permissions: Sign in with at least the Conditional Access Administrator role.
  • Roles: This procedure targets built-in directory roles. Conditional Access does not enforce this role targeting for custom roles or administrative-unit-scoped roles.
  • Emergency access: Have at least one tested break-glass account and exclude it from the policy. Do not use the same account for routine administration.
  • MFA readiness: Confirm that every included administrator can complete an available MFA method before enabling the policy.
  • Licensing: Conditional Access is a Microsoft Entra ID feature whose availability depends on the tenant’s subscription and licensing. Confirm entitlement in your tenant before deployment.

Choose the administrator roles

Microsoft’s guidance recommends protecting, at minimum, the following built-in roles with strong authentication: 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, and User Administrator.

Start with the roles that exist in your tenant. Avoid adding every directory role by guesswork. Review the resulting membership first, especially if privileged access is activated just in time through Privileged Identity Management.

Create the policy in Report-only mode

  1. Open the Microsoft Entra admin center.
  2. Go to Entra ID > Conditional Access > Policies.
  3. Select New policy and give it a specific name, such as CA-Require-MFA-Privileged-Built-In-Roles.
  4. Under Assignments > Users or workload identities, select Include > Directory roles.
  5. Select the administrator roles you intend to protect.
  6. Under Exclude > Users and groups, exclude the organization’s emergency access accounts. Do not exclude normal administrator accounts just to avoid testing.
  7. Under Target resources > Resources, select All resources.
  8. Under Access controls > Grant, select Grant access, choose Require multifactor authentication, and select Select.
  9. Set Enable policy to Report-only.
  10. Select Create.
Do not skip Report-only. A mis-scoped policy can lock out administrators. Report-only lets you inspect the likely result before enforcement, but it is not a substitute for a controlled test with a real administrator account.

Review the impact before enabling

Open the policy after creation and review its details. Then use the Conditional Access results in sign-in logs to identify sign-ins where the policy would apply. Test with a dedicated administrator account that is included in the policy and with an excluded emergency access account. Confirm that the test administrator is prompted for MFA and that the emergency access account remains available for recovery.

Check for automation that uses a user account to sign in interactively. User-scoped Conditional Access does not block service principals. Workload identities need their own controls, and Microsoft recommends replacing script credentials with managed identities where practical.

Turn the policy on

  1. Return to Entra ID > Conditional Access > Policies.
  2. Open the policy and change Enable policy from Report-only to On.
  3. Select Save.
  4. Sign in again with an included administrator account and complete MFA.

Enable the policy during a maintenance window when another administrator can recover access. Keep the emergency access credentials offline and test them periodically according to your incident-response process.

How to verify success

  • The included administrator is challenged for MFA when signing in to a targeted resource.
  • Conditional Access details in the Entra sign-in log show the policy as applied and the grant control as satisfied.
  • The excluded emergency access account is not blocked by this policy.
  • Administrative workflows, Privileged Identity Management activation, and required automation continue to work.

Common errors and limitations

The policy does not apply to a custom role

This policy pattern targets built-in directory roles. Custom roles and administrative-unit-scoped roles are not enforced by this role targeting condition. Use a different scope, such as a carefully managed group, where appropriate.

An administrator is locked out

Use the excluded emergency access account to sign in, disable or correct the policy, and review the sign-in logs. Do not remove all exclusions as a quick fix; restore the tested recovery path first.

MFA is satisfied but the account is still at risk

Standard MFA is better than password-only access, but it is not phishing-resistant. For high-value administrator roles, evaluate an authentication-strength policy that requires phishing-resistant methods such as passkeys or security keys, subject to your tenant’s supported methods and rollout plan.

Security checklist

  • Use separate admin accounts rather than granting admin roles to everyday identities.
  • Keep emergency access accounts excluded, monitored, and protected with long, unique credentials.
  • Review role assignments regularly and remove standing privilege that is no longer needed.
  • Prefer phishing-resistant MFA for privileged access.
  • Document rollback steps before enabling any tenant-wide policy.

Related Guava Insights guides

Official documentation

Topics:
Read next
November 18, 2026

Microsoft launches AI Transparency Initiative for enterprise agents

Microsoft has launched an AI Transparency Initiative with more than 40 organizations to develop open standards that let enterprises see, independently verify and control AI model and agent activity.