How to Fix Microsoft Authenticator Not Working
If Microsoft Authenticator is failing to approve sign-ins, generating wrong codes, or refusing to open, the cause is usually tied to a device setting, account sync issue, or outdated app data.
This guide explains how to fix Microsoft Authenticator not working with clear steps you can try on Android and iPhone.
Because the app supports multi-factor authentication for Microsoft 365, Outlook, Azure AD, and many third-party accounts, a small configuration problem can interrupt access fast.
The good news is that most issues can be resolved without resetting your entire account.
Why Microsoft Authenticator stops working
Microsoft Authenticator depends on several moving parts: the app itself, your phone’s clock, push notification permissions, network access, and the identity provider behind the account.
When one of those pieces changes, authentication prompts can fail or codes can become invalid.
- App corruption after an update
- Incorrect date and time on the device
- Disabled notifications or background refresh
- Outdated app version
- Account sync problems after changing phones
- Corrupted cached data on Android
- Sign-in policy changes from Microsoft Entra ID or your organization
Check the basics first
Start with the simplest causes before moving into account recovery.
These checks solve a large share of Microsoft Authenticator problems.
Verify the phone’s date and time
Authenticator codes are time-based, so even a small clock mismatch can break verification.
Set the device to automatic date and time, then reopen the app.
- iPhone: Settings > General > Date & Time > Set Automatically
- Android: Settings > System > Date & Time > Use network-provided time
Confirm internet access
Push approvals need a working connection.
Switch between Wi-Fi and mobile data to see whether the issue is network-related.
If you are on a corporate network, a firewall or VPN may be blocking sign-in traffic.
Restart the phone
A simple restart clears temporary app and system issues.
If notifications were delayed or the app was unresponsive, rebooting often restores normal behavior immediately.
Fix notification and push approval problems
One of the most common complaints is that Microsoft Authenticator is installed, but approval requests never appear.
This is usually a notification or battery-management issue, not an account failure.
Enable notifications for Microsoft Authenticator
Make sure notifications are allowed at the operating-system level and inside the app.
- iPhone: Settings > Notifications > Microsoft Authenticator > Allow Notifications
- Android: Settings > Apps > Authenticator > Notifications > Allow
Disable battery optimization for the app
Android power-saving features can stop background push messages.
Exclude Microsoft Authenticator from battery optimization or adaptive battery controls if approvals arrive late or not at all.
Check Focus mode or Do Not Disturb
On iPhone, Focus mode can hide alerts.
On Android, Do Not Disturb or notification channels may suppress prompts.
Temporarily turn these features off while testing sign-in.
Update Microsoft Authenticator
An outdated version can cause sign-in issues, especially after Microsoft changes authentication behavior or adds new features.
Open the App Store or Google Play Store and install any pending update.
After updating, force close the app and reopen it before trying again.
This helps refresh the session and load the latest configuration.
Clear cache or reinstall the app
If the app opens but codes are wrong, accounts are missing, or the interface is glitchy, local app data may be damaged.
The fix depends on your device platform.
On Android
You can clear the app cache first, then reinstall if needed.
- Settings > Apps > Authenticator > Storage
- Tap Clear cache
- If the problem continues, uninstall and reinstall the app
On iPhone
iOS does not offer the same cache-clearing options, so reinstalling the app is the usual next step.
Before you remove it, confirm that your accounts are backed up or that you can re-register them after reinstalling.
When reinstalling, sign in again and restore any available backup if your setup supports it.
Fix account sync and backup issues
If you changed phones or reset your device, Microsoft Authenticator may not restore all accounts automatically.
Whether recovery works depends on the account type and whether cloud backup was enabled.
Check whether backup was enabled
For personal Microsoft accounts, backup and recovery can help restore credentials.
For work or school accounts, the organization’s policies may require re-registration on the new device.
- Open Authenticator settings
- Look for backup or cloud sync options
- Sign in with the same Microsoft account used for backup
Re-add accounts if they are missing
If accounts disappeared after migration, scan the QR code again or follow your organization’s instructions to re-register MFA.
Some services require generating a new secret key rather than restoring an old one.
When codes are valid but still rejected
If the app shows a code, but the website or service refuses it, the issue may be with the specific account rather than the app.
This often happens when the time is out of sync, the account has been revoked, or a stale token is stored in the browser.
- Check the device clock again
- Sign out of the browser and sign back in
- Try a private or incognito window
- Clear saved passwords for the affected site
- Verify that the correct account is selected in Authenticator
Work and school account problems
In Microsoft Entra ID environments, your organization may enforce conditional access, device compliance, or passwordless sign-in settings.
If Microsoft Authenticator stops working for a work account, the problem may be policy-based rather than app-based.
Common enterprise causes
- The account was removed from MFA registration
- Device compliance checks failed
- Admin policy changed authentication methods
- The company disabled push approvals temporarily
- The phone was replaced without re-registering the account
If you use a corporate account, ask your IT administrator whether your authentication method needs to be reset in Microsoft Entra admin center or re-enrolled through the company portal.
How to recover access if you are locked out
If Microsoft Authenticator is your only sign-in method and it no longer works, use any backup method you previously configured.
Common alternatives include SMS, email verification, phone call verification, or recovery codes.
- Use backup authentication methods on the sign-in page
- Check whether recovery codes were saved securely
- Contact your organization’s help desk for an MFA reset
- Use account recovery workflows for Microsoft personal accounts
If no backup method exists, you may need support intervention to verify your identity and re-register the device.
Prevent Microsoft Authenticator from breaking again
Once the app is working again, a few habits can reduce future problems.
These preventive steps are especially useful if you rely on the app for Microsoft 365, Azure, GitHub, or banking logins.
- Keep the app updated
- Leave automatic date and time enabled
- Allow notifications and background activity
- Set up a second authentication method
- Back up or document recovery options before changing phones
- Review company MFA policies after device upgrades
Common signs the problem is fixed
You will usually know the issue is resolved when approval prompts arrive immediately, the six-digit code changes every 30 seconds as expected, and sign-ins no longer fail with verification errors.
If one account still fails while others work, focus on that account’s registration status rather than the app itself.
When to contact support
If you have already checked the clock, network, notifications, updates, and reinstall options, the remaining issue may involve account policy or server-side registration.
Contact Microsoft support, your employer’s IT team, or the service provider that uses Authenticator if the app is still not working after re-enrollment attempts.