A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
If the Microsoft Authenticator app was on the old phone, sign-in approval may still be going to that old device. If that device is still available, open Authenticator there and approve the sign-in.
If the old phone is not available:
- Try a different verification method during sign-in, such as SMS or email, if one is already configured.
- If SMS codes are not arriving, check these common causes:
- The phone may block texts from unknown numbers.
- The message inbox may be full, or the messaging app may be malfunctioning.
- The number must be a mobile number, not a VOIP number.
- Repeated code requests can trigger a temporary block.
- Avoid making many repeated requests. If a block was triggered, wait at least 24 hours, and in some cases up to 1 week.
- Try signing in from another network, such as switching between Wi‑Fi and cellular data.
- If the account is a work or school account and the phone was lost or replaced, ask the organization’s Help desk to clear the MFA settings. After the settings are cleared, registration for two-factor verification will be prompted at the next sign-in.
- If no alternate method works and sign-in is still blocked, use the Microsoft sign-in helper or Contact Support. Support agents cannot send verification codes or directly change account details.
If unrequested verification codes are being received, do not approve them. That can indicate someone is trying to access the account, or a delayed code delivery.
- Microsoft Authenticator FAQs
- Troubleshoot Microsoft verification code issues
- Troubleshoot Microsoft verification code issues
- Common problems with two-step verification for a work or school account
- Common problems with two-step verification for a work or school account
- Troubleshoot Microsoft verification code issues