A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
If the QR code scans but the account still shows as not registered, the setup is usually incomplete rather than fully added.
Try this sequence:
- In the Authenticator app, make sure the app has camera permission. If camera access was denied, the QR code can be added manually by selecting Can't scan the QR image on the setup page and entering the code and URL manually.
- After scanning the QR code, select Next on the computer’s Scan the QR code page. The setup is not complete until the test notification is sent and approved in the Authenticator app.
- Approve the notification in Microsoft Authenticator, then select Next again so the security info is updated.
- If prompted, complete the phone setup step by choosing text message or phone call, enter the verification code, and finish the wizard with Done.
If the account still appears as not registered, check these common causes in Authenticator:
- Update Authenticator to the latest version. Versions older than 12 months are not supported.
- In Authenticator, go to Settings and make sure:
- App updates is turned on
- Turn off battery optimization is enabled
- Notification Settings > Show notifications is turned on
- Make sure the device has network connectivity. If using mobile data, try Wi-Fi, and vice versa. Make sure Airplane mode is off.
- Make sure the device date and time are correct and the device is fully up to date.
- If using a VPN, disconnect it and try again.
If the app shows the account but it still does not complete registration, that can indicate the Authenticator setup is incomplete. In that case:
- On the sign-in page, use Sign in another way if another verification method is available.
- After access is restored, go to Security info and add Microsoft Authenticator again, then complete the QR scan and approval flow.
- If no other sign-in method works, contact the organization’s IT admin and ask for an MFA re-registration reset. The accepted guidance for this scenario is to have the admin require MFA re-registration.
If repeated sign-in attempts were made during setup, Microsoft Entra multifactor authentication can temporarily block more attempts. Wait and try again later, or use a different MFA method if available.