Share via

I keep getting multiple Authenticator notifications of someone trying to login to my account…it happens multiple times a day, everyday. How do I stop this?

Ralph Wakerly 0 Reputation points
2026-02-25T22:19:46.45+00:00

I keep getting multiple Authenticator notifications of someone trying to login to my account…it happens multiple times a day, everyday. How do I stop this?

Outlook | Web | Outlook.com | Account management, security, and privacy
0 comments No comments

3 answers

Sort by: Most helpful
  1. Hornblower409 9,200 Reputation points
    2026-02-27T15:49:00.4666667+00:00

    For detailed instructions on how to setup a Login Only Alias and disable Sign-In for your current email address:

    See the answer by "Hornblower409  Feb 27, 2026, 9:41 AM" in
    https://learn.microsoft.com/en-us/answers/questions/5789093/i-get-a-few-2fa-notifications-from-canada-daily-us

    Was this answer helpful?

    0 comments No comments

  2. Jeronimo Fuerte 39,850 Reputation points Independent Advisor
    2026-02-25T23:49:45.2133333+00:00

    Hi! Sorry to hear about this.

    Additionally, you can try changing the sign-in alias for your Microsoft account. You can manage which aliases are allowed to sign in here: https://account.live.com/SignInPreferences

    If you don’t currently have another alias available, you can add a new one here: https://account.live.com/names/manage

    I recommend not deleting your current alias, just add the new one and set it as the preferred sign-in. This can help improve account security, especially if your email address has been exposed publicly.

    Was this answer helpful?

    0 comments No comments

  3. AI answer

    2026-02-25T22:19:57.9133333+00:00

    Repeated Microsoft Authenticator prompts usually mean someone (or something like a script/app) is repeatedly trying to sign in as that account and is being blocked at the MFA step.

    To stop this and secure the account:

    1. Do not approve any unexpected prompts
      • Never approve notifications that were not initiated personally.
      • Never read verification codes to anyone who contacts by phone, text, or email.
    2. Review recent sign-in activity
      • Go to the Security basics page.
      • Select Review activity and check the Recent activity and Unusual activity sections.
      • For any sign-in that is not recognized:
        • If it is in Unusual activity, expand it and select This wasn’t me.
        • If it is in Recent activity, expand it and select Secure your account.
    3. Change the account password
      • From the same Security basics page, select Change password.
      • Set a strong, unique password that is not reused on other sites.
    4. Ensure multifactor authentication (MFA) is correctly configured
      • Keep Microsoft Authenticator enabled and working.
      • If SMS or email codes are also configured, consider whether they are still needed; unused or weaker methods can be removed once fully secured.
    5. Consider going passwordless
      • To reduce reliance on passwords (which can be guessed, stolen, or phished), switch to passwordless sign-in methods such as Microsoft Authenticator, Windows Hello, SMS/Email codes, or security keys. See Go passwordless for details.
    6. If the attempts continue at high volume
      • Treat this as a sustained attack.
      • Continue to deny all prompts and monitor Recent activity regularly.
      • If this is a work or school account, contact the organization’s IT admin so they can review Microsoft Entra sign-in logs and adjust security policies if needed.

    As long as unrequested prompts are not approved and verification codes are not shared, the account remains protected, but the steps above help both stop the prompts and harden the account against future attacks.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.