Colour theme
Book a consultation

Responding to repeated MFA approval requests

Reject unexpected sign-in prompts, report them through a known route and review authentication methods and sessions with your IT team.

A hand holding a smartphone in an orange case above an open laptop keyboard.

Repeated sign-in approval requests can pressure someone into accepting a login they didn’t start. This is often called MFA fatigue or push bombing.

Make the expected response clear before it happens: don’t accept an unexpected request just to stop the notifications.

Recognize the request type

A push approval pops up on your phone and asks you to confirm a sign-in, often by entering a number shown on the sign-in screen. A text-message or app code is different: you type it in yourself. Attackers go after both, sometimes by phoning and asking for the code.

If you didn’t start the sign-in, deny the request and report it. Don’t give a caller any code or number from your screen.

If someone calls claiming to be IT support, hang up and call back on the number you already have for them.

Report what happened

Tell IT the account, approximate time, request type and whether you approved anything or shared a code. Don’t include passwords in the report.

If you’re locked out, reach IT another way, such as by phone. Prompts you didn’t start often mean someone has your password, so IT will want to check the sign-in logs and reset it.

If you approved a request, say so promptly. Don’t wait to see whether something else goes wrong.

Coordinate account recovery

IT should check recent sign-ins, active sessions, the MFA methods registered on the account and any recent changes, such as a new phone added as a sign-in method. Then reset the password and revoke existing sessions.

Changing a password doesn’t always end existing sessions or remove permissions granted to apps, so check those separately.

The email recovery guide covers additional checks when a mailbox is involved.

Review number matching

Microsoft’s Authenticator number-matching guidance explains the supported prompt behaviour, including differences for some same-device scenarios.

Microsoft Authenticator now uses number matching for all push notifications. It makes an accidental approval much harder. A user on a fake sign-in page can still enter the number the attacker relays to them, though, so it isn’t phishing-resistant.

Check how prompts look on the phones and apps your staff use, and cover that in training.

Evaluate phishing-resistant methods

Passkeys and security keys don’t send push prompts, so there’s nothing to flood. Plan enrolment, spare devices and recovery before rolling them out.

The passkey rollout guide covers those steps.

Check fallback methods so an attacker can’t simply choose a weaker route.

Keep sign-in controls and support usable

Single sign-on cuts the number of passwords staff manage, but it makes that one account more valuable to protect. Conditional Access rules, such as blocking sign-ins from countries where you don’t work, cut down attempts. They need an exception process for staff who travel.

Keep staff instructions short and make incident reporting easy. Practise an unexpected-prompt scenario with a harmless example and confirm that support can investigate it.


Featured Image Credit