A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The issue is not with phone processing time. When a phone is replaced or reset and the old Authenticator app is no longer available, the existing MFA registration usually cannot be recovered from the app alone. The sign-in loop (being asked for a code or number match that cannot be approved) means the MFA methods must be reset by the account owner or an administrator.
Since Authenticator is used for both work and school accounts, the next steps depend on who manages each account:
- If these are work or school (organization) accounts
End users cannot break this loop themselves once they lose access to the old Authenticator. An IT admin must reset MFA:- Contact the organization’s IT/helpdesk and explain that access to Microsoft Authenticator was lost when the phone was replaced and there is no other verification method.
- Ask them to reset MFA / require re-register MFA for the account in the Microsoft Entra admin center. The documented admin path is:
- Go to Microsoft Entra admin center → Identity → Users → All users.
- Select the affected user.
- Open Authentication methods.
- Select Require re-register multifactor authentication.
- After this reset, sign in again; the account will prompt to set up Authenticator from scratch on the new phone (scan QR code or sign in in-app).
- If any of the accounts are personal Microsoft accounts
For personal accounts, use the account recovery and security options (alternate email, phone, or recovery form). If those are not available or also locked behind Authenticator, Microsoft’s Data Protection team must assist, again via a support ticket raised through customer service. - Push notifications and codes on the new phone
Once MFA is reset and Authenticator is re-registered, ensure the app can receive prompts:- Use the latest version of Microsoft Authenticator.
- In the app, go to Settings and:
- Turn on App updates.
- Turn off battery optimization for Authenticator.
- Under Notification Settings, ensure Show notifications is on.
- Make sure the device has correct Date & time, is not in Airplane mode, and has a working network connection (try both Wi‑Fi and mobile data).
- If a VPN is in use, disconnect it and test again.
- If Authenticator still does not show prompts after re-registration
For work/school accounts, the organization can control whether push notifications/number matching are allowed. If prompts still do not arrive after re-registering, the IT admin must verify that:- The account is correctly configured for Authenticator-based MFA.
- No conditional access or security policy is blocking notifications.
Because the old phone was traded in and there is no alternative MFA method, the only way out of the current loop is an MFA reset by the admin (for work/school) or by Microsoft support/Data Protection (if the admin is also locked out or it is a personal account). Waiting for device processing will not resolve this.
References:
- Troubleshoot problems with Microsoft Authenticator
- Microsoft Authenticator FAQs
- I need to reset my mfa methods - Microsoft Q&A
- Microsoft authenticator sending me into a spiral - Microsoft Q&A
- Microsoft Authenticator app doesn't show 6-digit OTP code - Microsoft Q&A
- Requesting a Tenant Admin MFA Reset - Microsoft Q&A
- Reset Personal Azure MFA - Microsoft Q&A