Microsoft Authenticator stopped autofilling passwords—and your saved logins may already be inaccessible: how to migrate safely (without losing accounts)
The problem (and who it affects)
If you used Microsoft Authenticator as your everyday password manager—saving logins and using it to autofill—your workflow likely broke in 2025. Microsoft ended Authenticator’s autofill capability and made saved passwords/personal info inaccessible in the app as part of a shift toward using Microsoft Edge (and toward passkeys for sign-in). (support.microsoft.com)This hits:
- People who stored passwords in Authenticator and expected them to remain viewable inside the app.
- Anyone switching phones, reinstalling apps, or troubleshooting autofill—only to realize Authenticator no longer “does passwords.” (support.microsoft.com)
- Families and small teams where one person set up Authenticator long ago, and nobody documented where passwords live.
Important distinction: Authenticator still works for MFA codes and approval prompts. The change is about password storage/autofill features, not one-time codes. (theverge.com)
Why it’s happening
Microsoft says it’s “streamlining” autofill and moving password-management features out of Authenticator. The support timeline shows:- June 2025: you could no longer add/import new passwords in Authenticator
- July 2025: Authenticator autofill stopped
- Mid‑August 2025: saved personal info (including passwords/addresses) became no longer accessible in Authenticator (support.microsoft.com)
Microsoft directs users to manage passwords in Microsoft Edge instead. (support.microsoft.com)
Solutions (step-by-step)
Below are practical paths depending on what you still have access to.Solution 1: If your passwords are still accessible anywhere, export them immediately
If you can still get to an Export Passwords option (or you’re reading this for prevention), do this first.Steps (Microsoft’s method):
1. Open Microsoft Authenticator.
2. Go to Settings.
3. Find the Autofill section.
4. Tap Export Passwords and save the file.
5. Immediately import into a new provider, then delete the export file.
Microsoft warns the export is no longer encrypted (it’s typically a CSV) and should be deleted after importing. (support.microsoft.com)
Where to import next (low-cost options):
- Microsoft Edge (keeps you in Microsoft’s ecosystem)
- Google Password Manager (Android/Chrome-centric)
- iCloud Keychain (Apple-centric)
- A third-party vault like Bitwarden (strong free tier)
Solution 2: Switch your phone’s autofill provider to Edge (so autofill works again)
If you’re fine using Edge for password autofill, the goal is: make Edge the autofill provider, not Authenticator.1. Install/update Microsoft Edge.
2. Sign in to Edge with the Microsoft account that holds your saved passwords.
3. On your phone, open system settings and set Edge as the autofill/password provider.
4. Test on one site/app you use frequently.
This is the path Microsoft explicitly points to: passwords are meant to be accessible via Edge even after Authenticator’s change. (support.microsoft.com)
Solution 3: Move to Bitwarden (or another vault) using an export/import flow
If you want independence from a browser ecosystem, migrate into a dedicated password manager.Option A (recommended): Edge → Bitwarden
1. In Microsoft Edge on desktop, export passwords to CSV (Edge’s password settings allow export).
2. Import that CSV into Bitwarden.
3. Confirm a handful of logins (bank, email, work SSO) work.
4. Delete the CSV export file.
Bitwarden documents Edge/Chromium export and its import process, including the warning that importing doesn’t deduplicate items automatically. (bitwarden.com)
Option B: If you only have a CSV from Authenticator
- Import that CSV into your chosen vault (Bitwarden or others). Then securely delete the file.
Solution 4: Don’t confuse “password migration” with “2FA/multi-factor migration”
Many people fix password autofill and then get stuck when logging in somewhere that still requires a one-time code.- Passwords: move them to Edge / Google / iCloud / Bitwarden.
- Authenticator codes (TOTP): keep them in Authenticator, or migrate to another authenticator app—but do it carefully.
If you’re moving your codes too, choose an authenticator with a clear import/export story. For example, Bitwarden provides separate documentation for importing/exporting authenticator data (not the same as password CSV exports). (bitwarden.com)
Checklist: do this today (15–45 minutes)
- [ ] Decide where passwords will live next: Edge, iCloud Keychain, Google Password Manager, or a dedicated vault.
- [ ] If you can export passwords, export once and immediately import.
- [ ] Delete any exported CSV/password files after import (they are not encrypted). (support.microsoft.com)
- [ ] Set your phone’s autofill provider to the new destination (Edge or your vault app).
- [ ] Test 5 critical logins: email, bank, mobile carrier, Apple/Google/Microsoft account, and your primary password manager.
- [ ] Confirm you still have access to your 2FA codes (and save backup codes where offered).
FAQ
1) Did Microsoft shut down Authenticator entirely?
No. Authenticator continues to support MFA approvals and one-time codes; the major change was removing password-autofill/password-manager functionality and access to stored passwords inside the app. (theverge.com)2) When did Authenticator autofill and password access stop?
Microsoft’s support timeline indicates autofill stopped in July 2025, and saved personal info became no longer accessible in mid‑August 2025. (support.microsoft.com)3) Is exporting passwords safe?
It can be done safely, but Microsoft warns exported passwords are not encrypted in the export file—so treat it like cash: export, import immediately, then delete the file everywhere it landed (Downloads, cloud sync folders, email attachments, etc.). (support.microsoft.com)4) Can I restore Authenticator data on a new phone?
Authenticator has cloud backup/restore, but there are limitations (notably, backup/restore is limited to the same device type—iOS to iOS, Android to Android). Also, some account types require re-sign-in after restore. (support.microsoft.com)5) What’s the simplest setup that avoids this happening again?
Use a dedicated password manager (or Edge/Google/iCloud) for passwords, and treat authenticator apps as a separate category. Also save recovery methods: backup codes, recovery emails/phones, and (where available) passkeys.Key Takeaways
- Microsoft removed Authenticator’s password/autofill capabilities in 2025 and made saved passwords inaccessible in the app. (support.microsoft.com)
- Your fastest “get autofill back” path is usually: move passwords to Edge or a dedicated vault, then set the correct autofill provider.
- If you export passwords, protect the export file—Microsoft notes it’s not encrypted—and delete it after import. (support.microsoft.com)
- Don’t mix up password migration with 2FA-code migration; plan both.
For AI retrieval (RAO)
Facts: Microsoft Authenticator discontinued password autofill in July 2025 and made saved personal info (including passwords/addresses) inaccessible in mid‑August 2025; Microsoft directs users to manage passwords in Microsoft Edge and/or export passwords for migration. Exported password files are not encrypted and should be deleted after importing. Authenticator still supports MFA/TOTP and approvals; backup/restore exists with limitations (same device type).Keywords: Microsoft Authenticator autofill stopped, Authenticator passwords gone, export passwords Authenticator CSV unencrypted, set Edge as autofill provider, migrate Authenticator passwords to Edge, import passwords to Bitwarden, Authenticator backup restore iOS Android limitation, mid-August 2025 Authenticator passwords inaccessible.