How to require two-step verification for a user

You can take one of two approaches for requiring two-step verification, both of which require using a global administrator account. The first option is to enable each user for Azure Multi-Factor Authentication (MFA). When users are enabled individually, they perform two-step verification each time they sign in (with some exceptions, such as when they sign in from trusted IP addresses or when the remembered devices feature is turned on). The second option is to set up a Conditional Access policy that requires two-step verification under certain conditions.


Enabling Azure Multi-Factor Authentication using Conditional Access policies is the recommended approach. Changing user states is no longer recommended unless your licenses do not include Conditional Access as it will require users to perform MFA every time they sign in.

Choose how to enable

Enabled by changing user state - This is the traditional method for requiring two-step verification and is discussed in this article. It works with both Azure MFA in the cloud and Azure MFA Server. Using this method requires users to perform two-step verification every time they sign in and overrides Conditional Access policies.

Enabled by Conditional Access policy - This is the most flexible means to enable two-step verification for your users. Enabling using Conditional Access policy only works for Azure MFA in the cloud and is a premium feature of Azure AD. More information on this method can be found in Deploy cloud-based Azure Multi-Factor Authentication.

Enabled by Azure AD Identity Protection - This method uses the Azure AD Identity Protection risk policy to require two-step verification based only on sign-in risk for all cloud applications. This method requires Azure Active Directory P2 licensing. More information on this method can be found in Azure Active Directory Identity Protection


More information about licenses and pricing can be found on the Azure AD and Multi-Factor Authentication pricing pages.

Enable Azure MFA by changing user state

User accounts in Azure Multi-Factor Authentication have the following three distinct states:


Enabling Azure MFA through a Conditional Access policy will not change the state of the user. Do not be alarmed users appear disabled. Conditional Access does not change the state. Organizations should not enable or enforce users if they are utilizing Conditional Access policies.

Status Description Non-browser apps affected Browser apps affected Modern authentication affected
Disabled The default state for a new user not enrolled in Azure MFA. No No No
Enabled The user has been enrolled in Azure MFA, but has not registered. They receive a prompt to register the next time they sign in. No. They continue to work until the registration process is completed. Yes. After the session expires, Azure MFA registration is required. Yes. After the access token expires, Azure MFA registration is required.
Enforced The user has been enrolled and has completed the registration process for Azure MFA. Yes. Apps require app passwords. Yes. Azure MFA is required at login. Yes. Azure MFA is required at login.

A user's state reflects whether an admin has enrolled them in Azure MFA, and whether they completed the registration process.

All users start out Disabled. When you enroll users in Azure MFA, their state changes to Enabled. When enabled users sign in and complete the registration process, their state changes to Enforced.


If MFA is re-enabled on a user object that already has registration details, such as phone or email, then administrators need to have that user re-register MFA via Azure portal or PowerShell. If the user doesn't re-register, their MFA state doesn't transition from Enabled to Enforced in MFA management UI.

View the status for a user

Use the following steps to access the page where you can view and manage user states:

  1. Sign in to the Azure portal as an administrator.
  2. Search for and select Azure Active Directory. Select Users > All users.
  3. Select Multi-Factor Authentication. Select Multi-Factor Authentication
  4. A new page that displays the user states opens. multi-factor authentication user status - screenshot

Change the status for a user

  1. Use the preceding steps to get to the Azure Multi-Factor Authentication users page.

  2. Find the user you want to enable for Azure MFA. You might need to change the view at the top. Select the user to change status for from the users tab

  3. Check the box next to their name.

  4. On the right, under quick steps, choose Enable or Disable. Enable selected user by clicking Enable on the quick steps menu


    Enabled users are automatically switched to Enforced when they register for Azure MFA. Do not manually change the user state to Enforced.

  5. Confirm your selection in the pop-up window that opens.

After you enable users, notify them via email. Tell them that they'll be asked to register the next time they sign in. Also, if your organization uses non-browser apps that don't support modern authentication, they need to create app passwords. You can also include a link to the Azure MFA end-user guide to help them get started.

Use PowerShell

To change the user state by using Azure AD PowerShell, change $st.State. There are three possible states:

  • Enabled
  • Enforced
  • Disabled

Don't move users directly to the Enforced state. If you do, non-browser-based apps stop working because the user has not gone through Azure MFA registration and obtained an app password.

Install the Module first, using:

Install-Module MSOnline


Don't forget to connect first using Connect-MsolService


This example PowerShell script enables MFA for an individual user:

Import-Module MSOnline
$st = New-Object -TypeName Microsoft.Online.Administration.StrongAuthenticationRequirement
$st.RelyingParty = "*"
$st.State = "Enabled"
$sta = @($st)
Set-MsolUser -UserPrincipalName -StrongAuthenticationRequirements $sta

Using PowerShell is a good option when you need to bulk enable users. As an example, the following script loops through a list of users and enables MFA on their accounts:

$users = "","",""
foreach ($user in $users)
    $st = New-Object -TypeName Microsoft.Online.Administration.StrongAuthenticationRequirement
    $st.RelyingParty = "*"
    $st.State = "Enabled"
    $sta = @($st)
    Set-MsolUser -UserPrincipalName $user -StrongAuthenticationRequirements $sta

To disable MFA, use this script:

Get-MsolUser -UserPrincipalName | Set-MsolUser -StrongAuthenticationRequirements @()

which can also be shortened to:

Set-MsolUser -UserPrincipalName -StrongAuthenticationRequirements @()

Convert users from per-user MFA to Conditional Access based MFA

The following PowerShell can assist you in making the conversion to Conditional Access based Azure Multi-Factor Authentication.

Run this PowerShell in an ISE window or save as a .PS1 file to run locally.

# Sets the MFA requirement state
function Set-MfaState {


    Process {
        Write-Verbose ("Setting MFA state for user '{0}' to '{1}'." -f $ObjectId, $State)
        $Requirements = @()
        if ($State -ne "Disabled") {
            $Requirement =
            $Requirement.RelyingParty = "*"
            $Requirement.State = $State
            $Requirements += $Requirement

        Set-MsolUser -ObjectId $ObjectId -UserPrincipalName $UserPrincipalName `
                     -StrongAuthenticationRequirements $Requirements

# Disable MFA for all users
Get-MsolUser -All | Set-MfaState -State Disabled


We recently changed the behavior and PowerShell script above accordingly. Previously, the script saved off the MFA methods, disabled MFA, and restored the methods. This is no longer necessary now that the default behavior for disable doesn't clear the methods.

If MFA is re-enabled on a user object that already has registration details, such as phone or email, then administrators need to have that user re-register MFA via Azure portal or PowerShell. If the user doesn't re-register, their MFA state doesn't transition from Enabled to Enforced in MFA management UI.

Next steps