Can I import from Microsoft Authenticator?

Migration · Help center · Current as of 2026-10-10

The order that cannot lock you out

1. Pick one account and sign in to it on a computer, with Microsoft Authenticator still installed and working on your phone.
2. In that service's security settings, add a new authenticator app. It will show a QR code.
3. Add it to KeyNesta and check the code it produces is accepted by the service.
4. Only then remove the old authenticator entry at the service, if it has not already been replaced.
5. Repeat. Keep Microsoft Authenticator installed until the last account is done and verified.

Start with the account that controls the others — your email — and do the rest in whatever order suits you.

Just changing phones and staying on Microsoft Authenticator? See how to move Microsoft Authenticator to a new phone.

Collect the service's own recovery codes as you go

Every service offers backup or recovery codes, and a migration is the right moment to save them somewhere separate. They are what gets you back in if a step goes wrong, and they are controlled by the service rather than by any authenticator.

Microsoft accounts themselves

Some Microsoft sign-ins use push approvals rather than a six-digit code, and those are a feature of the Microsoft Authenticator app rather than a TOTP secret, so there is nothing for another app to hold. Where Microsoft offers a standard authenticator-app option, that one moves like any other. Authy is in the same position for a different reason — see the Authy alternative guide, which has the same re-enrolment pattern worked through in detail.