You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/how-to-mfa-number-match.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Number matching is available for the following scenarios. When enabled, all scen
43
43
>[!NOTE]
44
44
>For passwordless users, enabling or disabling number matching has no impact because it's already part of the passwordless experience.
45
45
46
-
Number matching is available for signin 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.
In **featureSettings**, you'll need to change the **numberMatchingRequiredState** from **default** to **enabled**.
165
165
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**.
167
167
168
168
>[!NOTE]
169
169
>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:
354
354
355
355
## FAQs
356
356
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?
358
358
359
359
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.
360
360
@@ -364,7 +364,7 @@ Yes, currently you can disable number matching. We highly recommend that you ena
364
364
365
365
### What about my Apple Watch?
366
366
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.
368
368
369
369
### What happens if a user runs an older version of Microsoft Authenticator?
0 commit comments