A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
On the replacement Android phone, restore Authenticator from its cloud backup before signing in; if no backup exists, recovery must be completed separately for each personal, work, or school account.
1. Try restoring the Android backup
This works only if Cloud Backup was enabled in Authenticator on the old Android phone and the same personal Microsoft recovery account is available.
- Install Microsoft Authenticator from the Google Play Store.
- Open it and select Restore from backup or Begin recovery before signing in.
- Sign in with the personal Microsoft account previously used for Authenticator backup.
- Open each restored account and complete any Action required or Sign in to add your account prompt.
If Authenticator was already opened and signed in, sign out or remove the accounts first so that Restore from backup becomes available. Work or school account backups restore only the account name; those accounts still require sign-in and registration on the replacement phone. ^1^
If Restore from backup does not appear, or no accounts are recovered, a usable backup probably is not available. A normal phone data/app transfer does not replace the account-specific security registration.
2. If this is a work or school account
First select Sign in another way, I can’t use my Microsoft Authenticator app right now, or a similar option on the sign-in page. Use a previously registered text message, telephone call, security key, passkey, or other method.
If no alternative works, contact the organization’s IT help desk and request:
Reset my MFA methods and require me to re-register for multifactor authentication because my old phone is unavailable.
An Authentication Administrator can perform this in:
- Microsoft Entra admin center
- Entra ID → Users
- Select your user account.
- Select Authentication methods.
- Select Require re-register MFA.
This removes the existing Authenticator and related MFA methods and prompts you to configure new methods during the next sign-in. ^2^
After the reset:
- Sign in with your work or school account.
- Follow the security-information setup prompt.
- Choose Microsoft Authenticator.
- In Authenticator, add a Work or school account and scan the displayed QR code.
- Approve the test notification.
If this account is the tenant’s only administrator account, another administrator cannot perform the reset. That is a tenant-lockout case requiring Microsoft Support and ownership verification. ^3^
3. If this is a personal Microsoft account
At the verification screen, select another available email, telephone number, recovery code, or other verification method. Once signed in:
- Open the account’s Advanced security options.
- Select Add a new way to sign in or verify.
- Register the replacement phone and Authenticator.
- Test the new method.
- Remove the Authenticator entry for the old phone only after the new method works.
If all security information is unavailable, select I don’t have any of these during sign-in and follow the process to replace it. Microsoft documents a 30-day waiting period before sign-in is restored after all security information is replaced. ^4^
For a personal account with two-step verification enabled, if there is no backup, recovery code, or accessible alternate verification method, Microsoft Support cannot bypass two-step verification or manually change the account details. ^5^
After access is restored, enable Authenticator → menu → Settings → Cloud Backup and add at least one independent backup sign-in method.
References
- Transfer Microsoft Authenticator account entries to a new phone
- Manage user authentication methods for Microsoft Entra multifactor authentication
- Developer replaced their phone and can use Microsoft Authenticator for other sites but not Azure Portal - Microsoft Q&A
- Troubleshoot Microsoft verification code issues | Microsoft Support
- Help with the Microsoft account recovery form | Microsoft Support