My Service Support

Microsoft Authenticator App Not Working

Updated 2026-08-15 · 1012 words

Verified contacts

Taken from the company's own website and checked on 2026-08-15. Companies change these — if something does not match, the official site wins.

Phone
1-212-824-0758 Toll Cameroon
Phone
1-802-044-0086
Phone
1-877-867-2337
Phone
1-312-843-5151 Toll Free Sierra Leone

Official website: https://support.microsoft.com

Identify What Is Not Working

Start by matching the problem to what you see. This helps you avoid changing settings or registration details that are not causing the failure.

  • If the app will not open or closes immediately, restart the phone and check for an app update.
  • If no approval prompt appears, open Authenticator manually and look for a pending request.
  • If a six-digit code is rejected, check the phone’s time settings and use the newest code shown.
  • If the wrong account appears, compare the account name in Authenticator with the account named on the sign-in screen.
  • If setup cannot be completed, confirm that you are following the instructions for the correct personal, work, or school account.

When asking “why is my Microsoft Authenticator app not working,” also check whether the problem affects every account or only one. A single-account failure often points to that account’s registration. A problem affecting the whole app is more likely related to the phone, app permissions, or connectivity.

Check the Phone and App

  1. Switch between Wi-Fi and mobile data to test the connection. Approval notifications require a working connection, although rotating verification codes may still appear offline.
  2. Restart the phone, then open Authenticator again.
  3. Check the phone’s app store for an Authenticator update and install it if available.
  4. Set the phone’s date, time, and time zone to update automatically. Incorrect time can cause verification codes to fail.
  5. Open the phone’s notification settings and make sure Authenticator notifications are allowed.
  6. Review battery-saving or background-use settings. Allow Authenticator to run in the background so the phone does not delay approval requests.
  7. Check any permissions requested for the task you are performing, such as camera access when scanning a setup code.

If the app is controlled by an employer or school, device-management rules may limit which settings you can change. Contact the organization’s help desk before removing management settings.

Fix Missing Approval Notifications

A missing notification does not always mean the request failed. Leave the sign-in screen open, launch Authenticator yourself, and select the account that matches the sign-in attempt. Check for a pending approval request or instructions to enter a number shown on the sign-in screen.

Approve only a request that you started and recognize. If an unexpected request appears, deny it and follow your account provider’s security guidance.

If no request is visible, return to the phone’s settings. Confirm that notifications are enabled for Authenticator, including alerts on the lock screen if you rely on them. Turn off any focus or do-not-disturb mode temporarily, then retry the sign-in.

For phones that restrict background activity, allow Authenticator to use background data and remove app-specific battery restrictions. Open the app before sending another request. Avoid pressing the resend button many times because several prompts can arrive out of order. Cancel the old attempt when possible and respond only to the newest request.

When several accounts are listed, compare the full account label and organization name carefully. A prompt for one work or school tenant may not appear under another entry, even when both use the same email address.

Fix Codes That Do Not Work

Authenticator codes change quickly. Wait for a new code, enter it before it expires, and check every digit. Do not reuse a code from an earlier attempt.

Make sure automatic date and time are enabled on the phone. If they were already enabled, turn the setting off and back on only if your phone allows you to restore the correct automatic time immediately. Then restart Authenticator and try one fresh code.

Repeated failures may trigger extra security checks or cause old sign-in pages to reject otherwise valid codes. Close the failed sign-in attempt, begin again from the service you intended to access, and enter the newest code once.

If the sign-in screen offers another verification method, choose one you previously registered and can access, such as a security key, passkey, backup code, or another approved method. Available choices differ among personal, work, and school accounts. Never share an Authenticator code with someone who contacts you.

Restore or Re-register Authenticator

If you moved to a new phone, look in Authenticator for its recovery or backup-restoration option. Restoration works only when a compatible backup was created and you can access the account used for that backup. Some restored work or school entries may still require fresh registration.

Do not assume a backup exists. Keep the old phone available and working until you have confirmed that the new phone can complete a real sign-in. If you can still access the account by another method, open its official security-information area and add or re-register Authenticator by following the displayed setup steps.

Removing an account from Authenticator can erase the phone’s working verification entry and leave you unable to sign in. Before removing anything, confirm that you have another usable verification method, an active signed-in session, or help from the organization’s administrator.

For a personal Microsoft account, use the official account security and verification-method controls. For a work or school account, use the security-information process supplied by the organization. If registration is blocked, an administrator may need to reset the account’s authentication methods before you can enroll again.

Get Help When You Cannot Sign In

If my Microsoft Authenticator app is not working and no alternative method is available, the correct support path depends on who manages the account.

  • For a personal Microsoft account, go to Microsoft’s official support site and find the account sign-in or account recovery section. Use the guided recovery or contact-support option shown there.
  • For a work account, contact the employer’s IT help desk or identity administrator. Microsoft support may not be able to change authentication settings controlled by that organization.
  • For a school account, contact the school’s technology office, help desk, or account administrator.

Prepare the account email or username, the organization name, the phone model, the phone operating system, the exact error message, and whether the old device is available. Also note whether notifications, rotating codes, or setup are failing. Do not send passwords, verification codes, backup codes, or screenshots containing setup QR codes.