Configure and enable users for SMS-based authentication using Azure Active Directory
To simplify and secure sign-in to applications and services, Azure Active Directory (Azure AD) provides multiple authentication options. SMS-based authentication lets users sign-in without providing, or even knowing, their user name and password. After their account is created by an identity administrator, they can enter their phone number at the sign-in prompt. They receive an authentication code via text message that they can provide to complete the sign-in. This authentication method simplifies access to applications and services, especially for Frontline workers.
This article shows you how to enable SMS-based authentication for select users or groups in Azure AD. For a list of apps that support using SMS-based sign-in, see App support for SMS-based authentication.
Before you begin
To complete this article, you need the following resources and privileges:
- An active Azure subscription.
- If you don't have an Azure subscription, create an account.
- An Azure Active Directory tenant associated with your subscription.
- You need global administrator privileges in your Azure AD tenant to enable SMS-based authentication.
- Each user that's enabled in the text message authentication method policy must be licensed, even if they don't use it. Each enabled user must have one of the following Azure AD, EMS, Microsoft 365 licenses:
Here are some known issues:
- SMS-based authentication isn't currently compatible with Azure AD Multi-Factor Authentication.
- Except for Teams, SMS-based authentication isn't compatible with native Office applications.
- SMS-based authentication isn't recommended for B2B accounts.
- Federated users won't authenticate in the home tenant. They only authenticate in the cloud.
- If a user's default sign-in method is a text or call to your phone number, then the SMS code or voice call is sent automatically during multifactor authentication. As of June 2021, some apps will ask users to choose Text or Call first. This option prevents sending too many security codes for different apps. If the default sign-in method is the Microsoft Authenticator app (which we highly recommend), then the app notification is sent automatically.
- SMS-based authentication has reached general availability, and we're working to remove the (Preview) label in the Azure portal.
Enable the SMS-based authentication method
There are three main steps to enable and use SMS-based authentication in your organization:
- Enable the authentication method policy.
- Select users or groups that can use the SMS-based authentication method.
- Assign a phone number for each user account.
- This phone number can be assigned in the Azure portal (which is shown in this article), and in My Staff or My Account.
First, let's enable SMS-based authentication for your Azure AD tenant.
Sign-in to the Azure portal using an account with global administrator permissions.
Search for and select Azure Active Directory, then choose Security from the menu on the left-hand side.
Under the Manage menu header, select Authentication methods > Policies.
From the list of available authentication methods, select Text message.
Set Enable to Yes. Then select the Target users.
You can choose to enable SMS-based authentication for All users or Select users and groups. In the next section, you enable SMS-based authentication for a test user.
Assign the authentication method to users and groups
With SMS-based authentication enabled in your Azure AD tenant, now select some users or groups to be allowed to use this authentication method.
- In the text message authentication policy window, set Target to Select users.
- Choose to Add users or groups, then select a test user or group, such as Contoso User or Contoso SMS Users.
- When you've selected your users or groups, choose Select, then Save the updated authentication method policy.
Each user that's enabled in the text message authentication method policy must be licensed, even if they don't use it. Make sure you have the appropriate licenses for the users you enable in the authentication method policy, especially when you enable the feature for large groups of users.
Set a phone number for user accounts
Users are now enabled for SMS-based authentication, but their phone number must be associated with the user profile in Azure AD before they can sign-in. The user can set this phone number themselves in My Account, or you can assign the phone number using the Azure portal. Phone numbers can be set by global admins, authentication admins, or privileged authentication admins.
Search for and select Azure Active Directory.
From the navigation menu on the left-hand side of the Azure Active Directory window, select Users.
Select the user you enabled for SMS-based authentication in the previous section, such as Contoso User, then select Authentication methods.
Select + Add authentication method, then in the Choose method drop-down menu, choose Phone number.
Enter the user's phone number, including the country code, such as +1 xxxxxxxxx. The Azure portal validates the phone number is in the correct format.
Then, from the Phone type drop-down menu, select Mobile, Alternate mobile, or Other as needed.
The phone number must be unique in your tenant. If you try to use the same phone number for multiple users, an error message is shown.
To apply the phone number to a user's account, select Add.
When successfully provisioned, a check mark appears for SMS Sign-in enabled.
Test SMS-based sign-in
To test the user account that's now enabled for SMS-based sign-in, complete the following steps:
Open a new InPrivate or Incognito web browser window to https://www.office.com
In the top right-hand corner, select Sign in.
At the sign-in prompt, enter the phone number associated with the user in the previous section, then select Next.
A text message is sent to the phone number provided. To complete the sign-in process, enter the 6-digit code provided in the text message at the sign-in prompt.
The user is now signed in without the need to provide a username or password.
Troubleshoot SMS-based sign-in
The following scenarios and troubleshooting steps can used if you have problems with enabling and using SMS-based sign-in. For a list of apps that support using SMS-based sign-in, see App support for SMS-based authentication.
Phone number already set for a user account
If a user has already registered for Azure AD Multi-Factor Authentication and / or self-service password reset (SSPR), they already have a phone number associated with their account. This phone number isn't automatically available for use with SMS-based sign-in.
A user that has a phone number already set for their account is displayed a button to Enable for SMS sign-in in their My Profile page. Select this button, and the account is enabled for use with SMS-based sign-in and the previous Azure AD Multi-Factor Authentication or SSPR registration.
For more information on the end-user experience, see SMS sign-in user experience for phone number.
Error when trying to set a phone number on a user's account
If you receive an error when you try to set a phone number for a user account in the Azure portal, review the following troubleshooting steps:
- Make sure that you're enabled for the SMS-based sign-in.
- Confirm that the user account is enabled in the Text message authentication method policy.
- Make sure you set the phone number with the proper formatting, as validated in the Azure portal (such as +1 4251234567).
- Make sure that the phone number isn't used elsewhere in your tenant.
- Check there's no voice number set on the account. If a voice number is set, delete and try to the phone number again.
- For a list of apps that support using SMS-based sign-in, see App support for SMS-based authentication.
- For more ways to sign-in to Azure AD without a password, such as the Microsoft Authenticator App or FIDO2 security keys, see Passwordless authentication options for Azure AD.
- You can also use the Microsoft Graph REST API to enable or disable SMS-based sign-in.