Mycelium 365 — Microsoft Solutions Partner Australia

    MFA Fatigue: What It Is and How to Stop It in Microsoft 365

    MFA fatigue (push bombing) tricks staff into approving a sign-in. See how it works and the Microsoft 365 settings that stop it.

    By

    Published · Updated

    7 minute read

    MFA fatigue, also called push bombing or prompt bombing, is an attack where someone who already has a staff member’s password sends sign-in approval requests again and again until the person taps “Approve” just to make them stop. In Microsoft 365 you can largely stop it with three things: number matching, phishing-resistant sign-in methods for your most important accounts, and Conditional Access. This guide explains how the attack works and how to check your settings in about five minutes.

    What is MFA fatigue?

    Multi-factor authentication asks for a second proof of identity after the password, often an approval prompt in an authenticator app. In an MFA fatigue attack, the attacker has the password, usually from phishing or a previous breach, and triggers a stream of prompts to the real user’s phone. The attack relies on people being busy, interrupted and wanting the notifications to stop. Attackers sometimes add a phone call or message pretending to be IT support and telling the person to approve the request.

    The technique has been used in high-profile breaches, including the 2022 Uber breach.

    How does an MFA fatigue attack work?

    1. The attacker obtains the user’s password, often through phishing or credentials leaked elsewhere.
    2. They sign in repeatedly, so the user’s phone fills with approval prompts.
    3. The user, annoyed or confused, approves one. Sometimes the attacker contacts them directly to urge it.
    4. The attacker is now signed in and can read email, access files or move on to other systems.

    Many incidents start with credential phishing, so stopping stolen passwords reduces the exposure.

    Why simple “Approve/Deny” prompts are risky

    A plain approve button gives the user no way to tell a real request from a fraudulent one, and approving takes one tap. That convenience is the weakness. Stronger methods make the user prove they are the one signing in, or remove the prompt altogether.

    How to stop MFA fatigue in Microsoft 365

    1. Use number matching and additional context

    With number matching, the sign-in screen shows a two-digit number and the user must type it into Microsoft Authenticator to approve. Someone who didn’t start the sign-in won’t know the number, so blind approval stops working. Additional context shows the application name and the sign-in location in the prompt, so a request from another country is obvious. Microsoft enforced number matching for Authenticator push notifications during 2023 and removed the ability to switch it off, so check that the additional context settings are on too.

    To check in about five minutes: sign in to the Microsoft Entra admin center (entra.microsoft.com), go to Protection → Authentication methods → Policies, open Microsoft Authenticator, and confirm that number matching, “Show application name” and “Show geographic location” are enabled for all users.

    2. Move your most important accounts to phishing-resistant sign-in

    Passkeys and FIDO2 security keys use cryptography that is tied to the real Microsoft sign-in page, so there is no prompt to approve and nothing for an attacker to bomb. If you can’t do this for everyone at once, start with the accounts that matter most: global administrators, finance and payroll approvers, and anyone with access to backups and security tools.

    3. Use Conditional Access and authentication strengths

    Microsoft Entra Conditional Access, included in plans with Entra ID P1 such as Business Premium, lets you require a stronger method for specific people. Microsoft includes three built-in authentication strengths: multi-factor authentication, passwordless, and phishing-resistant. A common approach is to require phishing-resistant sign-in for administrators and standard Authenticator sign-in with number matching for everyone else. Risk-based policies, which react to unusual sign-ins automatically, need Entra ID P2.

    4. Reduce the chance the password is stolen in the first place

    Train staff to recognise phishing, protect email with a modern filter, and block legacy sign-in methods that can’t use MFA. Fewer stolen passwords means fewer attacks that reach the prompt stage.

    5. Watch for the warning signs

    A burst of failed or denied MFA prompts for one user is a clear signal. Make sure someone is watching sign-in logs and alerts, and that staff know to report unexpected prompts instead of ignoring them. A managed security service can monitor this around the clock.

    6. Tell staff what to do

    Keep the rule simple: if you didn’t just try to sign in, tap Deny, and then tell IT. Never approve a prompt because someone on the phone or in a message asked you to.

    What to do if someone approved a fraudulent prompt

    1. Reset the user’s password and sign them out of all sessions.
    2. Check which sign-in methods are registered on the account and remove any you don’t recognise.
    3. Review recent sign-in activity, mailbox rules and file access for signs the attacker used the account.
    4. Check whether the same password is used elsewhere and reset those accounts too.
    5. If sensitive data may have been accessed, get advice on whether you have notification obligations.

    Where MFA fatigue fits in the Essential Eight

    Multi-factor authentication is one of the Essential Eight mitigation strategies, and the framework places a strong emphasis on phishing-resistant MFA at higher maturity levels. Moving from basic push approvals to number matching, and then to phishing-resistant methods for important accounts, is a practical path. See our Essential Eight compliance service.

    How Mycelium 365 can help

    Our Modern Workplace package includes Microsoft 365 administration, device management, 24/7 Security as a Service monitoring via Huntress SOC and cyber awareness training from $147 per user per month plus licensing, and we manage identity settings such as Conditional Access and authentication methods through our managed Entra service. Not sure where you stand? Start with a free Essential Eight baseline assessment, or Book a discovery call.

    Frequently Asked Questions

    MFA fatigue, also called push bombing, is an attack where someone with a stolen password sends repeated sign-in approval requests until the user approves one to stop the notifications.

    It makes it much harder. The user must type a number shown on the sign-in screen into Microsoft Authenticator, so someone who didn’t start the sign-in can’t approve it by accident. Phishing-resistant methods such as passkeys and FIDO2 keys remove the approval prompt entirely.

    Microsoft enforced number matching for Microsoft Authenticator push notifications during 2023 and removed the option to disable it. You should still check that “Show application name” and “Show geographic location” are enabled.

    It is a sign-in method that can’t be captured or replayed by an attacker’s fake login page. Passkeys, FIDO2 security keys and Windows Hello for Business are examples.

    Tap Deny, don’t approve anything because someone asks them to, and report it to IT immediately so the password can be reset and the account checked.

    Ready to simplify and secure your technology?

    Book a free, no-obligation Discovery Call to talk through your Microsoft 365, Azure, security, or support needs — no sales pitch, just a straight conversation.