m Removed red links; misc.
Reform (talk | contribs)
Added a consumer workaround in 'Cross-platform migration friction'
 
Line 21: Line 21:


====Cross-platform migration friction====
====Cross-platform migration friction====
A major pain point for users is that Microsoft Authenticator '''does not support direct cross-platform restore'''. This means that if a user with many accounts synced on an iPhone purchases an Android device, they have effectively two options to continue using Microsoft Authenticator for MFA:
Microsoft Authenticator does ''not support'' direct cross-platform restore. This means that if a user with many accounts synced on an iPhone purchases an Android device, they have effectively two options to continue using Microsoft Authenticator for MFA:


#Retain possession of the old iPhone for daily MFA needs, or
#Retain possession of the old iPhone for daily MFA needs, or
Line 30: Line 30:
Microsoft's official documentation acknowledges this limitation, stating:
Microsoft's official documentation acknowledges this limitation, stating:
<blockquote>"'''Important''': You can only backup and restore on the same device type: accounts backed up using an iOS device cannot be restored on an Android device."<ref>{{Cite web |date=2025-10-07 |title=Back up your accounts in Microsoft Authenticator |url=https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |url-status=live |archive-url=https://web.archive.org/web/20260131003513/https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |archive-date=2026-01-31 |access-date=2025-10-07 |website=[[Microsoft]]}}</ref></blockquote>
<blockquote>"'''Important''': You can only backup and restore on the same device type: accounts backed up using an iOS device cannot be restored on an Android device."<ref>{{Cite web |date=2025-10-07 |title=Back up your accounts in Microsoft Authenticator |url=https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |url-status=live |archive-url=https://web.archive.org/web/20260131003513/https://support.microsoft.com/en-us/account-billing/back-up-your-accounts-in-microsoft-authenticator-bb939936-7a8d-4e88-bc43-49bc1a700a40 |archive-date=2026-01-31 |access-date=2025-10-07 |website=[[Microsoft]]}}</ref></blockquote>
===== Consumer workaround =====
For people who were initially pushed to use MS Authenticator for their Microsoft work account, the easy workaround is to switch to [[wikipedia:Time-based_one-time_password|TOTP]] instead of notification-based codes as their 2-factor authentication method. Copilot365 accounts have this option, and when one adds this method in their security settings, they don't have to export MFA codes from the MS Authenticator app.<ref>{{Cite web |date=5 Jun 2026 |title=Using Keeper TOTP with Azure or Office 365 |url=https://docs.keeper.io/user-guides/tips-and-tricks/using-keeper-totp-with-office-365 |url-status=live |archive-url=https://web.archive.org/web/20260605085339/https://docs.keeper.io/user-guides/tips-and-tricks/using-keeper-totp-with-office-365 |archive-date=5 Jun 2026 |access-date=5 Jun 2026 |website=Keeper}}</ref> Instead, they can simply set up another authenticator app, like Ente Auth or [[Proton Authenticator]] and import their TOTP code. Both of which are fully cross-platform compatible, and allow you to sync with multiple platforms, even on PC with their desktop apps.


==Incidents==
==Incidents==