Skip to content

Commit 883c5ac

Browse files
committed
fixed acrolinx
1 parent 281343f commit 883c5ac

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Number matching is available for the following scenarios. When enabled, all scen
4343
>[!NOTE]
4444
>For passwordless users, enabling or disabling number matching has no impact because it's already part of the passwordless experience.
4545
46-
Number matching is available for sign in for Azure Government. It is available for combined registration two weeks after General Availability. Number matching isn't supported for Apple Watch notifications. Apple Watch users need to use their phone to approve notifications when number matching is enabled.
46+
Number matching is available for sign-in for Azure Government. It's available for combined registration two weeks after General Availability. Number matching isn't supported for Apple Watch notifications. Apple Watch users need to use their phone to approve notifications when number matching is enabled.
4747

4848
### Multifactor authentication
4949

@@ -163,7 +163,7 @@ https://graph.microsoft.com/beta/authenticationMethodsPolicy/authenticationMetho
163163

164164
In **featureSettings**, you'll need to change the **numberMatchingRequiredState** from **default** to **enabled**.
165165

166-
The value of Authentication Mode can be either **any** or **push**, depending on whether or not you also want to enable passwordless phone sign-in. In these examples, we will use **any**, but if you don't want to allow passwordless, use **push**.
166+
The value of Authentication Mode can be either **any** or **push**, depending on whether or not you also want to enable passwordless phone sign-in. In these examples, we'll use **any**, but if you don't want to allow passwordless, use **push**.
167167

168168
>[!NOTE]
169169
>For passwordless users, enabling or disabling number matching has no impact because it's already part of the passwordless experience.
@@ -354,7 +354,7 @@ To enable number matching in the Azure AD portal, complete the following steps:
354354

355355
## FAQs
356356

357-
### When will my tenant see number matching if I do not use the Azure portal or Graph API to roll out the change?
357+
### When will my tenant see number matching if I don't use the Azure portal or Graph API to roll out the change?
358358

359359
Number match will be enabled for all users of Microsoft Authenticator app after February 27, 2023. Relevant services will begin deploying these changes after February 27, 2023 and users will start to see number match in approval requests. As services deploy, some may see number match while others don't. To ensure consistent behavior for all your users, we highly recommend you use the Azure portal or Graph API to roll out number match for all Microsoft Authenticator users.
360360

@@ -364,7 +364,7 @@ Yes, currently you can disable number matching. We highly recommend that you ena
364364

365365
### What about my Apple Watch?
366366

367-
Apple Watch will remain unsupported for number matching. We recommend you uninstall the Microsoft Authenticator Apple Watch app because you will have to approve notifications on your phone.
367+
Apple Watch will remain unsupported for number matching. We recommend you uninstall the Microsoft Authenticator Apple Watch app because you have to approve notifications on your phone.
368368

369369
### What happens if a user runs an older version of Microsoft Authenticator?
370370

0 commit comments

Comments
 (0)