Lost your phone and the six-digit codes from your authenticator app? Start by determining whether the app had a backed-up or synced copy of the codes. Google Authenticator and Microsoft Authenticator do not recover accounts in exactly the same way. If there is no restorable copy, the recovery step usually happens at each website or service where you enabled two-step verification, not through one universal master reset.
This guide separates those paths, explains what to check before wiping an old phone, and shows how to avoid a second lockout. The instructions concern legitimate recovery of your own accounts. Your provider may require additional identity verification.
Table of contents
What to do in the first five minutes
- Do not factory-reset a phone that still works. Keep it powered and signed in while you check how each service stores its two-factor codes.
- Look for a different already-approved sign-in method: a trusted device, security key, passkey, backup code or another authenticator you enrolled earlier. Availability depends on the service.
- Check your app: identify whether it is Google Authenticator, Microsoft Authenticator, a password manager or an issuer-specific banking app. The recovery instructions differ.
- If the device was stolen: secure the main email account and the phone itself using the platform’s official lost-device tools; then remove trusted sessions or devices as appropriate.
- Avoid supposed recovery agents. Never send a six-digit code, recovery code or password to an unsolicited caller, chat contact or site.
A useful distinction: having the password is not always enough when a website requires a second factor. A recovery phone number or backup email is useful only where that provider explicitly offers it as an alternative sign-in or account-recovery method.
Google Authenticator: check synchronization first
Google says its Authenticator app can synchronize verification codes between devices when you sign in to a Google Account in the app. Open Google Authenticator on the replacement device, sign in to the correct Google Account and inspect whether your expected entries appear. If you do not see them, first check whether you used another Google Account or had set the app to operate without an account. The official instructions also note that the codes can be generated without an internet connection once properly configured.
If the lost device stored codes without synchronization, Google’s guidance is different: visit each site where you configured Authenticator, use that site’s own permitted recovery procedure, and reconnect the new device after regaining access. Losing the app does not mean that Google can reset every third-party site’s two-factor authentication for you.

If you are locked out of the Google Account itself, follow the official Google Account recovery page and complete any identity or device prompts. Do not assume that signing into Authenticator is possible before you have recovered the Google Account. Official reference: Google Authenticator Help.
Microsoft Authenticator: backup is not the same as full restoration
Microsoft Authenticator can restore backed-up one-time password codes for eligible personal Microsoft and third-party accounts. The company specifies a key limitation: backup and restore work only between the same device types, such as Android to Android or iPhone to iPhone. Moving from iPhone to Android is not the same restoration path.
Microsoft also distinguishes several types of entries. Personal accounts using ordinary rotating one-time passwords may restore their codes. Passwordless credentials may need to be re-established. For work or school accounts, the account name may reappear after restore but the credential itself is not restored; the account must be signed in and registered again, often under the organisation’s policies.
If you still have the old phone, make sure the appropriate Microsoft Authenticator backup mechanism is actually enabled before switching. Follow the precise Microsoft backup instructions, then use the official restore procedure on the new device. Do not delete the old authenticator setup until you have tested each critical account.
| Situation | What to check | What not to assume |
|---|---|---|
| Google Authenticator codes synced | Correct Google Account in replacement app | All codes were necessarily synced |
| Google Authenticator used without sync | Each service’s recovery and re-enrolment | One Google reset unlocks every website |
| Microsoft Authenticator personal TOTP backup | Backup account, same phone platform, restore flow | Passwordless credentials restore identically |
| Microsoft work or school accounts | Re-register with organisation’s sign-in policies | Restored account name equals working credential |
No app backup? Recover one account at a time
Suppose your email account accepts a saved recovery code, but your shopping account does not. Do not treat those as one problem. Open each provider’s official sign-in page by typing the known address or using a trusted bookmark. Select its documented alternative verification or recovery route. Some accounts support backup codes or an enrolled security key; others require a review or support process and may not offer instant restoration.
- Prioritise your primary email account, because its inbox often receives security notices and account-recovery messages.
- Use a previously generated backup code only on that specific service’s legitimate sign-in page. Recovery codes are typically single-use; store the remaining codes securely.
- For an employer or school account, contact the official IT help desk rather than trying to bypass organisational security policies.
- After regaining access, remove a missing authenticator device where the service allows it and enrol the new device. Test a fresh login before closing the current session.
- If a provider offers no valid recovery path, follow its published appeal or verification process; do not claim that there is a universal way to bypass two-factor authentication.
Before replacing or resetting a phone, make this checklist
A little preparation prevents the most stressful lockouts. On the old phone, examine every authenticator app and identify which accounts depend on it. Save fresh recovery codes through each provider’s security settings in a secure location independent of the phone. Where offered, add a second approved sign-in method and test it while you still have access.
Then sign in to the accounts from the new device. Verify that the recovery method works and that the old phone is no longer required before erasing or trading it in. If you also use passkeys, our separate guide explains what to check when moving passkeys to a new phone.

Security steps after you get back in
Recovery is also the moment to close the security gap. Review signed-in devices and recent activity, remove devices that are lost or no longer yours, update important credentials if compromise is suspected, and enrol a trustworthy backup verification method. Some synchronised authenticator-code systems are protected by the account used for syncing, which makes that main account’s security especially important.
If the phone was stolen, review device-protection options. Our Android theft-protection settings guide covers steps to prepare before a phone goes missing, while the shared-computer passkey guide explains why signing out and removing a credential are different actions.
Frequently asked questions
Will installing the same authenticator app restore all my codes?
Not necessarily. It depends on the app, the account under which codes were synced or backed up, the recovery device, and the type of credential. Microsoft work or school credentials, for example, need re-registration.
Can a mobile network operator restore two-factor authenticator codes?
A replacement SIM may help where a provider permits SMS verification, but it does not inherently restore time-based codes stored in a separate authenticator app.
Is a screenshot of my backup codes a good backup?
Avoid storing sensitive backup codes somewhere another person can easily access, including unsecured shared albums and messages. Follow the provider’s guidance and use a secure location separate from the phone being replaced.
How do I handle an office account that says “Action required”?
Follow your organisation’s official re-registration process or ask its IT administrator. A restored account name in Microsoft Authenticator does not establish that the work or school credential is ready.
Official sources and editorial method
Reviewed against Google Authenticator support, Microsoft Authenticator backup documentation and Microsoft restoration documentation. This is a general guidance article: account-specific recovery screens, eligibility and security policies may change. No authentication bypass or guaranteed restoration is implied.