A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Invalid authenticator codes are commonly caused by the device generating the code being out of sync, or by the authentication flow timing out.
- Check the date and time on both the sign-in device and the phone running Microsoft Authenticator.
- Ensure the device settings are correct.
- If the clocks differ by even a few minutes, the one-time code can be rejected as invalid.
- After correcting the time, generate and use a new code.
- Do not reuse the previous code.
- Codes refresh every 30 seconds, so if the countdown is almost finished, wait for the next code before pasting it.
- If the sign-in page has been open too long, restart the sign-in process.
- Some authentication attempts time out.
- If the MFA code entry screen has been open for more than five minutes, start over and enter a fresh code.
- If the error is "Authentication did not complete," also check:
- Microsoft Authenticator is unlocked
- Notifications are enabled
- The app is updated to the latest version
- The phone has internet access; switching between Wi-Fi and mobile data can help
If the problem started after reinstalling Authenticator or changing phones, the MFA registration may no longer be valid. In that case, an admin may need to reset MFA registration, or if locked out as the only admin, Microsoft support for business accounts is the escalation path.
References: