A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Follow these steps to troubleshoot Microsoft Authenticator not showing an authorization/verification code when adding the account to Outlook:
- Check Microsoft Authenticator basics
- Ensure the device has a stable network connection. If using mobile data, switch to Wi‑Fi and vice versa, and make sure Airplane mode is off.
- Confirm that Microsoft Authenticator is updated to the latest version. In the app, go to Settings and make sure App updates is turned on.
- Make sure the device date and time are set correctly and the OS is fully updated.
- Fix notification and battery settings for Authenticator
- In Authenticator, open Settings:
- Turn on Show notifications (under Notification Settings).
- Turn off or disable battery optimization for Authenticator so it can run and sync in the background.
- On Android specifically, also ensure any system power‑saving mode is not blocking Authenticator from running or launching other apps.
- In Authenticator, open Settings:
- Disable power optimization / power‑saving conflicts (especially on Android)
- If using a device with aggressive power management (for example, some Huawei or similar Android devices):
- Turn off system power‑saving mode.
- Allow Authenticator (and, if used, Company Portal) to auto‑launch and run in the background.
- Example for Huawei: Phone Manager > Auto‑launch > Secondary launch management > enable Authenticator/Company Portal.
- If using a device with aggressive power management (for example, some Huawei or similar Android devices):
- Try again on both mobile and desktop
- After adjusting the above settings, fully close and reopen Authenticator.
- Retry adding the account in Outlook on the phone.
- If still failing, try again on the desktop Outlook or Outlook on the web, and watch for either:
- A push notification in Authenticator to approve sign‑in, or
- A “one‑time password code” (6‑digit TOTP) under the account entry in Authenticator, if that method is configured.
- If Authenticator still does not show a code or prompt
- Verify that the account is correctly added inside Authenticator and that it is not blocked by Conditional Access or admin policies.
- If there are policy‑based blocks (for example, “You might be signing in from a location that is restricted by your admin” or registration is blocked), contact the organization’s Microsoft 365/Entra ID administrator to:
- Review Conditional Access policies.
- Reset or re‑enable MFA registration for the user so Authenticator can be re‑registered.
- If access to the account is completely blocked
- If none of the above resolves the issue and no OTP or push prompt appears, the MFA registration or account state may need to be reset by support.
- Contact the organization’s admin or Microsoft support (frontline support for business/Entra ID) and provide the Request Id, Correlation Id, and Timestamp so they can trace the failed sign‑in and reset MFA or device registration as needed.
These steps address the known causes where Authenticator does not surface codes or prompts due to app version, connectivity, notifications, battery optimization, or admin policies.
References: