A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Microsoft does not document a user-accessible way to inspect or relink an Authenticator cloud backup, so the next supported action is to submit Authenticator diagnostic logs immediately after reproducing the failure and escalate through the Authenticator support channel.
Submit diagnostics for the failed recovery
You have already used the correct Android sequence—selecting Restore from backup/Begin recovery before signing in, using the original personal recovery account, and restoring to Android. Those are Microsoft’s documented requirements.^1^
Proceed as follows:
- Check the device’s app store for an Authenticator update. Microsoft recommends the latest version and does not support versions more than 12 months old.^2^
- Reproduce the recovery failure once.
- Without clearing Authenticator’s data or reinstalling it again, open the app’s top-level menu and select Send feedback.
- Include:
- Exact error text and approximate UTC timestamp.
- Authenticator version
6.2609.6214. - Device model and EMUI version.
- That this is an Android-to-Android recovery on the same physical phone after a factory reset.
- The masked recovery-account address shown by the error.
- That recovery previously worked with that account.
- After sending the logs, contact Support or use the Microsoft Authenticator app forum, referring to the submitted feedback and timestamp. Microsoft identifies this as the escalation path for persistent personal-account Authenticator problems.^2^
Authenticator diagnostic logs remain in the app until Send feedback is selected and can include the information needed to investigate account and device-related failures.^3^
What the message establishes—and what it does not
The message establishes that Authenticator did not find a restorable backup associated with the recovery account used in that attempt. Public documentation does not identify version 6.2609.6214 or this exact message as a known incident, nor does it document a customer-facing backup inventory, previous restore points, or a procedure for attaching a backup to another account.
Microsoft documents that Android cloud backup uses a selected personal Microsoft account as its recovery account. It also says that changing the recovery account requires deleting the existing backup and creating another one.^4^ Nothing available here establishes whether your backup was deleted, replaced, detached, or is temporarily undiscoverable. The diagnostic submission is therefore the appropriate way to ask the Authenticator team to investigate; do not post the full email address or other account identifiers publicly.
If Microsoft cannot restore the backup
If no usable backup can be found, the factory reset removed the only local Authenticator instance. Authenticator entries cannot normally be recovered without either that instance or its cloud backup; recovery then has to be performed separately with every affected service.^5^
For each account:
- Third-party sites and personal accounts: use a recovery code, SMS/email method, another signed-in device, or the service’s account-recovery process. After access is restored, remove the previous authenticator registration and scan a new QR code.
- Work or school accounts: contact the organization’s IT administrator/help desk to reset or re-register the authentication method.
- No alternative method available: contact that service’s support team. Microsoft cannot reset authentication configured by an unrelated service.
Even when backup restoration succeeds, its scope is limited:
- Eligible personal and third-party 30-second one-time-password codes can be restored.
- Personal passwordless credentials are not restored; only the account name returns.
- Work or school credentials are not backed up; only the account name returns, followed by sign-in and registration again.^1^
Avoid enabling Cloud Backup in a newly initialized, empty Authenticator installation while this is being investigated: a documented Q&A case reports that doing so after reinstalling replaced the previous backup, with no supported way to select an older restore point.^6^
References
- Restore one-time password codes in Microsoft Authenticator
- Troubleshoot problems with Microsoft Authenticator
- Microsoft Authenticator FAQs | Microsoft Support
- Transfer Microsoft Authenticator account entries to a new phone
- Accidentally Factory Reseted my phone - Microsoft Q&A
- Restore a previous backup - Microsoft Q&A