Use number matching in multifactor authentication (MFA) notifications - Azure Active Directory - Microsoft Entra (2023)

  • Article
  • 13 minutes to read

This topic covers how to enable number matching in Microsoft Authenticator push notifications to improve user sign-in security.

Note

Number matching is a key security upgrade to traditional second factor notifications in Microsoft Authenticator. We will remove the admin controls and enforce the number match experience tenant-wide for all users starting February 27, 2023.
We highly recommend enabling number matching in the near term for improved sign-in security.

Prerequisites

  • Your organization needs to enable Microsoft Authenticator (traditional second factor) push notifications for some users or groups by using the new Authentication methods policy. You can edit the Authentication methods policy by using the Azure portal or Microsoft Graph API.

  • If your organization is using AD FS adapter or NPS extensions, upgrade to the latest versions for a consistent experience.

Number matching

Number matching can be targeted to only a single group, which can be dynamic or nested. On-premises synchronized security groups and cloud-only security groups are supported for the Authentication methods policy.

Number matching is available for the following scenarios. When enabled, all scenarios support number matching.

  • Multifactor authentication
  • Self-service password reset
  • Combined SSPR and MFA registration during Authenticator app set up
  • AD FS adapter
  • NPS extension

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.

Multifactor authentication

When a user responds to an MFA push notification using the Authenticator app, they'll be presented with a number. They need to type that number into the app to complete the approval.

Use number matching in multifactor authentication (MFA) notifications - Azure Active Directory - Microsoft Entra (1)

SSPR

Self-service password reset (SSPR) with Microsoft Authenticator will require number matching when using Microsoft Authenticator. During self-service password reset, the sign-in page will show a number that the user will need to type into the Microsoft Authenticator notification. This number will only be seen by users who are enabled for number matching.

Combined registration

Combined registration with Microsoft Authenticator will require number matching. When a user goes through combined registration to set up the Authenticator app, the user is asked to approve a notification as part of adding the account. For users who are enabled for number matching, this notification will show a number that they need to type in their Authenticator app notification.

AD FS adapter

AD FS adapter will require number matching on supported versions of Windows Server. On earlier versions, users will continue to see the Approve/Deny experience and won’t see number matching until you upgrade. The AD FS adapter supports number matching only after installing one of the updates in the following table.

Note

Unpatched versions of Windows Server don't support number matching. Users will continue to see the Approve/Deny experience and won't see number matching unless these updates are applied.

VersionUpdate
Windows Server 2022November 9, 2021—KB5007205 (OS Build 20348.350)
Windows Server 2019November 9, 2021—KB5007206 (OS Build 17763.2300)
Windows Server 2016October 12, 2021—KB5006669 (OS Build 14393.4704)

NPS extension

Make sure you run the latest version of the NPS extension. Until February 27, 2023, users are asked to enter a One-Time Passcode (OTP) for push notifications beginning with NPS extension 1.2.2131.2 only if number matching is enabled. After February 27, 2023, number matching will be enabled by default and all users with push notifications beginning with NPS extension 1.2.2131.2 will be asked to enter an OTP.

The user must have an OTP authentication method registered to see this behavior. Common OTP authentication methods include the OTP available in Microsoft Authenticator, other software tokens, and so on. For OTP to work, the VPN needs to use PAP protocol. For more information, see Determine which authentication methods your users can use.

Note

If the user doesn't have an OTP method registered, they'll continue to get the Approve/Deny experience. A user who can't use an OTP will always see the Approve/Deny experience with push notifications triggered by a legacy NPS extension.

Earlier versions of the NPS extension beginning with 1.0.1.40 also support number matching, but you need to create a registry key that overrides push notifications to ask a user to enter an OTP. If you don't create the registry key, or you run a version prior to 1.0.1.40, users who are enabled for number matching will be prompted to Approve/Deny.

To create the registry key that overrides push notifications:

  1. On the NPS Server, open the Registry Editor.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureMfa.
  3. Set the following Key Value Pair:Key: OVERRIDE_NUMBER_MATCHING_WITH_OTPValue = TRUE
  4. Restart the NPS Service.

