The Authenticator app keeps asking me to set up phone-based login

Follow these steps to fix the issue where Authenticator keeps asking for phone-based login and sign-ins fail after changing screen lock:

1. Check for the "Authentication did not complete" causes
   • Make sure the Microsoft Authenticator app is unlocked when trying to approve sign-ins. If the app is locked, the entry box or prompt may not appear.
   • Ensure notifications are enabled for Microsoft Authenticator on the phone and not set to silent/Do Not Disturb. If notifications are silent, you might miss prompts and think sign-in is failing.
   • Confirm the app is up to date by installing the latest version from the store. Outdated versions can cause sign-in issues.
   • Verify the phone has a working internet connection (try switching between Wi‑Fi and mobile data) so the app can complete the authentication.
   • Check that the date and time on the device are correct and preferably set automatically.
2. Fix issues caused by screen lock or device security changes Changing the screen lock (PIN, fingerprint, Face ID) can interfere with passwordless or phone-based sign-in if device security no longer meets requirements. On Android work/school accounts in particular:
   • Ensure the device requires a PIN or biometric to unlock. If recently changed, re‑enable Face ID or fingerprint in device settings, restart the device, then unlock using that method and try enabling or using passwordless sign-in again.
   • If using Android for Work / Work Profile, confirm PIN or biometric is enabled for that work profile as well.
   • Make sure hardware encryption is enabled on the device. For guidance, see the steps in Encrypt your Android device referenced in the documentation.
   • Open Authenticator → Settings → Device Registration and confirm the account is registered for passwordless and joined to work or school. If not, sign in on the device registration page and then re‑enable passwordless for the account.
3. Resolve repeated prompts to set up phone-based login If Authenticator keeps asking to set up phone-based login but the flow never completes:
   • Confirm push notifications are enabled and Google Play Services / Google Play Store (on Android) are installed and enabled.
   • If seeing messages like "Sorry, only part of the set up completed successfully" or "We could not complete the sign-in at this time", follow these steps:
     • Go to device Settings and ensure push notifications are enabled for Authenticator.
     • Confirm network connectivity is working.
     • Remove the problematic account from Authenticator and add it again, allowing notifications.
4. If codes or notifications are not arriving or are always expired
   • If notifications only appear when the app is open or never alert:
     • Check that the phone is not in Do Not Disturb/Quiet mode.
     • Verify other apps can send notifications; if not, there may be a system or network issue with the notification channel.
   • If notifications or codes are always expired, set the device clock to automatic time and restart the device so the time is accurate.
5. If still unable to complete 2FA or passwordless sign-in
   • If unable to sign in because the password or 2FA keeps failing, use the Reset your password option provided in the documentation to regain access, then reconfigure Authenticator and phone-based sign-in from a working session.
   • If this is a work or school account and access remains blocked, contact the organization’s IT admin so they can reset multifactor authentication settings in Microsoft Entra and force re‑registration of Authenticator.

These steps address the most common causes: app lock, notification issues, outdated app, network problems, incorrect device time, and device security changes (such as screen lock) that can break passwordless or phone-based login.

References:

• Troubleshoot problems with Microsoft Authenticator
• Authentication did not complete