A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
This usually happens for one of these reasons:
- The notification is being sent to an older phone where Authenticator was last used.
- Push notifications are disabled or blocked on the device.
- The phone has a network, time, battery optimization, VPN, or app-version issue.
- The Authenticator registration for the account is no longer valid, which can create a verification loop.
Try these steps in order:
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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:
- Microsoft Authenticator FAQs | Microsoft Support
- Troubleshoot problems with Microsoft Authenticator | Microsoft Support
- Authentication did not complete | Microsoft Support
- Stuck in Authenticator Loop after deleting account from authenticator - Microsoft Q&A
- Stuck in loop needing authenticator code to create new account in authenticator - Microsoft Q&A