Since the phone was changed and the Microsoft Authenticator app on the old phone is no longer available, the existing multifactor authentication (MFA) methods must be reset or updated before access to the inbox is possible.
For a personal Microsoft account (Outlook.com, Hotmail, Live):
- If verification codes are not being received:
- Avoid repeatedly requesting codes, as excessive requests can cause temporary blocking of code delivery.
- Check whether the phone blocks texts from unknown numbers and adjust settings, then choose I don't have a code to have another code sent.
- Ensure the phone number is a mobile number (not VOIP) and that the SMS inbox is not full.
- Check junk email for codes from @accountprotection.microsoft.com if email is used as a verification method.
- If the security info (phone/email) is wrong or no longer accessible:
- When prompted for a verification method, select I don't have any of these and follow the prompts to replace or update the security info.
- If the phone/email shown is not recognized, verify that the correct account and domain are being used; if still correct but inaccessible, start account recovery using the provided recovery flow.
For a work or school account used with Outlook mobile:
- If verification codes are not received, follow the same checks above (no VOIP number, SMS not blocked, junk folder for email codes, avoid excessive requests).
- If none of the methods work or are accessible, sign in to the Security info page with a method that still works and select Update info to add or change security methods. If no method works, choose I don't have any of these and follow the prompts to replace security info.
- If sign-in is still not possible because all MFA methods are lost, contact the organization’s IT admin and request an MFA reset so that new methods (such as a new phone number or new Authenticator registration) can be configured.
Once MFA/security info is updated and at least one working method is configured (phone, email, or Authenticator on the new phone), sign-in to Outlook mobile should succeed again.
References: