How to Transfer Microsoft Authenticator to a New Phone
Learning how to transfer Microsoft Authenticator to a new phone is mostly about preparation, backup, and re-verifying your accounts after the move.
The process is straightforward if you know which backup type you use and which accounts still require manual re-setup.
Microsoft Authenticator protects sign-ins for Microsoft accounts, work accounts, and many third-party services using one-time passcodes and push approvals.
Because those credentials are tied to your device, changing phones requires a careful migration so you do not lose access.
What Microsoft Authenticator stores on your phone
Microsoft Authenticator may contain more than one type of sign-in data, and that matters when you move to a new device.
Some accounts can be restored from a cloud backup, while others must be re-added manually for security reasons.
- Microsoft accounts: Personal Microsoft sign-ins often support cloud backup and restore.
- Work or school accounts: These may require re-registration through your organization.
- Third-party accounts: Many TOTP codes can be restored if backup is enabled, but some services require fresh setup.
- App settings: Notification preferences and account layout can vary after restoration.
Before you switch phones
Preparation is the most important part of moving Authenticator.
If you still have access to your old phone, take a few minutes to confirm backup settings and make sure you can sign in to the accounts that depend on the app.
Check that cloud backup is enabled
Open Microsoft Authenticator on the old phone and confirm that backup is turned on.
On iPhone, backups typically use iCloud; on Android, they use your Microsoft account and associated cloud services.
If backup was not enabled before the old phone stopped working, you may still be able to recover some accounts, but many will need to be reconfigured manually.
Verify recovery access for each account
Before replacing your phone, review the accounts in Authenticator and make sure you know each account’s backup email, password, recovery codes, or alternate MFA method.
This step is especially important for Microsoft 365, Azure AD, GitHub, Google, banking apps, and other services that use multi-factor authentication.
- Save recovery codes in a password manager or secure offline location.
- Confirm that SMS or email backup methods are current.
- Update the phone number attached to critical accounts if needed.
- Check whether your employer requires IT approval for MFA changes.
How to transfer Microsoft Authenticator to a new phone on iPhone
If you are moving from one iPhone to another iPhone, the transfer is usually done through iCloud backup and restore inside Microsoft Authenticator.
This is the simplest path when the old phone is still available and signed in to the same Apple ID.
- On the old iPhone, open Microsoft Authenticator and ensure iCloud backup is enabled in the app settings.
- On the new iPhone, install Microsoft Authenticator from the App Store.
- Sign in with the same Microsoft account used for backup, if prompted.
- Restore the backup when the app offers the option.
- Wait for your accounts to appear, then test each one before removing the old phone.
After restore, some accounts may immediately work, while others may show a notice that they need to be reconnected.
That is normal and usually means the service wants to confirm the new device.
How to transfer Microsoft Authenticator to a new phone on Android
On Android, Microsoft Authenticator uses Microsoft account-based backup.
The process is similar in concept to iPhone migration, but the sign-in flow and backup location are different.
- On the old Android phone, open Microsoft Authenticator and confirm cloud backup is enabled.
- Install the app on the new Android phone from Google Play.
- Sign in with the same Microsoft account used for backup.
- Choose restore from backup when prompted.
- Check which accounts restored successfully and which need re-verification.
If you use a work profile or company-managed device, your organization may have policies that restrict backup, device registration, or account transfer.
In those cases, your IT administrator may need to reset your MFA methods.
How to transfer Microsoft Authenticator to a new phone when changing platforms
Moving between iPhone and Android is more complicated than switching within the same platform.
Some data may restore, but not everything transfers cleanly because Apple and Google backups are not interchangeable in the same way.
When changing platforms, plan for a partial migration and be ready to re-add accounts manually.
This is common with third-party services and work accounts.
Best practice for iPhone to Android or Android to iPhone
- Keep the old phone until every account is confirmed on the new device.
- Export or record recovery options for each account first.
- Use backup codes where the service provides them.
- Re-register Microsoft work accounts through the required organization process.
For personal accounts, open each service and update its two-factor authentication settings to point to the new phone.
For Microsoft accounts, you may need to sign in to your security settings and approve the new device before the old one can be removed.
How to move accounts manually if backup is unavailable
If the old phone is lost, damaged, or reset before backup was turned on, you will need to rebuild Authenticator access account by account.
The exact steps depend on the service, but the process generally starts by signing in through an alternate verification method.
- Use recovery codes if you saved them.
- Choose email, SMS, or backup app verification if available.
- Contact the service provider’s support team if you are locked out.
- For Microsoft work accounts, contact your organization’s help desk or administrator.
Once you regain access, immediately set up Microsoft Authenticator again on the new phone and turn on backup so you do not repeat the same problem later.
How to confirm the transfer worked
After restoring or re-adding your accounts, test each important login before erasing the old phone.
This helps you catch issues while both devices are still available.
Use a login test checklist
- Open a Microsoft account sign-in and approve the notification.
- Check one or two third-party TOTP codes to make sure they refresh properly.
- Verify any work or school accounts that use push authentication.
- Make sure notifications are enabled on the new device.
If codes are not appearing, check the time settings on the new phone, update the app, and confirm that battery optimization is not blocking background activity.
Time drift can cause authenticator codes to fail, especially with TOTP-based services.
Common problems during transfer
Most transfer issues come from missing backup, account-specific security rules, or an incomplete restore.
Knowing the common failure points can save time and prevent unnecessary lockouts.
The backup does not appear
Confirm that you signed in with the same Microsoft account used on the old phone and that backup was enabled before the switch.
If the old device was never backed up, there may be nothing to restore.
Some accounts restore, but not all
This usually means the service does not support full migration or requires a separate re-enrollment step.
Work accounts, banking apps, and high-security services often fall into this category.
Push notifications stop working
Check notification permissions, internet access, battery saver settings, and whether the account needs to be re-approved on the new device.
On Android, device optimization settings can interfere with timely alerts.
Security tips for switching devices
Changing phones is also a good time to improve account security.
A device migration exposes weak recovery plans, outdated phone numbers, and forgotten backup methods.
- Remove old devices from account security pages after confirming the transfer.
- Update recovery email addresses and phone numbers.
- Store backup codes in a secure password manager.
- Use a strong device passcode and biometric lock on the new phone.
- Keep Authenticator protected with screen lock and cloud account security.
If the old phone is lost or sold, remotely wipe it if possible and sign out of any Microsoft or Apple/Google accounts linked to the device.
That reduces the chance that someone could access your authentication data.
When to contact support
If you cannot restore accounts, cannot sign in with backup, or are locked out of a critical work or school account, contact the service provider or your organization’s IT team right away.
For Microsoft 365 and Azure-based environments, administrators can often reset MFA methods and issue a new registration flow.
For personal accounts, support is most useful when you can prove ownership through recovery email, recovery codes, payment details, or alternate verification channels.
The more recovery information you keep current, the easier the phone switch will be.