Migration guide
Switch from Microsoft Authenticator to Tokn
Microsoft Authenticator backs up to a Microsoft account, but there is no export other apps can read. To switch, you re-enroll each third-party account once. Your Microsoft work or school sign-in can stay in Microsoft Authenticator if it uses push approval.
How to switch, step by step
- 1
Take stock
Go through Microsoft Authenticator and note every third-party account. Keep the app installed and working until the last one is moved.
- 2
Install Tokn
Get Tokn from Google Play or F-Droid. There is no account to create - set a vault password or fingerprint unlock and you are ready.
- 3
Re-enroll third-party accounts
For each service, open its security settings and choose to change or re-set up the authenticator app. Scan the new QR code with Tokn and confirm the code.
- 4
Decide about Microsoft sign-ins
Microsoft accounts also support standard authenticator codes, which Tokn handles. Only the push-style Approve sign-in flow is exclusive to Microsoft's app - keep it just for that, or switch the account to standard codes. Then create an encrypted Tokn backup.
FAQ
Common questions
Can I export from Microsoft Authenticator?
No. Its cloud backup only restores into Microsoft Authenticator itself; there is no export format other apps can read. Re-enrolling each account once is the way out.
Can Tokn generate codes for my Microsoft account?
Yes. Microsoft accounts support standard TOTP codes, which Tokn handles like any other account. Only the push 'Approve sign-in' prompts are exclusive to Microsoft's app.
Is the one-time effort worth it?
If you want open source, no cloud dependency, and backups you own, yes. You re-enroll once and are never locked into a vendor's app again - Tokn's backups and sync are open, encrypted formats.
More migration guides
Get Tokn
Install the app, add your first account in a few seconds, and keep your second factor where it belongs: with you.