If Outlook is refusing your verification code, the problem is usually not your account itself but a mismatch between Microsoft authentication settings, device time, app versions, or account registration.
This guide explains how to fix two factor authentication not working on Outlook with practical steps you can apply on Outlook.com, the Outlook desktop app, and mobile devices.
Why Outlook two-factor authentication fails
Outlook uses Microsoft account security systems, including two-step verification, Microsoft Authenticator, SMS codes, email codes, and app-based sign-in prompts.
When any part of that chain breaks, you may see repeated sign-in prompts, invalid code errors, or a verification request that never arrives.
- Outdated Outlook or Microsoft Authenticator app versions
- Incorrect device date and time settings
- Network restrictions blocking Microsoft services
- Old cached credentials in the Outlook profile
- Account recovery settings that are incomplete or outdated
- Browser cookies or extensions interfering with Outlook sign-in
Check whether the issue is the account or the app
Before changing settings, determine where the failure happens.
Sign in to your Microsoft account through a browser at Outlook.com or account.microsoft.com.
If verification works there but not in the desktop or mobile app, the issue is likely local to that device or app profile.
If verification fails everywhere, focus on account security settings, recovery methods, and authentication method registration.
That distinction saves time and helps you avoid unnecessary resets.
How to fix two factor authentication not working on Outlook
1. Verify the device date and time
Time-based codes depend on synchronized clocks.
If your phone, tablet, or computer has the wrong time zone or an incorrect clock, Microsoft Authenticator and similar verification methods may reject valid codes.
- Enable automatic date and time on Windows, iPhone, or Android.
- Confirm the correct time zone is selected.
- Restart the device after changing time settings.
2. Update Outlook and Microsoft Authenticator
Microsoft frequently updates authentication behavior, so older app builds can fail during sign-in.
Install the latest version of Outlook and, if you use it, Microsoft Authenticator from the Microsoft Store, Apple App Store, or Google Play Store.
After updating, fully close the app and reopen it.
If the app still requests repeated verification, sign out and sign back in to refresh the session.
3. Confirm the correct verification method is selected
Many Outlook sign-in problems happen because the account is expecting one verification method while the user is trying another.
For example, Microsoft may be sending an Authenticator prompt when you are looking for a text message code.
- Check whether your account uses Microsoft Authenticator, SMS, email, or phone call verification.
- Open the registered device that receives the prompt.
- Approve the request only if it matches your sign-in attempt.
4. Remove old cached sign-in data
Outlook desktop and mobile apps can store outdated tokens that conflict with two-step verification.
Clearing the cache or removing the saved account often resolves repeated prompts.
- In Outlook for Windows, remove and re-add the account in the profile if needed.
- In the browser, clear cookies for Microsoft and Outlook domains.
- On mobile, clear the app cache or reinstall Outlook if the sign-in loop continues.
5. Check your internet connection and security software
A weak network or aggressive firewall can block Microsoft authentication endpoints.
Public Wi-Fi, VPNs, DNS filtering, and antivirus web shields may prevent verification pages or push prompts from loading correctly.
- Try a different network, such as mobile data or another Wi-Fi connection.
- Disable VPN temporarily and test again.
- Allow Outlook, Microsoft account services, and Microsoft Authenticator through firewall or security software.
6. Use a browser session to reset the sign-in flow
If the Outlook desktop app is stuck in a verification loop, sign in through a browser first.
A successful browser session can refresh the account’s authentication state and make the desktop app behave normally afterward.
- Open a private or incognito browser window.
- Sign in to Outlook.com using your Microsoft account.
- Complete the second-factor prompt.
- Reopen Outlook desktop and test sign-in again.
7. Regenerate or re-register Microsoft Authenticator
If the Authenticator app is no longer linked correctly, delete the old account entry only after you have another recovery method available.
Then re-add the account from Microsoft’s security settings so the new device registration is clean.
On the Microsoft account security page, review your sign-in methods and make sure the current phone is listed correctly.
If you recently changed phones, this step is especially important.
8. Confirm recovery information is current
Microsoft may block verification if your recovery phone number or backup email is outdated or inaccessible.
Update this information from the security section of your Microsoft account once you are back in.
- Replace old phone numbers no longer in use.
- Add a backup email address you can access immediately.
- Store recovery codes securely if Microsoft provides them.
9. Turn off and re-enable two-step verification only when necessary
If every other method fails and you can still access your account through another trusted sign-in path, temporarily disabling two-step verification and turning it back on can clear broken registration data.
Use this as a last resort because it briefly reduces account security.
After re-enabling, test the login on Outlook.com, Outlook for Windows, and your mobile device so the new setup is consistent across platforms.
Fix Outlook desktop app-specific authentication problems
Outlook desktop relies on Windows identity components, cached credentials, and Office account licensing.
When two-factor authentication fails only in the desktop app, focus on the local profile and Office sign-in state.
- Close Outlook completely and reopen it as administrator once.
- Remove saved Windows credentials related to MicrosoftOffice, Outlook, or ADAL.
- Open Control Panel or Settings and create a fresh Outlook profile if needed.
- Repair Microsoft 365 or Office using the built-in repair tool.
These steps often fix sign-in prompts that repeat even after a correct verification code is entered.
Fix Outlook mobile app-specific authentication problems
On iOS and Android, the most common causes are app cache corruption, push notification limits, and device-level security restrictions.
If the code arrives but the approval prompt does not, check notification permissions for Microsoft Authenticator and Outlook.
- Allow notifications for Outlook and Microsoft Authenticator.
- Disable battery optimization for the authentication app.
- Reinstall Outlook if the account sign-in keeps looping.
- Make sure the mobile device has stable internet access when the prompt appears.
When to contact Microsoft support
Contact Microsoft support if you cannot access any verified sign-in method, your recovery options are outdated, or the account is locked due to suspicious activity.
If your organization uses Microsoft 365 with Entra ID, your IT administrator may need to reset authentication methods or re-enroll the device.
Keep details ready, including the exact error message, the device type, the Outlook version, and the verification method you were using.
That information helps support diagnose whether the failure is tied to account security, conditional access, or a local app issue.
Common errors and what they usually mean
- Invalid code: wrong time, expired code, or incorrect verification method
- Too many requests: repeated attempts or temporary security throttling
- Can’t receive prompt: notification disabled, app not installed, or network issue
- Sign-in loop: stale cached credentials or corrupted app session
- Verification unavailable: recovery data missing or account security settings need review
By matching the error pattern to the likely cause, you can fix two factor authentication on Outlook faster and with less trial and error.