Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Identity and Access Management/1 of 115

1.1Ensure that 'Multi-Factor Auth Status' is 'Enabled' for all Privileged Users

Control family: Identity and Access Management

Control description

Enable multi-factor authentication for all roles, groups, and users that have write access or permissions to Azure resources. These include custom created objects or built-in roles such as;

- Service Co-Administrators

- Subscription Owners

- Contributors

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Anyone who can change Azure resources, through Owner, Contributor or any role with write access, must prove who they are with a second factor at every sign-in. A stolen password then isn't enough to change or delete what the organization runs. Microsoft now also requires MFA for signing in to the Azure portal, but a policy you own covers every way in, including tools and scripts.

Before you start

The same on every cloud, before the steps in the tabs.

  • Create two emergency access (break-glass) accounts, excluded from the policy, with long random passwords kept in a safe, and alert on any sign-in by them.
  • Tell users when MFA starts and how to register, and give the help desk a way to verify people who lose their device.

Evidence

  • The break-glass account record and the sign-in alert on those accounts

On Azure the tasks require MFA for privileged roles with a Conditional Access policy in Microsoft Entra ID, then check that every privileged user has registered a method.

Task 1Require MFA for privileged roles with Conditional Access

  1. Sign in to the Azure portal at portal.azure.com as a Conditional Access Administrator and open Microsoft Entra ID > Conditional Access > Policies.
  2. Select + New policy and name it require-mfa-admins.
  3. Under Users, choose Select users and groups > Directory roles, and pick Global Administrator, Privileged Role Administrator, Security Administrator and the other admin roles; also include the groups that hold Owner or Contributor on subscriptions.
  4. Under Exclude, add the two break-glass accounts.
  5. Under Target resources, choose All resources (formerly all cloud apps).
  6. Under Grant, choose Grant access with Require multifactor authentication, and select Select.
  7. Set Enable policy to Report-only, check the sign-in logs for a few days, then switch it to On and select Save.
  8. Check it: a privileged user's sign-in log entry shows the policy applied and MFA satisfied.

Task 2Check every privileged user has an MFA method

  1. In Microsoft Entra ID, open Authentication methods > User registration details.
  2. Filter on users who are not Multifactor authentication capable.
  3. Compare the list with the holders of admin roles (Roles and administrators) and of Owner or Contributor on subscriptions (Access control (IAM)).
  4. Ask each one still listed to register a method, or remove their privileged access.
  5. Check it: no privileged user remains on the not-capable list.

Evidence

  • The require-mfa-admins Conditional Access policy, showing its users, exclusions and grant control
  • The User registration details report, showing every privileged user MFA capable

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.