Mfa cisco how to#

When a user goes through combined registration to set up Authenticator, the user needs to approve a notification to add the account.

Combined registrationĬombined registration with Authenticator requires number matching.

Mfa cisco how to#

For more information about how to set up SSPR, see Tutorial: Enable users to unlock their account or reset passwords. During self-service password reset, the sign-in page shows a number that the user needs to type into the Authenticator notification. Self-service password reset (SSPR) with Authenticator requires number matching when using Authenticator. For more information about how to set up MFA, see Tutorial: Secure user sign-in events with Azure AD Multi-Factor Authentication. They need to type that number into the app to complete the approval. When a user responds to an MFA push notification using Authenticator, they'll be presented with a number. Wearable device users need to use their phone to approve notifications when number matching is enabled. Number matching isn't supported for push notifications for Apple Watch or Android wearable devices. Combined SSPR and MFA registration during Authenticator app set up.

When enabled, all scenarios support number matching. Number matching is available for the following scenarios. Users can be enabled for Authenticator push notifications either in the Authentication methods policy or the legacy multifactor authentication policy if Notifications through mobile app is enabled. Number matching is a key security upgrade to traditional second factor notifications in Authenticator.īeginning May 8, 2023, number matching is enabled for all Authenticator push notifications.Īs relevant services deploy, users worldwide who are enabled for Authenticator push notifications will begin to see number matching in their approval requests. This topic covers how number matching in Microsoft Authenticator push notifications improves user sign-in security.