If you're using Remote Desktop Gateway and the user is registered for OTP code along with Microsoft Authenticator push notifications, the user won't be able to meet the Azure AD MFA challenge and Remote Desktop Gateway sign-in will fail. In this case, you can set OVERRIDE_NUMBER_MATCHING_WITH_OTP = FALSE to fall back to push notifications with Microsoft Authenticator.

Apple Watch supported for Microsoft Authenticator

In the upcoming Microsoft Authenticator release in January 2023 for iOS, there will be no companion app for watchOS due to it being incompatible with Authenticator security features. You won't be able to install or use Microsoft Authenticator on Apple Watch. We therefore recommend that you delete Microsoft Authenticator from your Apple Watch, and sign in with Microsoft Authenticator on another device.

Enable number matching in the portal

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

  1. In the Azure AD portal, click Security > Authentication methods > Microsoft Authenticator.

  2. On the Enable and Target tab, click Yes and All users to enable the policy for everyone or add selected users and groups. Set the Authentication mode for these users/groups to Any or Push.

    Only users who are enabled for Microsoft Authenticator here can be included in the policy to require number matching for sign-in, or excluded from it. Users who aren't enabled for Microsoft Authenticator can't see the feature.

    Use number matching in multifactor authentication (MFA) notifications - Azure Active Directory - Microsoft Entra (2)

  3. On the Configure tab, for Require number matching for push notifications, change Status to Enabled, choose who to include or exclude from number matching, and click Save.

    Use number matching in multifactor authentication (MFA) notifications - Azure Active Directory - Microsoft Entra (3)

Enable number matching using Graph APIs

Identify your single target group for the schema configuration. Then use the following API endpoint to change the numberMatchingRequiredState property under featureSettings to enabled, and include or exclude groups:

https://graph.microsoft.com/beta/authenticationMethodsPolicy/authenticationMethodConfigurations/MicrosoftAuthenticator

Note

In Graph Explorer, you'll need to consent to the Policy.Read.All and Policy.ReadWrite.AuthenticationMethod permissions.

MicrosoftAuthenticatorAuthenticationMethodConfiguration properties

PROPERTIES

PropertyTypeDescription
idStringThe authentication method policy identifier.
stateauthenticationMethodStatePossible values are: enabled
disabled

RELATIONSHIPS

RelationshipTypeDescription
includeTargetsmicrosoftAuthenticatorAuthenticationMethodTarget collectionA collection of users or groups who are enabled to use the authentication method
featureSettingsmicrosoftAuthenticatorFeatureSettings collectionA collection of Microsoft Authenticator features.

MicrosoftAuthenticator includeTarget properties

PROPERTIES

PropertyTypeDescription
authenticationModeStringPossible values are:
any: Both passwordless phone sign-in and traditional second factor notifications are allowed.
deviceBasedPush: Only passwordless phone sign-in notifications are allowed.
push: Only traditional second factor push notifications are allowed.
idStringObject ID of an Azure AD user or group.
targetTypeauthenticationMethodTargetTypePossible values are: user, group.

MicrosoftAuthenticator featureSettings properties

PROPERTIES

PropertyTypeDescription
numberMatchingRequiredStateauthenticationMethodFeatureConfigurationRequire number matching for MFA notifications. Value is ignored for phone sign-in notifications.
displayAppInformationRequiredStateauthenticationMethodFeatureConfigurationDetermines whether the user is shown application name in Microsoft Authenticator notification.
displayLocationInformationRequiredStateauthenticationMethodFeatureConfigurationDetermines whether the user is shown geographic location context in Microsoft Authenticator notification.

Authentication method feature configuration properties

PROPERTIES

PropertyTypeDescription
excludeTargetfeatureTargetA single entity that is excluded from this feature.
You can only exclude one group for number matching.
includeTargetfeatureTargetA single entity that is included in this feature.
You can only include one group for number matching.
StateadvancedConfigStatePossible values are:
enabled explicitly enables the feature for the selected group.
disabled explicitly disables the feature for the selected group.
default allows Azure AD to manage whether the feature is enabled or not for the selected group.

Feature target properties

