Skip to content

Commit 7472e42

Browse files
committed
1 parent 9197f31 commit 7472e42

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

articles/active-directory/authentication/how-to-mfa-additional-context.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ To enable additional context in the Azure AD portal, complete the following step
187187
1. Under the **Manage** menu header, select **Authentication methods** > **Policies**.
188188
1. From the list of available authentication methods, select **Microsoft Authenticator**.
189189

190-
![Screenshot that shows how to select the Microsoft Authenticator policy](./media/how-to-mfa-additional-context/select-microsoft-authenticator-policy.png)
190+
![Screenshot that shows how to select the Microsoft Authenticator policy.](./media/how-to-mfa-additional-context/select-microsoft-authenticator-policy.png)
191191

192192
1. Select the target users, select the three dots on the right, and choose **Configure**.
193193

articles/active-directory/authentication/how-to-mfa-number-match.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -233,12 +233,12 @@ To turn number matching off, you'll need to PATCH remove **numberMatchingRequire
233233

234234
To enable number matching in the Azure portal, complete the following steps:
235235

236-
1. Sign in to the [Azure portal](https://portal.azure.com) using an account with *global administrator* permissions.
236+
1. Sign-in to the [Azure portal](https://portal.azure.com) using an account with *global administrator* permissions.
237237
1. Search for and select **Azure Active Directory**, then choose **Security** from the menu on the left-hand side.
238238
1. Under the **Manage** menu header, select **Authentication methods** > **Policies**.
239239
1. From the list of available authentication methods, select **Microsoft Authenticator**.
240240

241-
![Screenshot that shows how to select the Microsoft Authenticator policy](./media/how-to-mfa-number-match/select-microsoft-authenticator-policy.png)
241+
![Screenshot that shows how to select the Microsoft Authenticator policy.](./media/how-to-mfa-number-match/select-microsoft-authenticator-policy.png)
242242

243243
1. Select the target users, select the three dots on the right, and choose **Configure**.
244244

articles/active-directory/authentication/howto-authentication-sms-signin.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: SMS-based user sign in for Azure Active Directory
3-
description: Learn how to configure and enable users to sign in to Azure Active Directory using SMS
2+
title: SMS-based user sign-in for Azure Active Directory
3+
description: Learn how to configure and enable users to sign-in to Azure Active Directory using SMS
44

55
services: active-directory
66
ms.service: active-directory
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717

1818
# Configure and enable users for SMS-based authentication using Azure Active Directory
1919

20-
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.
20+
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.
2121

2222
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](how-to-authentication-sms-supported-apps.md).
2323

@@ -59,7 +59,7 @@ There are three main steps to enable and use SMS-based authentication in your or
5959

6060
First, let's enable SMS-based authentication for your Azure AD tenant.
6161

62-
1. Sign in to the [Azure portal](https://portal.azure.com) using an account with *global administrator* permissions.
62+
1. Sign-in to the [Azure portal](https://portal.azure.com) using an account with *global administrator* permissions.
6363
1. Search for and select **Azure Active Directory**, then choose **Security** from the menu on the left-hand side.
6464
1. Under the **Manage** menu header, select **Authentication methods** > **Policies**.
6565
1. From the list of available authentication methods, select **Text message**.
@@ -85,7 +85,7 @@ Each user that's enabled in the text message authentication method policy must b
8585

8686
## Set a phone number for user accounts
8787

88-
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](https://support.microsoft.com/account-billing/set-up-sms-sign-in-as-a-phone-verification-method-0aa5b3b3-a716-4ff2-b0d6-31d2bcfbac42) 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*.
88+
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](https://support.microsoft.com/account-billing/set-up-sms-sign-in-as-a-phone-verification-method-0aa5b3b3-a716-4ff2-b0d6-31d2bcfbac42) 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*.
8989

9090
When a phone number is set for SMS-sign, it's also then available for use with [Azure AD Multi-Factor Authentication][tutorial-azure-mfa] and [self-service password reset][tutorial-sspr].
9191

@@ -125,7 +125,7 @@ To test the user account that's now enabled for SMS-based sign-in, complete the
125125

126126
## Troubleshoot SMS-based sign-in
127127

128-
The following scenarios and troubleshooting steps can used if you have problems with enabling and using SMS-based sign in.
128+
The following scenarios and troubleshooting steps can used if you have problems with enabling and using SMS-based sign-in.
129129
For a list of apps that support using SMS-based sign-in, see [App support for SMS-based authentication](how-to-authentication-sms-supported-apps.md).
130130

131131

@@ -150,7 +150,7 @@ If you receive an error when you try to set a phone number for a user account in
150150
## Next steps
151151

152152
- For a list of apps that support using SMS-based sign-in, see [App support for SMS-based authentication](how-to-authentication-sms-supported-apps.md).
153-
- 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][concepts-passwordless].
153+
- 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][concepts-passwordless].
154154
- You can also use the Microsoft Graph REST API to [enable][rest-enable] or [disable][rest-disable] SMS-based sign-in.
155155

156156

0 commit comments

Comments
 (0)