Microsoft Authenticator

❗Article Status Notice: This Article is a stub

---

This article is underdeveloped, and needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Learn more ▼

Issues may include:

• This article needs to be expanded to provide meaningful information
• This article requires additional verifiable evidence to demonstrate systemic impact
• More documentation is needed to establish how this reflects broader consumer protection concerns
• The connection between individual incidents and company-wide practices needs to be better established
• The article is simply too short, and lacks sufficient content

How you can help:

• Add documented examples with verifiable sources
• Provide evidence of similar incidents affecting other consumers
• Include relevant company policies or communications that demonstrate systemic practices
• Link to credible reporting that covers these issues
• Flesh out the article with relevant information

This notice will be removed once the article is sufficiently developed. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the Discord (join here) and post to the #appeals channel, or mention its status on the article's talk page.

Microsoft Authenticator

File:Microsoft Authenticator.svg

Basic Information
Release Year
Product Type	Security, Software
In Production	Yes
Official Website	https://www.microsoft.com/en-us/security/mobile-authenticator-app

Microsoft Authenticator is a free app that secures Microsoft account with single sign-on (SSO) and provides multi-factor authenication (MFA) for other online services.

One of its key functions is generating secure, ephemeral, random six-digit tokens to enable two-factor authentication (2FA) for arbitrary online services.

Consumer-impact summary

Overview of concerns that arise from the conduct towards users of the product (if applicable):

• User Freedom
• User Privacy
• Business Model
• Market Control

---

Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.

Incidents

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:

1. Retain possession of the old iPhone for daily MFA needs, or
2. Manually reconfigure every service that depends on Microsoft Authenticator for MFA on the new Android device.

For personal power users, manual reconfiguration may be inconvenient but feasible. However, for work accounts, this process is often impractical as it may require administrative privileges beyond the user’s own.

Microsoft’s official documentation acknowledges this limitation, stating:

"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."

Inability to export codes

Like Authy, Microsoft Authenticator does not allow the user to export their MFA codes to another service.

See also

• Authy
• Proton Authenticator