How to Fix Microsoft Authenticator Code Not Working in 2026
If you are trying to sign in and the Microsoft Authenticator code is not working, the issue is usually tied to time drift, account setup, or a syncing problem.
The good news is that most failures can be fixed quickly without losing access to your Microsoft account or work login.
Why Microsoft Authenticator codes stop working
Microsoft Authenticator generates time-based one-time passwords (TOTP) for personal Microsoft accounts, work accounts in Microsoft Entra ID, and many third-party services.
These codes are short-lived, so even a small mismatch can make them invalid.
- Time is out of sync on the phone or server.
- The account was re-added or set up incorrectly in the app.
- You are using the wrong account entry in Microsoft Authenticator.
- Device changes affected app data, notifications, or security settings.
- Company policies require sign-in approval instead of a six-digit code.
Check the time and time zone first
Time drift is the most common reason a Microsoft Authenticator code fails.
Authenticator codes depend on the current time, so even a small mismatch can cause repeated errors.
On iPhone
- Open Settings.
- Tap General and then Date & Time.
- Turn on Set Automatically.
On Android
- Open Settings.
- Go to System or General management.
- Open Date & time.
- Enable Use network-provided time and Use network-provided time zone.
If the code still fails after this change, restart the phone and try again after the next code refresh.
A fresh network sync often resolves the mismatch.
Make sure you are using the correct account entry
Many users have more than one Microsoft or school/work account in the app.
It is easy to enter the code from the wrong tile, especially if the account names look similar.
- Open Microsoft Authenticator and confirm the account label.
- Match the code to the service asking for it.
- If you recently changed jobs, schools, or phones, remove old account entries you no longer use.
For work or school accounts, the entry may be for Microsoft Entra ID rather than a personal Microsoft account.
The code must correspond to the exact account that is prompting you to sign in.
Confirm that the code is still valid
Microsoft Authenticator codes expire quickly, usually within 30 seconds.
Entering a code too late is a common reason for failure, especially when switching between apps or dealing with a slow network.
- Wait for the code to refresh fully before typing it.
- Enter the code immediately after it appears.
- Do not reuse an older code after the countdown changes.
If the app supports copying the code, paste it carefully and make sure there are no extra spaces.
Resync the account in Microsoft Authenticator
Some Microsoft account issues are caused by a temporary sync problem between the app and the cloud.
Resyncing can restore the correct secret key and reduce code mismatches.
For personal Microsoft accounts
- Sign in to your Microsoft account security page.
- Review your two-step verification settings.
- Remove the old authenticator registration if it appears broken, then set it up again.
For work or school accounts
- Open the Microsoft Authenticator app.
- Check whether the account needs to be re-verified.
- Contact your organization’s IT administrator if the code is rejected repeatedly.
In many enterprise environments, the code is only one part of the authentication policy.
Conditional Access, device compliance, or MFA registration status can also block sign-in.
Fix notification and account permission issues
Although this article focuses on code problems, Microsoft Authenticator often uses push approval as a fallback.
If notifications are disabled or permissions are restricted, the app may appear broken even when the code is available.
- Allow notifications for Microsoft Authenticator.
- Disable battery optimization for the app on Android if it is being restricted.
- Make sure background app refresh is enabled on iPhone.
- Check that the app has permission to use the camera if you need to scan a QR code again.
Notification issues do not directly corrupt the code, but they can prevent you from re-registering or confirming an account after a sync problem.
Remove and re-add the account if the code keeps failing
If time sync and account checks do not help, the safest next step is to remove the affected account and add it again.
This rebuilds the secret used to generate the code.
Before removing anything, make sure you have another sign-in method available, such as a backup phone number, recovery code, email address, or secondary authentication app.
Losing all methods can lock you out temporarily.
Best practice before re-adding
- Save backup codes for the account.
- Confirm that the service allows re-registration from another device.
- Check whether your employer requires IT approval before enrolling a new authenticator.
After re-adding the account, test the code immediately while the registration page is still open, if possible.
Clear app cache or reinstall Microsoft Authenticator
Corrupted local data can cause persistent code errors.
Clearing the cache on Android or reinstalling the app on either platform can restore normal behavior.
Android
- Open Settings.
- Go to Apps and select Microsoft Authenticator.
- Tap Storage.
- Choose Clear cache first.
If needed, reinstall the app.
iPhone
- Delete the app.
- Reinstall Microsoft Authenticator from the App Store.
- Sign in again and restore accounts if backup is enabled.
Reinstalling may remove locally stored data, so check whether cloud backup is enabled before you begin.
Check for server-side or policy-related issues
Sometimes the code is fine, but the account cannot accept it because the authentication system is having a wider issue.
This is more common with Microsoft Entra ID, Azure AD-integrated services, and organizations using strict identity policies.
- Review Microsoft service health if you are an admin.
- Ask whether MFA registration has changed recently.
- Confirm that your account is not blocked by Conditional Access rules.
- Verify that passwordless sign-in has not replaced code-based verification.
If coworkers are also affected, the problem is likely on the service side rather than on your device.
Use recovery options when you are locked out
If Microsoft Authenticator code not working problems prevent you from signing in, switch to another recovery path immediately.
Microsoft account recovery and organizational help desks are designed for this situation.
- Use backup codes if you saved them earlier.
- Try SMS or email verification if those methods are enabled.
- Use a previously registered alternate device.
- Contact your organization’s IT support for MFA reset.
For work accounts, an administrator may need to reset your multifactor authentication methods before you can enroll Microsoft Authenticator again.
How to prevent Microsoft Authenticator code issues in the future
A few habits reduce the chances of authentication failures:
- Keep automatic time enabled on your phone.
- Register at least one backup sign-in method.
- Back up Microsoft Authenticator if the feature is available in your version.
- Update the app regularly from the App Store or Google Play.
- Review your account setup after switching phones or resetting the device.
These steps help preserve access across device upgrades, app reinstallations, and policy changes.
They also make it easier to recover quickly if Microsoft Authenticator stops producing valid codes again.
When to contact support
Reach out for help if the code still fails after time sync, account verification, re-registration, and reinstalling the app.
Persistent failures can indicate a registration problem, an organizational policy change, or a corrupted account record that only support can fix.
- Personal Microsoft account: use Microsoft account recovery and security support.
- Work or school account: contact your IT help desk or Microsoft Entra administrator.
Having your device model, operating system version, and account type ready will make troubleshooting faster and more precise.