A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
There are supported steps to get Microsoft Authenticator backup and restore working again, but they depend on device type and on whether the backup was correctly created.
Key points from current behavior and documentation:
- Backup and restore must stay on the same platform
- Accounts backed up on iOS cannot be restored on Android, and vice versa.
- If a platform was changed, restore will not work by design.
- Ensure backup is actually enabled on the old device
- On iOS, Authenticator uses iCloud:
- A personal Microsoft account is required as the recovery account.
- iCloud must be signed in.
- In Authenticator → Settings → under Backup, the iCloud backup toggle must be turned on.
- On Android:
- A personal Microsoft account is required as the recovery account.
- In Authenticator → Settings → under Backup, the Cloud Backup toggle must be turned on.
- If the app shows “Something went wrong” when enabling backup, sign in to the recovery account in Authenticator and then turn the backup toggle on again.
- On iOS, Authenticator uses iCloud:
- iOS-specific restore troubleshooting
If a backup is not appearing or restore seems non‑functional on iOS:
- On the old device:
- Enable iCloud Drive.
- Enable iCloud Keychain.
- Enable iCloud Backup.
- In the Saved to iCloud list, locate Authenticator and turn its toggle on.
- Ensure Authenticator is version 6.8.33 or later and open the app at least once.
- On the new device:
- Uninstall and reinstall Authenticator.
- Open it and sign in with the same personal Microsoft account used for backup.
- The backup should then appear for restore.
- On the old device:
- What actually gets restored
- Microsoft personal accounts:
- If using only time-based one-time password (TOTP) codes, the codes are restored.
- If using passwordless sign-in, only the account name is restored; sign-in must be completed again.
- Work or school accounts:
- Only the account name is restored; sign-in is required again.
- Third-party accounts (Amazon, Facebook, Gmail, etc.):
- TOTP codes are restored.
- Microsoft personal accounts:
- If restore still fails
- If the backup container (iCloud account on iOS, Microsoft recovery account on Android) cannot be accessed, support cannot recover the Authenticator data itself.
- In that case, accounts must be re-added manually using each service’s MFA recovery process.
- When completely unable to restore
- If access to the Microsoft backup account itself is lost, use the Microsoft account sign-in helper to regain access to that account, then try Authenticator restore again.
- If restore fails for other reasons, re-add accounts following each site’s “lost phone / new authenticator” flow.
These are the currently documented mechanisms and limitations; there is no separate server-side recovery path for lost or non-functional Authenticator backups beyond these steps.
References: