Microsoft’s own support page says that starting in January 2027, Android owners can no longer use a Microsoft personal account to turn on backup in Microsoft Authenticator. The replacement is Google One: the app has to be switched on as an item in the phone’s Google One backup list. Anyone who skips the change risks arriving at a new phone with none of the one-time-password codes that the old one held.
The day in tech, in one email: TLDR is the daily newsletter with links and TLDRs of the most interesting stories in startups, tech and programming.
We may earn a commission if you sign up.
Microsoft’s support page and the Android change
Until now, the Android steps in Authenticator have been to open the menu, go to Settings, turn on Cloud Backup and pick a Microsoft personal account to hold the backup. Microsoft’s support page states that starting January 2027 that route ends, and that backup is enabled through Google One instead. Ben Schoon of 9to5Google, who wrote up the change on Nov. 3, noted that the page is his only Microsoft source and called the deadline weeks away.
The backup covers one-time-password credentials for Microsoft personal accounts and for third-party accounts, the six-digit codes that sites ask for as a second sign-in step. Work and school accounts have never been part of it. Without a backup, a lost or broken phone can leave those codes unrecoverable, and each affected service then requires its own recovery path, such as saved backup codes or a different second factor.
Turning on the Google One toggle
The action itself is short. On the phone, open Google One’s backup settings and enable Microsoft Authenticator in the list of items it backs up. Microsoft’s Authenticator backup instructions link to Google’s help page for that screen instead of spelling out each tap, and the page does not say whether a paid Google One plan is required. Google One backup also depends on a screen lock being set on the device.
That last requirement comes from a second Microsoft notice. Message center item MC1528006, published Oct. 27 for enterprise administrators, describes an improved backup and restore experience on Android and says general availability begins in mid-January 2027, rolling out worldwide. Users who set up Authenticator on a new Android phone will be guided differently depending on whether they still have the previous device, and will be pointed to Authenticator passkeys for cross-device sign-in. Microsoft says the experience already exists on iOS.
The runway is short. 9to5Google’s article, dated Nov. 3, called the change weeks away, and the support page’s January 2027 wording is the only cutoff Microsoft has given. Because the toggle sits in Google’s settings rather than inside Authenticator, the practical check is whether Microsoft Authenticator shows up in the phone’s Google One backup list at all; no source describes how the item appears across Android versions, and Microsoft’s page defers to Google’s help article for the steps.
Install location and what stays the same
Two conditions come with the restore flow. Authenticator has to be installed in the Android personal profile, because backup and restore is not supported in a work profile. And Google One backup plus a screen lock must be on before a new device can use the restored data. Microsoft says no administrator action is needed, though organizations may choose to tell employees about the updated experience.
On iPhones the arrangement is unchanged. Authenticator already uses iCloud Backup there, and backups made on an iOS device cannot be restored on an Android device, a limit the support page spells out. 9to5Google observed that the iOS approach is not new, and with the January change both mobile platforms will keep Authenticator’s one-time-password backup in the platform owner’s cloud service, iCloud on iPhones and Google One on Android, instead of in a Microsoft account. The article did not say whether anything changes on iOS.
Open questions in Microsoft’s guidance
Microsoft’s pages do not say what happens to backups already stored in a personal account after January 2027, and the support page tells people only to delete an existing backup and make a new one if they saved it to the wrong account. Michael Aussems of ITdaily, reporting on Oct. 6, found no visible way inside the app to choose a different backup location or move an existing backup. He added that Microsoft announced the change through notices inside the app, tied it to the earlier removal of the password manager from Authenticator, and warned that anyone with a personal Microsoft account needs an alternative active by 2027 or risks losing access to every sign-in that depends on the app after a lost or broken device, leaving backup codes or other second factors as the only way back in.
The same guidance appears in the account-and-billing version of Microsoft’s backup article, which repeats that a Microsoft personal account will no longer be the way to enable backup. No Microsoft spokesperson has put a name to the decision in any of the coverage reviewed, so the support text and the admin notice are the only direct word from the company. Whether the exact cutover falls on Jan. 1 or mid-month is the detail still unstated.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
The day in tech, in one email: Get TLDR →
We may earn a commission if you sign up.
More from Morning Overview
- The NSA says three phone features should be off whenever you aren’t using them
- Hurricane Hunter radar shows four warning signs that a tropical cyclone is about to strengthen, a University of Miami study found
- Tropical Storm Rachel is dumping up to 12 inches on four Mexican states on its way to major hurricane strength
- The FTC says Lens.com doubled the price shoppers saw in Google ads
