How to Fix Authenticator App Code Not Working for Microsoft Account
If your Microsoft Authenticator code is not working, the cause is usually a sync issue, a time mismatch, or a setup problem with your Microsoft account.
This guide explains the most reliable fixes so you can get back into Outlook, Microsoft 365, Xbox, and other Microsoft services.
Most problems can be solved without resetting your phone, but a few Microsoft account settings can block sign-in until they are corrected.
The steps below focus on the fastest ways to identify the issue and restore one-time passcode verification.
Why Microsoft Authenticator Codes Fail
Microsoft Authenticator generates time-based one-time passwords, often called TOTP codes.
These codes only work for a short window, so even a small mismatch in time, account configuration, or app state can make them appear invalid.
- Incorrect device time on the phone running the app
- Out-of-date account registration after changing devices or reinstalling the app
- Network or sync issues that prevent the app from refreshing properly
- Using the wrong account entry when multiple Microsoft accounts are listed
- Expired or manually entered codes after the sign-in prompt has refreshed
Check the Time and Time Zone First
Time drift is one of the most common reasons an authenticator app code does not work for a Microsoft account.
If the phone clock is even slightly off, the code generated by the app will not match Microsoft’s verification window.
How to correct the time sync
- Open your phone’s Date and Time settings.
- Enable Set time automatically or the equivalent option.
- Enable Set time zone automatically if available.
- Restart the phone and open Microsoft Authenticator again.
After adjusting the clock, wait for a fresh code and try signing in again.
If the code still fails, move on to the account and app checks below.
Confirm You Are Using the Right Microsoft Account
Many users have more than one Microsoft account linked to the app, such as a personal Outlook.com account and a work or school account through Microsoft Entra ID.
Entering a code for the wrong account will cause the sign-in attempt to fail.
- Open Microsoft Authenticator and verify the exact account name shown on the tile.
- Match that account to the Microsoft sign-in screen.
- If you recently switched phones, confirm the account was restored from backup and not added twice.
If the account label looks unfamiliar, you may have an old or duplicate entry.
Removing stale entries and re-registering the current account can resolve repeated failures.
Update Microsoft Authenticator and Restart the App
An outdated app version can create problems with notifications, verification codes, and account syncing.
Updating the app often fixes issues caused by bugs or compatibility changes.
What to do
- Update Microsoft Authenticator from the Apple App Store or Google Play Store.
- Close the app completely and reopen it.
- Restart your device if the code still does not verify.
If you use Android, also check whether battery optimization is limiting the app in the background.
Aggressive battery settings can interfere with timely code generation and push approvals.
Make Sure the Code Has Not Expired
Microsoft Authenticator codes refresh frequently, and the current code may expire before you submit it.
This happens most often when a user pauses on the login page, switches apps, or types the code too slowly.
- Use the newest code displayed in the app.
- Enter it immediately after opening the sign-in prompt.
- Do not reuse a code from a previous attempt.
If the Microsoft login page refreshes, always generate a fresh code rather than trying the one you copied earlier.
Verify Internet Access and Background Permissions
Authenticator codes themselves do not require a constant data connection, but the app still depends on system permissions and occasional syncing.
If notifications or refresh behavior is broken, permissions may be the cause.
Check these settings
- Wi-Fi or mobile data is available
- Background app refresh is enabled on iPhone
- Battery optimization is not restricting the app on Android
- Notifications are allowed for Microsoft Authenticator
These settings matter most if you rely on push approvals, but they can also affect whether the app stays responsive and current.
Re-Add the Microsoft Account to the App
If time and app updates do not solve the problem, the account registration itself may be broken.
Re-adding the account often restores correct code generation and sign-in pairing.
Before removing the account
- Make sure you still have another sign-in method available.
- Check whether your Microsoft account has backup codes, alternate email, or phone verification.
- Save any recovery information you may need later.
Re-register the account
- Remove the Microsoft account from Authenticator.
- Sign in to your Microsoft account from a browser.
- Go to the security or two-step verification settings.
- Set up Microsoft Authenticator again by scanning the QR code or following the on-screen pairing steps.
This process refreshes the secure link between your account and the app, which is often the real fix when codes consistently fail.
Restore Access After Changing Phones
Phone changes are a frequent trigger for authenticator errors.
If you restored the app but the code does not work, the backup may not have transferred the active registration correctly.
- Open Microsoft Authenticator on the new device.
- Confirm that the correct account was restored from cloud backup.
- Check whether the Microsoft account needs to be reverified.
- Sign in using an alternate method if the app is no longer trusted.
On a new phone, Microsoft may require you to complete a fresh verification step before it accepts app-generated codes again.
Use Alternate Microsoft Account Recovery Options
If you cannot get the code accepted, use Microsoft’s recovery and fallback options to regain access.
Microsoft accounts typically provide alternate methods during sign-in, especially for security verification failures.
- Choose Use a different verification option on the sign-in screen.
- Use text message, email, or phone call verification if available.
- Check for backup recovery codes if you saved them earlier.
- Use account recovery through Microsoft’s official recovery form if you are locked out completely.
For work or school accounts, your organization may require help from an IT administrator or help desk to reset the MFA registration.
When to Remove and Recreate the Account
Sometimes the cleanest fix is to remove the Microsoft account from Authenticator and set it up again from scratch.
This is especially useful when the app shows the account, but every code is rejected.
Consider a full reset if:
- The code fails on every attempt, even after time sync is corrected
- You recently changed devices or restored from backup
- The account tile appears duplicated or outdated
- Microsoft asks you to verify identity but never accepts the app response
A re-enrollment clears stale registration data and gives Microsoft a new trusted device binding.
Prevent Future Microsoft Authenticator Problems
Once access is restored, a few habits can reduce the chance of the same problem happening again.
Small maintenance steps often prevent code failures before they start.
- Keep your phone time set automatically
- Update Microsoft Authenticator regularly
- Save backup recovery methods for your Microsoft account
- Review your security info after changing phones
- Keep at least one alternate verification method active
If you use Microsoft 365 for work, ask your administrator whether your organization supports backup methods or passwordless sign-in options.
Those features can make account recovery much easier later.
Signs the Problem Is Not the Code Itself
In some cases, the app is working and the real issue is the Microsoft sign-in flow.
That usually means the account is blocked, the verification challenge is stale, or the security settings need to be refreshed.
- The login page keeps looping back to verification
- The app code is accepted once, then fails on the next screen
- You are asked to approve a sign-in that never appears in the app
- Microsoft shows a security warning or unusual activity notice
When that happens, the best fix is often to reauthenticate the account, reset the verification method, or use Microsoft account recovery tools to rebuild trust between the app and the account.