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
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to use number matching in MFA notifications
4
4
ms.service: active-directory
5
5
ms.subservice: authentication
6
6
ms.topic: conceptual
7
-
ms.date: 02/09/2023
7
+
ms.date: 02/10/2023
8
8
ms.author: justinha
9
9
author: justinha
10
10
ms.collection: M365-identity-device-management
@@ -366,13 +366,15 @@ Regardless of their default method, any user who is prompted to sign-in with Aut
366
366
367
367
No, number matching isn't enforced because it's not a supported feature for MFA Server, which is [deprecated](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-september-2022-train/ba-p/2967454).
368
368
369
-
### What happens if a user runs an older version of Microsoft Authenticator?
369
+
### What happens if a user runs an older version of Microsoft Authenticator?
370
370
371
-
If a user is running an older version of Microsoft Authenticator that doesn't support number matching, authentication won't work if number matching is enabled. Users need to upgrade to the latest version of Microsoft Authenticator to use it for sign-in.
371
+
If a user is running an older version of Microsoft Authenticator that doesn't support number matching, authentication won't work if number matching is enabled. Users need to upgrade to the latest version of Microsoft Authenticator to use it for sign-in if they use Android versions prior to 6.2006.4198, or iOS versions prior to 6.4.12.
372
372
373
-
### Why is my user prompted to tap on one out of three numbers instead of entering the number in their Microsoft Authenticator app?
373
+
### Why is my user prompted to tap on one of three numbers rather than enter the number in their Microsoft Authenticator app?
374
374
375
-
Older versions of Microsoft Authenticator prompt users to tap and select a number instead of entering the number in their Microsoft Authenticator app. These authentications won't fail, but we highly recommend that users update to the latest version of the app to be able to enter the number.
375
+
Older versions of Microsoft Authenticator prompt users to tap and select a number rather tha enter the number in their Microsoft Authenticator app. These authentications won't fail, but we highly recommend that users update to the latest version of the app to be able to enter the number.
376
+
377
+
Older versions of Microsoft Authenticator prompt users to tap and select a number rather than enter the number in Microsoft Authenticator. These authentications won't fail, but Microsoft highly recommends that users upgrade to the latest version of Microsoft Authenticator if they use Android versions prior to 6.2108.5654, or iOS versions prior to 6.5.82, so they can use number match.
0 commit comments