CIS Microsoft Azure Foundations Benchmark v1.4.0/Identity and Access Management/2 of 115
1.2Ensure that 'Multi-Factor Auth Status' is 'Enabled' for all Non-Privileged Users
Control family: Identity and Access Management
Control description
Enable multi-factor authentication for all non-privileged users.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Every person with an account in the directory, not just administrators, signs in with a second factor. Ordinary accounts can still read data, invite guests and register devices, and they are the ones phishing usually catches first. Security defaults (1.21) or a Conditional Access policy for all users does this.
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 MFA rollout communication
On Azure the tasks require MFA for all users with a Conditional Access policy in Microsoft Entra ID, then check that everyone has registered a method.
Task 1Require MFA for all users with Conditional Access
- Sign in to the Azure portal at portal.azure.com as a Conditional Access Administrator and open Microsoft Entra ID > Conditional Access > Policies.
- Select + New policy and name it require-mfa-all-users.
- Under Users, include All users, and under Exclude add the break-glass accounts and any service accounts that can't do MFA (replace them with managed identities over time).
- Under Target resources, choose All resources.
- Under Grant, choose Require multifactor authentication and select Select.
- Set Enable policy to Report-only, review the impact in the sign-in logs, then set it to On and select Save.
- Check it: any user's sign-in log shows the policy applied and MFA satisfied.
Task 2Check everyone has an MFA method
- In Microsoft Entra ID, open Authentication methods > User registration details.
- Filter on users who are not Multifactor authentication capable.
- Contact each one to register, starting with accounts that are active.
- Check it: the list is empty apart from documented exceptions.
Evidence
- The require-mfa-all-users Conditional Access policy
- The User registration details report, with every user MFA capable or a documented exception
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
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.