Microsoft authenticator stuck in a loop

Bethany Lowe 0 Reputation points
2026-11-19T10:23:42.2466667+00:00

Instructed to verify access from a website via microsoft authenticator app.

The app is receiving no notifications.

I try to reset the app or sign in via another account via the microsoft authenticator app and it again tells me to verify it via the app, the app that I'm already in and not receiving anything for.

Unable to find any support for issues of the same nature.

Microsoft Security | Microsoft Authenticator
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-19T10:24:00.2433333+00:00

    This usually happens for one of these reasons:

    1. The notification is being sent to an older phone where Authenticator was last used.
    2. Push notifications are disabled or blocked on the device.
    3. The phone has a network, time, battery optimization, VPN, or app-version issue.
    4. The Authenticator registration for the account is no longer valid, which can create a verification loop.

    Try these steps in order:

    1. Check for an old device
      • If Authenticator was previously active on another phone, the approval prompt may be going there instead.
      • If that old phone is still available, open Authenticator there and approve the sign-in.
      • If another verification method such as SMS is offered, use that instead.
    2. Verify notification settings on the current phone
      • Make sure the phone is not in Do Not Disturb or Quiet mode.
      • In Authenticator, go to Settings > Notification Settings and make sure Show notifications is turned on.
      • If the app shows an error like Enable push notifications to receive alerts, enable push notifications in the device settings and confirm network connectivity.
    3. Check connectivity and device basics
      • Switch between mobile data and Wi‑Fi.
      • Make sure Airplane mode is off.
      • If using a VPN, disconnect it and test again.
      • Make sure the device Date & time is correct and set automatically, then restart the device.
    4. Update the app and device
      • Make sure Authenticator is on the latest version. Versions older than 12 months are not supported.
      • Make sure the device OS and any related security apps are up to date.
      • In Authenticator Settings, turn on App updates.
      • In Settings, select Turn off battery optimization for better sync performance.
    5. If notifications still do not arrive
      • If some accounts in Authenticator receive notifications but one account does not, remove the problematic account from the app and add it again, allowing notifications.
      • If the app shows We could not complete the sign-in at this time, or Something went wrong. [4s8qz], retry after a few moments, update the app, and restart the device.
    6. If this is a work or school account and the loop continues
      • This often requires the organization’s IT admin to reset MFA or require re-registration of Authenticator.
      • For work/school accounts, if the registration was removed or is broken, this is not fully fixable from the app alone.
    7. Capture logs before escalating
      • Open Authenticator, go to the app’s top-level menu, and select Send feedback to send logs for diagnostics.
      • For personal accounts, contact Support after sending logs.
      • For work/school accounts, send logs and then contact the IT admin.

    If the account was deleted from Authenticator or the app was reset and the sign-in still demands approval from the same app, the most likely cause is a broken MFA registration. In that case, the next step is an MFA reset or re-registration by the IT admin for work/school accounts.


    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.