A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Yes. Microsoft Authenticator does not require only a code-based flow.
Supported sign-in methods include:
- Push notification approval: enter the username, select Next, then Send notification. If needed, select Other ways to sign in > Approve a request on my Microsoft Authenticator app. Open Authenticator, match or enter the displayed number, then Approve.
- Verification code from the app: Authenticator can generate an OATH code that is entered on the sign-in page.
- Passwordless / passkey sign-in: Authenticator can support passwordless sign-in and passkeys.
To break the loop:
- On the sign-in page, look for Other ways to sign in or another verification method.
- If available, choose a different registered method instead of the app code or app prompt.
- If repeated attempts caused a block, wait and try again later, or use a different MFA method.
- For work or school accounts, if no alternate method is available, contact the organization’s IT administrator or Help desk. They can investigate Microsoft Entra sign-in logs and help with MFA settings.
- If the issue is with a Microsoft personal account and verification is blocked, try another verification method connected to the account, try another network, and avoid repeated attempts. Waiting up to 24 hours, and in some cases longer, can remove a temporary block.
Important details:
- Work or school account users might need to unlock Authenticator before confirming sign-in.
- For anomalous sign-ins, a push notification might not be sent automatically. In that case, open Microsoft Authenticator manually, pull down to refresh or tap Refresh, then approve the request.
- In China, Authenticator push notifications on Android do not work because Google Play services are blocked there. iOS notifications do work, and Android users should use alternate authentication methods.