A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
A normal phone transfer does not transfer Authenticator credentials; restore the Authenticator backup if one exists, then re-register any work or school accounts that cannot be restored.
1. Try restoring the Authenticator backup
Backup and restore work only between the same device type: iPhone-to-iPhone or Android-to-Android. An iPhone backup cannot be restored to Android, or vice versa.^1^
Android
- Open Microsoft Authenticator before adding or signing in to accounts.
- Select Restore from backup or Begin recovery.
- Sign in with the personal Microsoft account previously selected as the recovery account.
- Confirm that the saved accounts and eligible verification codes appear.
- If the restore option is missing, sign out of or remove accounts already added to Authenticator, then reopen it and select the recovery option.^2^
iPhone
- Confirm the new iPhone uses the same Apple/iCloud account as the old phone.
- Enable iCloud Drive, iCloud Keychain, and iCloud Backup.
- Install and open Microsoft Authenticator.
- The backed-up account entries should appear automatically.
- For entries showing Sign in to restore your account, tap Sign in and complete the additional verification.^2^
Do not erase the old phone if it remains available until sign-in has been tested successfully on the new one.^1^
2. Understand what can be restored
- Personal Microsoft accounts: A 30-second one-time-password entry can be restored. Passwordless sign-in credentials are not restored, so sign-in must be configured again.
- Third-party accounts: Backed-up 30-second codes for services such as Amazon, Facebook, or Gmail can be restored.
- Work or school accounts: Only the account name is restored—not its credentials. Open each restored entry and sign in again to register the new phone. You might see Sign in to add your account.^1^
The new phone number does not recreate Authenticator codes; those depend on the original Authenticator backup or re-registration with each service.
3. If no backup is available
The missing codes generally cannot be reconstructed from the new phone. Recover access separately for every affected account:
- On the service’s sign-in page, choose Try another way, I can’t use my Authenticator app, or its account-recovery option.
- Use an available recovery email, SMS number, recovery code, security key, or already signed-in device.
- Once signed in, open that service’s security or two-step-verification settings.
- Remove the old Authenticator registration.
- Add Authenticator again and scan the newly displayed QR code.
- Test a code before signing out, and save the service’s recovery codes securely.
For a personal Microsoft account, if all security information is inaccessible, select I don’t have any of these during identity verification and follow the security-information replacement process. Microsoft states that replacing all security information introduces a 30-day wait before sign-in becomes available.^3^
4. If a work or school account blocks re-registration
Contact the organization’s IT help desk and request MFA re-registration. An Authentication Administrator can:
- Open Microsoft Entra admin center.
- Go to Entra ID → Users.
- Select your user account.
- Select Authentication methods → Require re-register MFA.
This removes the existing Authenticator and related MFA methods so that new ones can be enrolled at the next sign-in.^4^
If the missing accounts belong to several organizations where you are a guest, each organization may need to reset its own MFA registration.^5^
References
- Transfer Microsoft Authenticator account entries to a new phone
- [Android](https://support.microsoft.com/authenticator/restore-account-credentials-from-microsoft-authenticator#what-information-is-restored-in-authenticator)
- Troubleshoot Microsoft verification code issues | Microsoft Support
- Manage user authentication methods for Microsoft Entra multifactor authentication
- I change my phone and have issues with auhtenticator - Microsoft Q&A