Back to Flash News

Proton Mail mocks daily 47 times opening of authenticator

Proton Mail stated that the human body is not designed to open Microsoft Authenticator 47 times a day just to log into Microsoft Teams. The number 47 is rhetorical, not a published measurement result.

This statement appeared after the update of its enterprise migration tool. On September 29, Easy Switch for Business began supporting Microsoft 365, allowing team emails, contacts, and calendars to be migrated to Proton, claiming no downtime during the migration.

Proton also has its own Authenticator, focusing on cross-platform and encrypted backup of one-time passwords. Microsoft's authenticator is tied to push approvals, passkeys, and passwordless login, primarily serving Microsoft 365 and Entra accounts. The login actions offered by both are not the same.

Proton was established by scientists in Switzerland, with a product line that includes end-to-end encrypted email, calendar, cloud storage, and VPN, with a commercial narrative centered around replacing ads and tracking. Microsoft integrates email, meetings, chats, and authentication within the same tenant, with the authenticator serving as a gateway to Teams and a lock for the tenant.

The company did not disclose the number of enterprises migrating from Microsoft or the contract amounts in this statement. In the same week, it also explained that emails and VPNs are subject to different laws, and employees will not be imprisoned for the illegal actions of others.

The buyers are team administrators looking to exit the Microsoft tenant, while the sellers are Microsoft 365, which binds identity, meetings, and email together. The event is driven by comparative statements following the launch of the migration feature. Funding is shifting from Microsoft subscriptions based on seats to Proton's enterprise email, benefiting the privacy suite that can migrate emails and calendars in bulk, while alternatives that rely solely on the number of authenticator uses and cannot migrate identity directories are under pressure.

Source: Public Information

ABAB AI Insight

Proton was started in 2014 by Andy Yen and others at CERN, initially addressing the encryption needs post-Snowden as a Gmail alternative, and later integrating VPN, cloud storage, calendar, and authenticator into a suite. On Microsoft's side, the path from acquiring Skype, launching Teams, to using Entra and Authenticator to consolidate logins within the same tenant involves initially offering office software for free or bundled, with identity later being charged.

The capital path is the migration tool, not just another privacy declaration. Easy Switch directly connects to Microsoft 365's emails, contacts, and calendars, aiming to reduce the downtime cost of switching suppliers. The authenticator statement attacks the friction of repeatedly opening the app daily, while the real target is the seats. If Proton Authenticator cannot replace push approvals and passwordless logins, enterprises will still keep their identities with Microsoft.

A comparable situation is Slack's use of "email is dead" against Outlook, and Zoom's friction against enterprise video suites. The current position is a control period. Teams are already within the seats, and Proton aims to cut the migration costs, not the meeting functionalities themselves. The 47 times did not provide a sample, and cannot be considered as login frequency data.

Structurally, this represents a transfer of pricing power. Microsoft's pricing power lies in the identity directory: once email, meetings, and the authenticator are bound within the same tenant, replacing any layer requires redoing the login. Proton seeks to buy this layer of pricing power with zero downtime migration. If the calendar and identity are migrated together, the seat fees will follow; if only emails are changed while the authenticator still points to Teams, the statement cannot change the contract.

ABAB News · Cognitive Law

  1. Login friction is advertising, tenant binding is the contract.

  2. Numbers can be exaggerated, migration cannot have downtime.

  3. Authenticators left at the original factory, even if the email is changed, it is still from the original factory.