Number matching

Number matching is an authentication approval step that asks a person to enter or select the number shown in the sign-in flow in their authenticator, instead of blindly approving a push notification.

A better prompt still needs a legitimate sign-in

Number matching makes a push approval more deliberate. In Microsoft’s usual flow, the sign-in page displays a number and Authenticator asks the user to enter it. It reduces the opportunity to accept repeated notifications without looking at the sign-in.

CISA recommends number matching as an interim mitigation for MFA fatigue when phishing-resistant MFA is not yet available. It does not give the same protection as phishing-resistant authentication.

A caller reading you a number has not proved they are your help desk. The important question is whether you initiated the sign-in for the service you meant to use. If you did not, approving the request is not a troubleshooting step. The unexpected MFA request guide covers that decision and what to report.

Check the actual application experience

Not every Microsoft approval looks identical. Microsoft documents supported same-device mobile app flows that use a Yes/No confirmation rather than asking the person to enter the number. Browser flows continue to use number entry.

Training should reflect the prompts people actually receive, without teaching that any familiar-looking prompt is safe. The recovery trust-boundaries article covers the separate risk of changing which authenticator can approve access in the first place.

Sources

See it in practice