Authenticator notification going to neither new or old phone

This usually happens because the old Authenticator registration is still associated with the previous device, and deleting or reinstalling the app alone does not move notifications to the new phone.

Try this:

1. If the old phone is still available, check whether the prompt is still being sent there.
2. Remove the old Authenticator device registration:
   • For a personal Microsoft account, go to the two-step verification area of the Account Security page and turn off verification for the old device.
   • For a work or school account, go to the two-step verification area of either your My Apps page or your organization’s company portal and turn off verification for the old device.
3. Add the new phone again:
   • On the security info page, choose Add sign-in method.
   • Select Authenticator app or Phone as needed.
   • In Microsoft Authenticator on the new phone, use Add account and complete the setup.
4. If no notification appears on the new phone, check these basics on that phone:
   • Notifications are enabled for Microsoft Authenticator.
   • The phone is not in Do Not Disturb or Quiet mode.
   • The phone has internet access.
   • Date and time are set correctly.
   • The app is updated to the latest version.
5. If the sign-in is waiting for approval from the old phone and that phone cannot approve it, use another verification method such as SMS if available.

If the account is a school or work account and no alternate sign-in method is available, the organization’s IT administrator may need to reset the MFA registration so the new phone can be registered again.

• Microsoft Authenticator FAQs
• Use a screen reader to set up and troubleshoot multifactor authentication
• Troubleshoot problems with Microsoft Authenticator
• How do I make my authenticator app work on my new device? - Microsoft Q&A
• Accidentally erase microsoft authenticator in previous phone - Microsoft Q&A