Multifactor authentication for your Microsoft 365 for enterprise test environment
This Test Lab Guide can be used for both Microsoft 365 for enterprise and Office 365 Enterprise test environments.
For an additional level of security for signing in to Microsoft 365 or any service or application that uses the Microsoft Entra tenant for your subscription, you can enable Microsoft Entra multifactor authentication, which requires more than just a username and password to verify an account.
With multifactor authentication, users are required to acknowledge a phone call, type a verification code sent in a text message, or verify the authentication with an app on their smart phones after correctly entering their passwords. They can sign in only after this second authentication factor is satisfied.
This article describes how to enable and test text message-based authentication for a specific user account.
Setting up multifactor authentication for an account in your Microsoft 365 for enterprise test environment involves two phases and a third optional phase:
- Phase 1: Build out your Microsoft 365 for enterprise test environment
- Phase 2: Enable and test multifactor authentication for the User 2 account
- Phase 3: Enable and test multifactor authentication with a conditional access policy
For a visual map to all the articles in the Microsoft 365 for enterprise Test Lab Guide stack, go to Microsoft 365 for enterprise Test Lab Guide Stack.
Phase 1: Build out your Microsoft 365 for enterprise test environment
If you just want to test multifactor authentication in a lightweight way with the minimum requirements, follow the instructions in Lightweight base configuration.
If you want to test multifactor authentication in a simulated enterprise, follow the instructions in Pass-through authentication.
Testing multifactor authentication does not require the simulated enterprise test environment, which includes a simulated intranet connected to the internet and directory synchronization for an Active Directory Domain Services (AD DS) forest. It is provided here as an option so that you can test multifactor authentication and experiment with it in an environment that represents a typical organization.
Phase 2: Enable and test multifactor authentication for the User 2 account
Enable multifactor authentication for the User 2 account with these steps:
Open a separate, private instance of your browser, go to the Microsoft 365 admin center (https://portal.microsoft.com), and then sign in with your global administrator account.
In the left navigation, select Users > Active users.
In the Active users pane, select multifactor authentication.
In the list, select the User 2 account.
In the User 2 section, under Quick steps, select Enable.
In the About enabling multifactor authentication dialog box, select Enable multifactor authentication.
In the Updates successful dialog box, select Close.
On the Microsoft 365 admin center tab, select the user account icon in the upper right, and then select Sign out.
Close your browser instance.
Complete the configuration for the User 2 account to use a text message for validation and test it with these steps:
Open a new, private instance of your browser.
Go to the Microsoft 365 admin center and sign in with the User 2 account name and password.
After signing in, you are prompted to set up the account for more information. Select Next.
On the Additional security verification page:
Select your country or region.
Enter the phone number of the smart phone that will receive text messages.
In Method, select Send me a code by text message.
Enter the verification code from the text message received on your smart phone, and then select Verify.
On the Step 3: Keep your existing applications page, select Done.
If this is the first time you signed in with the User 2 account, you are prompted to change the password. Enter the original password and a new password twice, and then select Update password and sign in. Record the new password in a secure location.
You should see the Office portal for User 2 on the Microsoft Office Home tab of your browser.
Phase 3: Enable and test multifactor authentication with a conditional access policy
This phase can only be used for a Microsoft 365 for enterprise test environment.
In this phase, you enable multifactor authentication for the User 3 account using a group and a conditional access policy.
Next, create a new group named MFAUsers and add the User 3 account to it.
- On the Microsoft 365 admin center tab, select Groups in the left navigation, and then select Groups.
- Select Add a group.
- In the Choose a group type pane, select Security, and then select Next.
- In the Set up the basics pane, select Create group, and then select Close.
- In the Review and finish adding group pane, enter MFAUsers, and then select Next.
- In the list of groups, select the MFAUsers group.
- In the MFAUsers pane, select Members, and then select View all and manage members.
- In the MFAUsers pane, select Add members, select the User 3 account, and then select Save > Close > Close.
Next, create a conditional access policy to require multifactor authentication for members of the MFAUsers group.
- In a new tab of your browser, go to https://portal.azure.com.
- Select Microsoft Entra ID > Security > Conditional Access.
- In the Conditional access – Policies pane, select New policy.
- In the New pane, enter MFA for user accounts in the Name box.
- In the Assignments section, select Users and groups.
- On the Include tab of the Users and groups pane, select Select users and groups > Users and groups > Select.
- In the Select pane, select the MFAUsers group, and then select Select > Done.
- In the Access controls section of the New pane, select Grant.
- In the Grant pane, select Require multifactor authentication, and then select Select.
- In the New pane, select On for Enable policy, and then select Create.
- Close the Azure portal and Microsoft 365 admin center tabs.
To test this policy, sign out and sign in with the User 3 account. You should be prompted to configure MFA. This demonstrates that the MFAUsers policy is being applied.
Explore additional identity features and capabilities in your test environment.