Microsoft Authenticator: Back from password manager to authenticator
Microsoft's Authenticator app can also manage passwords in addition to extended authentication as a second factor. That ends now.
(Image: oatawa/Shutterstock.com)
In addition to its main function of confirming logins as a second factor, Microsoft's Authenticator can also do other things – such as manage and automatically insert passwords. Microsoft now wants to remove these functions and streamline the Authenticator app.
In a support article, Microsoft discusses the measure and the timetable. "Microsoft is streamlining 'Autofill' so you can easily use saved passwords across devices," the Redmond-based company explains. "As part of these updates, the 'Autofill' feature in Microsoft Authenticator will be phased out starting July 2025."
Microsoft: Tight schedule presented
While there is currently still a function for importing passwords from web browsers into Microsoft Authenticator, users in the app will no longer be able to save new passwords in Authenticator from June. During July 2025, it will no longer be possible to use the 'autofill' function of Authenticator and from August 2025, the saved passwords in Authenticator will no longer be accessible at all.
Videos by heise
The saved passwords – but not the password history of created passwords – and addresses would be securely synchronized with the Microsoft account. They can still be used "seamlessly" with the 'autofill' function of Microsoft's Edge web browser. If you want to use the passwords with other password managers, you can also export them from the Microsoft account and import them into the desired software.
To retain access to the generated passwords, they must be saved manually from the generator history to the saved passwords. Microsoft will delete the generated and unsaved passwords after August 2025. Microsoft will delete payment information stored in the Authenticator from devices after July 2025. Microsoft is keen to point out that the Authenticator will of course continue to support and store passkeys.
At the beginning of the year, Microsoft had problems with the core function of the Authenticator. In Chromium-based web browsers, authentication via the Authenticator app was not possible for Microsoft 365 services. The login attempts failed with an error message stating that the services had not received permission from those affected. Microsoft suggested switching to other methods such as logging in with a password, one-time code or passkey as a temporary workaround.
(dmk)