A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Based on the symptoms (“Authentication did not complete” after scanning the QR code and entering the PIN in Microsoft Authenticator), the sign-in is failing at the passkey/MFA step rather than the QR scan itself.
Work through these checks in order on the iPhone and laptop:
- Confirm Authenticator is unlocked
- Before scanning the QR code, open Microsoft Authenticator on the iPhone and make sure it is fully unlocked (Face ID/Touch ID/PIN already entered).
- If the app is locked when the prompt comes in, the entry box or confirmation step may not complete and will cause the “cannot complete”/“Authentication did not complete” behavior.
- Check notifications and silent mode
- On the iPhone, ensure notifications are enabled for Microsoft Authenticator:
- In iOS Settings → Notifications → Authenticator → allow notifications, sounds, and banners.
- Make sure Focus/Do Not Disturb is off and that notifications are not being delivered silently. Silent or blocked notifications can prevent the approval step from completing.
- On the iPhone, ensure notifications are enabled for Microsoft Authenticator:
- Verify Authenticator app version
- In Microsoft Authenticator → Settings, confirm App updates are turned on and that the app is the latest version.
- Out-of-date versions can cause sign-in and QR/passkey flows to fail.
- Check network connectivity
- Ensure both the laptop and the iPhone are connected to the internet.
- If the iPhone is on mobile data, briefly switch to Wi‑Fi (or vice versa) and try again. Network disruptions can cause the “Authentication did not complete” error.
- Verify device date and time
- On the iPhone, ensure Date & Time are set correctly (preferably “Set Automatically”).
- Incorrect time can break authentication flows.
- Try an alternate sign-in method if available
- On the laptop sign-in screen, choose “Sign in another way” (if shown) and use a different MFA method (SMS, call, or another passkey) to get in once.
- After signing in, review the account’s passkeys and remove any that no longer apply, then recreate the passkey for this laptop.
- If the message is specifically “Authentication did not complete”
- This message is explicitly associated with:
- Locked app
- Silent/disabled notifications
- Outdated app
- Network issues
- Incorrect device time
- Re-test after each change above.
- This message is explicitly associated with:
- If multiple attempts are blocked
- If there have been many failed attempts, Microsoft Entra multifactor authentication may temporarily block further sign-ins as a protection measure. Wait and then try again, or use a different MFA method if offered.
- If this is a work account, the organization’s IT admin can review Entra sign-in logs and MFA configuration to see if any policies are blocking passkey/Bluetooth-based authentication on these new laptops.
If, after these steps, the QR/passkey flow still fails on both laptops, escalate to the organization’s IT/Entra administrator to:
- Check whether passkey/Bluetooth-based authentication is allowed by policy for these devices.
- Review sign-in logs for the affected users at the time of failure.
- Temporarily require re-registration of MFA and reconfigure the methods.
References: