Share via

Code notifications

Christopher Williams 0 Reputation points
2026-06-23T16:35:52.0833333+00:00

Just completed a phone replacement and cannot get verification codes on new device.

Microsoft 365 and Office | Subscription, account, billing | For business | Android
0 comments No comments

2 answers

Sort by: Most helpful
  1. Teddie-D 18,295 Reputation points Microsoft External Staff Moderator
    2026-06-24T04:29:06.7666667+00:00

    Hi @Christopher Williams

    It looks like you’ve run into a common issue after switching to a new phone. Since multi‑factor authentication (MFA) was set up on your old device and not yet configured on the new one, you won’t be able to receive codes until recovery steps are taken.

    1.If you are using a work or school account 

    Please contact your IT administrator and ask them to reset your MFA registration. After the reset, you can register Microsoft Authenticator again. 

    For reference, your administrator can follow the steps in this article: Manage authentication methods for Microsoft Entra multifactor authentication - Microsoft Entra ID |… 

    2.If you are using a personal Microsoft account (@outlook.com, @hotmail.com, @live.com) 

    You can try one of the following options: 

    -Use the Microsoft Account Recovery Form: Help with the Microsoft account recovery form | Microsoft Support 

    -Alternatively, contact Microsoft Support: Go to Contact - Microsoft Support, > type "Support" and click Get Help, > click Sign in to contact support at the bottom of the > page under Products & Services, select Microsoft 365 & Office > under Subcategory, select Support, > choose Chat with a support agent in your browser.

    For future reference, here are steps to reconfigure MFA on a new phone: 

    If you are using a work or school account:

    -Visit the My Sign-Ins | Security Info | Microsoft.com page to manage your verification methods   

    -Sign in with your work account. 

    -Select Add sign‑in method > Microsoft Authenticator. 

    -Install Microsoft Authenticator on the new phone. 

    -In the app, choose Work or school account, then scan the QR code shown on the Security Info page. 

    -Approve the test notification sent to the new phone. 

    -Once the new phone works, remove the old device from the Security Info page. 

    User's image

    If you are using a personal Microsoft account

    Please try to sign in Additional security options > Remove and set up Two-step verification again

    User's image

    I hope this information helps. 


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-23T16:36:17.43+00:00

    On a new phone, verification codes or Authenticator prompts often fail because the app or method is still tied to the old device or a blocked verification channel.

    Try these steps depending on how verification is set up:

    1. If using Microsoft Authenticator push notifications
      • The notification may still be going to the old phone where Authenticator was last used.
      • If the old phone is available, open the Authenticator app there and approve the sign-in.
      • Then remove the old device from account security settings and reconfigure Authenticator on the new phone using the guidance in the Authenticator FAQ.
      • If the old device is not accessible, choose a different verification method (SMS or email) when prompted.
    2. If using SMS or email codes and they are not arriving
      • Avoid repeated or excessive requests for codes; this can trigger a temporary block.
      • Check that the phone number or email shown (masked) is correct.
      • Ensure the phone does not block texts from unknown numbers; if it does, change the setting and select I don't have a code to trigger a new one.
      • Check junk/spam folders for email codes from @accountprotection.microsoft.com and mark that sender as trusted.
      • If using a VOIP number, replace it with a mobile number; VOIP numbers cannot receive Microsoft verification codes.
      • If there is heavy compromised traffic from the region, delivery may be delayed; waiting some time can resolve it automatically.
    3. If Authenticator is locked or misconfigured after phone replacement (personal account)
      • Sign in at account.microsoft.com in a browser.
      • Go to Security info.
      • Add a different sign-in method (SMS or email) if available.
      • Remove the existing Authenticator app entry.
      • Add Authenticator app again and complete setup on the new phone.
    4. If unable to access any listed phone/email for codes
      • On the Verify your identity screen, select I don't have any of these and follow the prompts to replace security information.
      • Be aware that replacing all security info can put the account into a restricted state for 30 days while the new info is validated.
    5. If this is a business/tenant admin account and all MFA methods are lost
      • If the account is the only global admin and no verification method works, a self-service reset is not possible.
      • Contact Microsoft Support via the global customer service phone numbers and request a Data Protection team case to reset the admin authentication method.
      • If direct contact is difficult, create a temporary trial tenant, use its admin center to open a support ticket, and clearly state that access is needed for a different, locked tenant where this account is the sole administrator.

    If none of the above methods work and codes still do not arrive, use the sign-in helper tool for Microsoft accounts or contact Microsoft Support for additional troubleshooting options. Support agents cannot send codes or change account details but can help route to the correct recovery path.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.