A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
This usually happens when the sign-in is using a different Authenticator method than the one expected, or the notification is not reaching the device that is currently registered for approvals.
Based on the symptoms:
- The 6-digit code means the app is set up to generate an OATH verification code for the account.
- The sign-in prompt on microsoftonline.com is trying to use notification approval in Authenticator.
- If no prompt appears, the approval request may be going to a different device, the app may be locked, notifications may be delayed/silent, or the sign-in may require opening Authenticator and refreshing manually.
Try these steps in order:
- Open Authenticator manually during the sign-in
- When microsoftonline.com says to approve the request, open Microsoft Authenticator directly.
- If the sign-in is anomalous or the push does not appear automatically, pull down to refresh or tap Refresh, then look for the pending approval request.
- If prompted, unlock the app first.
- Check whether the request is going to an old phone
- If Authenticator was previously active on another device, the push notification may still be sent there.
- If the old device is still available, open Authenticator on that device and check for the approval request.
- Remove old devices so future prompts do not go there.
- Confirm notifications are actually usable, not just enabled
- In Authenticator, go to Settings > Notification Settings and make sure Show notifications is turned on.
- If the app is locked, the entry box may not appear until the app is unlocked.
- If notifications are silent or delayed, check whether a code arrived silently.
- Check app and device health
- Update Microsoft Authenticator to the latest version. Versions older than 12 months are not supported.
- Make sure the device date and time are correct.
- Switch between Wi‑Fi and mobile data.
- If using VPN, disconnect it and test again.
- Turn off battery optimization for Authenticator for better sync performance.
- Make sure the device OS and related security apps are up to date.
- Use another sign-in method if available
- On the sign-in page, select Other ways to sign in.
- Then choose another available method such as SMS or a verification code.
- This is the fastest workaround if push approval is failing.
- If the account only shows a 6-digit code and never receives approval prompts
- That indicates the account is available as a verification-code method, but notification approval may not be properly active for that account/device.
- For a work or school account, if the issue continues after the checks above, contact the IT admin/helpdesk so the MFA method can be reset or re-registered.
- Before escalating, capture logs from Authenticator using Send feedback from the app menu/settings.
If unexpected approval prompts ever appear, select Deny for any request that was not initiated.
References: