Microsoft Authenticator Doesn't Fucking Work

Rivinius, Scott 5 Reputation points
2026-08-18T01:29:03.9166667+00:00

This garbage app has me in an endless loop. I am trying to register my account in the app on an Android. I am able to put in my account and password but then it prompts me to enter the code displayed on my Authenticator which can't happen because I haven't registered it in Authenticator yet. The "sign in another way" feature is all through the Authenticator. I'm in an endless loop. My notifications are on. I had to use another one of my account's to post this since trying to sign in to get help required me to get a code from Authenticator, which I can't get into....

Microsoft Security | Microsoft Authenticator

1 answer

Sort by: Most helpful
  1. AI answer

    2026-08-18T01:29:23.0666667+00:00

    This is usually an Authenticator sign-in loop caused by one of these conditions:

    1. The approval request is being sent to an older device where Authenticator was last active.
    2. No alternate verification method was set up, so every fallback still routes back to Authenticator.
    3. The app or device is not in a good state for push approval.

    Try these steps in order:

    1. On the sign-in screen, select Other ways to sign in or Sign in another way.
      • If available, choose Approve a request on my Microsoft Authenticator app, SMS, phone, or email instead of the current looping path.
      • If no non-Authenticator option appears, there may be no alternate method registered.
    2. Check whether the notification is going to a different device.
      • If Authenticator was previously active on an older phone, the push may be sent there instead of the current Android device.
      • If the old phone is still available, open Authenticator there and approve the sign-in.
    3. On the Android device, verify the app can actually receive and complete prompts.
      • Open Microsoft Authenticator directly and make sure it opens normally and the account is listed.
      • If using a work or school account, unlock Authenticator before confirming sign-in.
      • In Authenticator, check Settings > Notification Settings and confirm Show notifications is turned on.
      • In Authenticator Settings, select Turn off battery optimization.
    4. Check device and connectivity conditions.
      • Switch between Wi‑Fi and mobile data.
      • Make sure Airplane mode is off.
      • If using a VPN, disconnect it and test again.
      • Confirm the device Date & time are correct and preferably automatic.
    5. Update and restart.
      • Update Microsoft Authenticator from the app store.
      • On work or school devices, also update Company Portal and ensure the device is compliant.
      • Restart the phone and try again.
    6. If the app shows Authentication did not complete:
      • Make sure the app is unlocked.
      • Confirm notifications are enabled and not silent.
      • Retry after switching networks and confirming date/time.
    7. If this is a work or school account and the loop continues:
      • The organization’s IT admin should reset the account’s authentication methods by revoking sessions and requiring re-registration of multifactor authentication.
      • Before setting it up again, remove the existing account from the Authenticator app.
    8. If this is a personal Microsoft account and no alternate verification method works:
      • Use another verification option if offered.
      • If the issue persists, send logs from Authenticator using Send feedback from the app menu, then contact Support for personal accounts.

    A special case applies on Android in China: push notifications for Notification through mobile app do not work because Google Play services are blocked there. In that case, an alternate authentication method is required.


    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.