Hello Bitwarden Dev Team,
I noticed that you don’t have an option currently available or listed to import from “Microsoft Authenticator”. Hence, could you please check & add that option too, if possible?
Thanks,
VVR
Hey @VVR just having a look at this one, and looking at info online, what options (file formats) does it give you for exporting the codes?
Hello @bw-admin so, it gives plain text CSV file as the only option to export the stored passwords.
Gotcha, in the meantime you can export your vault and condition the CSV and add the new items. Just be sure to securely backup your vault data prior to making the changes.
So, you mean while your team works on implementing this option, you’re asking me to refer to the format that’s accepted by Bitwarden and manually to the passwords & make changes?
If so, I understand but it’s going to be real pain for me as I’ve close to 180 passwords. 
As this is currently a feature request, I’m providing a possible solution/workaround for the time being.
You can copy everything from the Microsoft export CSV into the Bitwarden CSV in one action. You may just need to adjust headers in the Microsoft doc beforehand to match.
1 Like
No matter how many passwords you have - tens, hundreds, even thousands - you would just need to modify the CSV file to match a format that BW accepts. This is usually easy enough to do on a global level, so you aren’t manually changing individual rows. For example, you can open the CSV using spreadsheet software and manipulate the order of columns, tweak formats using functions, etc.
2 Likes
I realized this is an old topic but all I did was select the CSV.Chrome format and it worked perfectly, most android apps are Chrome based
It didn’t work perfectly for me. The mappings for chrome and MS Autofill CSV exports differ. It’s poor that MS Autofill isn’t on the list of supported sources and that we are messing about with spreadsheets of sensitive data.
Yep. Some encrypted JSON or XML from MS would go a long way.
Hi there.
SO I just read this this afternoon:
Microsoft ends Authenticator password autofill, moves users to Edge (3rd May 2025)
Is there going to be a feature that would allow us to import out Microsoft Authenticator data straight into Bitwarden without having to play around with CSV Files?
Regards
Andrew W
1 Like
@Andrew_Watson, very, very improbably. AOSP and XNU-based OSes’ application sandboxes are nigh impenetrable from inside the OS (without utilising Shizuku to bypass some restrictions, and solely on AOSP). Dedicating time to this would be nonsensical for BW.
Would love to know this as well.
Any news?
I came here for the same query.
We are not asking BW to go into the Microsoft app, we are just confused that BW cannot import from the VERY BASIC CSV file Microsoft exports to, without having to go into said CSV file to mess about.
It’s not like we are talking about an obscure 3rd party app.
And the fact it cannot do it is telling me BW is not a useful reacwment option if the can’t be asked to do something this simple
@Sandra_Pegasus, not necessarily, for CSV (even when RFC 4180 is adhered to) is a very brittle format. Were Microsoft Authenticator to output JSON, XML, or even YAML, I would agree with you. However, CSV is probably not versatile enough to represent the internal state of the application. An example of this that you can test RN is Google and Apple contacts’ CSV outputs versus their CardDAV outputs.
This is conjecture, though. Unless someone can find an example of the MS Auth output CSV being successfully parsed by a consumer, we shan’t know.
How BASIC is it? Development of importer tools is sometimes hampered by the fact that developers do not have access to any documentation about the source file format, nor any example CSV files produced by export from the source.
To help your cause, the best thing you can do is to share information about how the exported CSV file is formatted (specifically, what are the names of each column, and what type of data is stored in each column), with examples if possible.
According to this comment from a Microsoft Authenticator user, the exported CSV file does not contain any TOTP keys, so all of your TOTP would have to be manually reset, regardless of how well Bitwarden (or any other password manager) can import the data that actually does get exported.
For instructions on how to import the exported usernames, passwords, and URLs, you may want to look at this Reddit comment, as well as the follow-up response.
1 Like
url,username,password
The only issue is each field is then in quotes
That is it, nothing else.
I’m only talking about passwords here, not authenticator data
Anyway I was able to get them in RoboForm, so I’ll use that instead
1 Like
I was able to import my saved MS Authenticator csv by choosing to import an Edge csv. However, the data doesn’t look like it does in Authenticator…the website name doesn’t display, just the website icon does…the only name that displays are app names like com.facebook katana. Guessing this is because the name isn’t in the Authenticator export file like it is for Google
1 Like
FYI…I found a way to import MS authenticator passwords and have their website name show up. Google’s csv has an extra field called Name which is the website name that MSA doesn’t have. So I just opened the MSA csv in Excel, added a column for the first field, Name, and the B column has the full website address…use a couple of basic Excel formulas to have just the part of the website name I wanted, and when done imported that csv into bitwarden and it worked perfectly! Try it out
In essence, this the option to condition a csv (or json), as @bw-admin suggested in this previous post here.
1 Like