A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
This is usually an Authenticator sign-in loop caused by one of these conditions:
- The approval request is being sent to an older device where Authenticator was last active.
- No alternate verification method was set up, so every fallback still routes back to Authenticator.
- The app or device is not in a good state for push approval.
Try these steps in order:
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Microsoft Authenticator FAQs
- Sign in using Microsoft Authenticator
- Troubleshoot problems with Microsoft Authenticator
- Authentication methods in Microsoft Entra ID - Microsoft Authenticator app
- Authentication did not complete
- I am stuck in authenticator loop for my business account - Microsoft Q&A
- I have authentication issue with Microsoft Authenticator (authenticator asking for authentication). - Microsoft Q&A