Microsoft Authenticator App Not Showing a Code

Why Microsoft Authenticator May Not Show a Code

First, check what the sign-in page is asking you to do. Microsoft Authenticator can handle several kinds of verification, and not all of them display a six-digit code.

• Time-based code: The account tile in Authenticator shows a code that changes regularly. You type that code on the sign-in screen.
• Approval notification: Authenticator sends a prompt asking you to approve or deny the sign-in. A code may not appear.
• Number matching: The sign-in screen displays a number. Open the notification or Authenticator prompt, enter that number, and approve the request.
• Passwordless sign-in: The app may ask you to approve the request and unlock the phone instead of entering a password or code.

A code can also be absent because the wrong account is open, account setup was never completed, the entry needs attention, or the account was not transferred to a replacement phone. Notification problems affect approval prompts, but ordinary time-based codes can normally be generated without an internet connection.

Check the Account and Sign-In Method

1. Read the full message on the sign-in screen. Look for wording that asks for a verification code, approval, or the number shown on the screen.
2. Open Authenticator directly instead of waiting for a notification.
3. Find the account whose name and organization match the account being used to sign in. People often have separate personal, work, and school entries with similar names.
4. Tap the correct account. Check whether it displays a changing code, a pending sign-in request, or a warning that action is required.
5. If the sign-in screen expects another method, use its option commonly labeled “Other ways to sign in,” “Use another verification method,” or similar.

Do not repeatedly approve unexpected requests. If the account name, location, or sign-in details look unfamiliar, deny the request and change the account password through Microsoft’s official account or security pages.

Fix Missing Codes on the Current Phone

If the Microsoft Authenticator app is not showing a code on the phone that was already working, keep the account in place while you check the following:

• Unlock the phone and open Authenticator manually. Complete any phone passcode, fingerprint, or face check requested by the app.
• Make sure the phone’s date, time, and time zone are set automatically. Incorrect device time can make a displayed code fail even when it looks normal.
• For approval prompts, confirm that Wi-Fi or mobile data works. Then check the phone settings to make sure Authenticator can use data and send notifications.
• Turn off Focus, Do Not Disturb, or battery restrictions temporarily if they are delaying notifications. Opening the app directly may reveal a waiting request.
• Install available operating-system and Authenticator updates through the phone’s official app store.
• Restart the phone, reopen Authenticator, and begin a fresh sign-in request. An older approval prompt may have expired.
• Look for an error or “action required” notice beside the account. A work or school account may need attention from its organization.

Do not remove the account, clear the app’s data, or reinstall the app as an early troubleshooting step. Those actions can remove credentials that are still your only working verification method.

Restore Authenticator on a New Phone

If the Microsoft Authenticator app is not showing a code on a new phone, installing the app alone is usually not enough. The accounts must be recovered from an Authenticator backup or registered again.

If cloud backup was enabled on the old phone, open Authenticator on the new phone and choose its recovery option. Sign in with the same recovery account used for the backup and follow the prompts. Recovery can depend on the phone platform and backup settings, so follow the instructions shown inside the official app.

After recovery, inspect every entry. Some accounts may return but still display “action required.” Work and school accounts, passwordless sign-in, and certain protected credentials may require registration on the new device. Use another working verification method to sign in to the account’s official security-information page, then add the new Authenticator installation by scanning the QR code shown there.

If the old phone still works, keep it available until you have tested the new phone with each important account. Do not erase it or remove its registrations merely because account names appear on the new phone.

Use Another Verification Method

Return to the sign-in screen and look for the choice to use another method. Depending on what was previously registered, the available choices may include a text message, phone call, email, security key, recovery code, or approval on another registered device. Only methods already associated with the account will normally appear.

For a personal Microsoft account, use the official account recovery and security guidance reached through Microsoft’s support site. Be ready to confirm account details and access any backup method you previously registered.

For a work or school account, contact the organization’s help desk or account administrator. Explain that Authenticator is unavailable or was not transferred to the new phone. The administrator may need to verify your identity, reset your authentication registration, or provide the organization’s approved temporary access process.

If no alternative appears, do not follow instructions from unsolicited callers, messages, or third-party recovery services. Use support options found from the organization’s official website or an internal directory you already trust.

Avoid Getting Locked Out

• Add more than one verification method before changing phones, if the account permits it.
• Turn on Authenticator’s official backup feature and confirm which recovery account it uses.
• Keep recovery codes in a secure place separate from the phone.
• Transfer or re-register accounts while the old phone is still available.
• Test sign-in and approval on the new phone before removing the old device registration.
• Review personal, work, and school accounts separately; restoring one does not prove that every account is ready.
• Do not share a code, approval, QR registration image, or recovery code with anyone who contacts you unexpectedly.

Before resetting Authenticator, removing an account, replacing a device, or erasing the old phone, confirm that another method works and that the new phone can complete a real sign-in. That final test is the safest protection against losing access.