PROPERTIES

PropertyTypeDescription
idStringID of the entity targeted.
targetTypefeatureTargetTypeThe kind of entity targeted, such as group, role, or administrative unit. The possible values are: ‘group’, 'administrativeUnit’, ‘role’, unknownFutureValue’.

Note

Number matching can be enabled only for a single group.

Example of how to enable number matching for all users

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

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.

Note

For passwordless users, enabling or disabling number matching has no impact because it's already part of the passwordless experience.

You might need to patch the entire schema to prevent overwriting any previous configuration. In that case, do a GET first, update only the relevant fields, and then PATCH. The following example only shows the update to the numberMatchingRequiredState under featureSettings.

Only users who are enabled for Microsoft Authenticator under Microsoft Authenticator’s includeTargets will see the number match requirement. Users who aren't enabled for Microsoft Authenticator won't see the feature.

//Retrieve your existing policy via a GET. //Leverage the Response body to create the Request body section. Then update the Request body similar to the Request body as shown below.//Change the Query to PATCH and Run query { "@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodConfigurations/$entity", "@odata.type": "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration", "id": "MicrosoftAuthenticator", "state": "enabled", "featureSettings": { "numberMatchingRequiredState": { "state": "enabled", "includeTarget": { "targetType": "group", "id": "all_users" }, "excludeTarget": { "targetType": "group", "id": "00000000-0000-0000-0000-000000000000" } } }, "includeTargets@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodsPolicy/authenticationMethodConfigurations('MicrosoftAuthenticator')/microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration/includeTargets", "includeTargets": [ { "targetType": "group", "id": "all_users", "isRegistrationRequired": false, "authenticationMode": "any", } ]} 

To confirm the change is applied, run the GET request by using the following endpoint:

GET https://graph.microsoft.com/beta/authenticationMethodsPolicy/authenticationMethodConfigurations/MicrosoftAuthenticator

Example of how to enable number matching for a single group

In featureSettings, you'll need to change the numberMatchingRequiredState value from default to enabled.Inside the includeTarget, you'll need to change the id from all_users to the ObjectID of the group from the Azure AD portal.To remove an excluded group from number matching, change the id of the excludeTarget to 00000000-0000-0000-0000-000000000000.

You need to PATCH the entire configuration to prevent overwriting any previous configuration. We recommend that you do a GET first, and then update only the relevant fields and then PATCH. The example below only shows the update to the numberMatchingRequiredState.

Only users who are enabled for Microsoft Authenticator under Microsoft Authenticator’s includeTargets will see the number match requirement. Users who aren't enabled for Microsoft Authenticator won't see the feature.

{ "@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodConfigurations/$entity", "@odata.type": "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration", "id": "MicrosoftAuthenticator", "state": "enabled", "featureSettings": { "numberMatchingRequiredState": { "state": "enabled", "includeTarget": { "targetType": "group", "id": "1ca44590-e896-4dbe-98ed-b140b1e7a53a" }, "excludeTarget": { "targetType": "group", "id": "00000000-0000-0000-0000-000000000000" } } }, "includeTargets@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodsPolicy/authenticationMethodConfigurations('MicrosoftAuthenticator')/microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration/includeTargets", "includeTargets": [ { "targetType": "group", "id": "all_users", "isRegistrationRequired": false, "authenticationMode": "any" } ]}

To verify, run GET again and verify the ObjectID:

GET https://graph.microsoft.com/beta/authenticationMethodsPolicy/authenticationMethodConfigurations/MicrosoftAuthenticator

FAQs

When will my tenant see number matching if I don't use the Azure portal or Graph API to roll out the change?

Number match will be enabled for all users of Microsoft Authenticator 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.

Will the changes on February 27th, 2023, override number matching settings that are configured for a group?

The Enable and Target tab of the Microsoft Authenticator authentication method policy will remain unchanged. Admins can continue to Target specific users and groups or All Users for Push or Any notifications. This change will only impact members of users and groups that are Targeted on the Enable and Target tab for Push and/or Any.

When Microsoft begins protecting all organizations by enabling number matching on February 27th, 2023, administrators will see the Require number matching for push notifications setting on the Configure tab of the Microsoft Authenticator policy is set to Enabled for All users and can't be disabled. In addition, the Exclude option for this setting will be removed.

How should users be prepared for default number matching?

Here are differences in sign-in scenarios that Microsoft Authenticator users will see after number matching is enabled by default:

  • Authentication flows will require users to do number match when using Microsoft Authenticator. If their version of Microsoft Authenticator doesn’t support number match, their authentication will fail.

  • Self-service password reset (SSPR) and combined registration will also require number match when using Microsoft Authenticator.

  • AD FS adapter will require number matching on supported versions of Windows Server. On earlier versions, users will continue to see the Approve/Deny experience and won’t see number matching until you upgrade.

  • NPS extension versions beginning 1.2.2131.2 will require users to do number matching. Because the NPS extension can’t show a number, the user will be asked to enter a One-Time Passcode (OTP). The user must have an OTP authentication method such as Microsoft Authenticator or software OATH tokens registered to see this behavior. If the user doesn’t have an OTP method registered, they’ll continue to get the Approve/Deny experience.

    To create a registry key that overrides this behavior and prompts users with Approve/Deny:

    1. On the NPS Server, open the Registry Editor.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureMfa.
    3. Set the following Key Value Pair:Key: OVERRIDE_NUMBER_MATCHING_WITH_OTPValue = FALSE
    4. Restart the NPS Service.
  • 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.

How can users enter an OTP with the NPS extension?

The VPN and NPS server must be using PAP protocol for OTP prompts to appear. If they're using a protocol that doesn't support OTP, such as MSCHAPv2, they'll continue to see the Approve/Deny notifications.

Will users get a prompt similar to a number matching prompt, but will need to enter an OTP?

They'll see a prompt to supply a verification code. They must select their account in Microsoft Authenticator and enter the random generated code that appears there.

Can I opt out of number matching?

Yes, currently you can disable number matching. We highly recommend that you enable number matching for all users in your tenant to protect yourself from MFA fatigue attacks. To protect the ecosystem and mitigate these threats, Microsoft will enable number matching for all tenants starting February 27, 2023. After protection is enabled by default, users can't opt out of number matching in Microsoft Authenticator push notifications.

Does number matching only apply if Microsoft Authenticator is set as the default authentication method?

If the user has a different default authentication method, there won't be any change to their default sign-in. If the default method is Microsoft Authenticator and they are members of groups targeted for Push or Any on the Enable and Target tab, they'll start to receive number matching approval on February 27th, 2023.

Regardless of their default method, any user who is prompted to sign-in with Authenticator will see number match after February 27th, 2023. If the user is prompted for another method, they won't see any change.

Will users who don't use number matching be able to perform MFA?

It depends on how the Enable and Target tab is configured. The scope for number match approvals will change under the Configure tab to include everyone, but it only applies for users and groups targeted on the Enable and Target tab for Push or Any. However, if Target on the Enable and Target tab is set to specific groups for Push or Any, and the user isn't a member of those groups, then they won't receive the number matching approvals once the change is implemented on February 27th, 2023 because they aren't a member of the groups defined on the Enable and Target tab for Push and/or Any.

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

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.

Why is my user prompted to tap on one out of three numbers instead of entering the number in their Microsoft Authenticator app?

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.

Next steps

Authentication methods in Azure Active Directory

Top Articles
Latest Posts
Article information

Author: Amb. Frankie Simonis

Last Updated: 03/30/2023

Views: 5835

Rating: 4.6 / 5 (76 voted)

Reviews: 91% of readers found this page helpful

Author information

Name: Amb. Frankie Simonis

Birthday: 1998-02-19

Address: 64841 Delmar Isle, North Wiley, OR 74073

Phone: +17844167847676

Job: Forward IT Agent

Hobby: LARPing, Kitesurfing, Sewing, Digital arts, Sand art, Gardening, Dance

Introduction: My name is Amb. Frankie Simonis, I am a hilarious, enchanting, energetic, cooperative, innocent, cute, joyous person who loves writing and wants to share my knowledge and understanding with you.