Signing in with passkey in Microsoft Authenticator gets stuck in “Connecting…”

Question

Signing in with passkey in Microsoft Authenticator gets stuck in “Connecting…”

Karolina Johansson (External) 0

A couple of weeks ago I started noticing problems with the Authenticator app.

The most disrupting issue is that signing in with the passkey I have stored in the app isn’t working anymore. This passkey is used for a specific account in a tenant and is not my usual work account.

It gets stuck in “Connecting…” and never continues to for instance Face ID check.

The app is the latest version, I have the latest iOS, both iPhone and laptop are updated to the latest versions.

I also tried removing the passkey and created a new one. It hasn’t helped.

0 comments

Answer recommended by moderator

Karolina Johansson (External) 0

Hi @Anonymous
I installed a software update today on my Mac. The update appeared two days ago, from 26.5 to 26.5.1. And now it works signing in with the Passkey and Authenticator. Seems like there was an issue in the Mac software that was causing the issue.

Anonymous

2026-06-05T08:25:47.2966667+00:00

Hi Karolina Johansson (External)

I'm glad to hear that it works and thank you so much for your sharing.

Best regards

2 additional answers

Your answer

Anonymous

2026-06-05T08:25:47.2966667+00:00

Hi Karolina Johansson (External)

I'm glad to hear that it works and thank you so much for your sharing.

Best regards

Answer 1

Anonymous

Hi Karolina Johansson (External)

Since recreating the passkey and reinstalling the Authenticator app didn’t resolve the issue, you can try to reset your authentication methods (MFA registration).

An admin can reset MFA settings by following this article: Manage authentication methods for Microsoft Entra multifactor authentication - Microsoft Entra ID | Microsoft Learn

After the reset, these users can:

Sign back in to your account
Re-register Microsoft Authenticator
Recreate the passkey

If you are not admin, you can contact your organization's IT administrator and request a reset of your MFA settings.

(Please understand that we're not Microsoft support, this is a user-to-user support forum. Moderators have no backend access and cannot directly intervene in Microsoft products. We provide only technical guidance and best-practice recommendations based on reported issues)

I hope this information helps and if you have any question, please feel free to ask!

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Anonymous

2026-05-31T23:50:05.96+00:00

Hi Karolina Johansson (External)

Just checking in to see if you've had a chance to check my previous reply.

Please let me know if you have any further questions.
Karolina Johansson (External) 0 Reputation points

2026-06-01T09:17:06.51+00:00

Hi @Anonymous

Thank you for posting your suggestion on how to resolve it. I'm waiting to hear from our IAM team what they say about my report of not being able to sign in with the passkey. I haven't shared your suggestion yet.
Anonymous

2026-06-02T03:42:43.59+00:00

Hi Karolina Johansson (External)

Thank you for your update. If you have any questions, please feel free to reach out.
Karolina Johansson (External) 0 Reputation points

2026-06-05T04:48:04.6566667+00:00

Hi @Anonymous

Resetting the MFA settings didn't work either unfortunately.
Anonymous

2026-06-05T07:46:40.47+00:00

Hi Karolina Johansson (External)

If the IAM team investigates and confirms there is no misconfiguration on their side, and resetting MFA does not resolve the issue, I recommend reaching out to your IT team to submit a support ticket with Microsoft. They can provide the necessary tenant IDs and diagnostic data, which are essential for Microsoft’s engineering teams to investigate a potential product issue.

More details on how to get help from Microsoft 365 support can be found here: Get support - Microsoft 365 admin | Microsoft Learn

Answer 2

The behavior matches known issues where passkey registration or attestation in Microsoft Authenticator fails or becomes invalid, causing sign-in to hang or never reach Face ID.

Use the following steps for the affected account/tenant on iOS:

Remove the existing passkey from Authenticator
- Open Microsoft Authenticator.
- Tap the account name for the affected tenant.
- Tap Settings > Delete passkey.
Remove the passkey from Security info
- After deleting in Authenticator, go to Security info for that account.
- If the passkey is still listed, select Delete to remove it.
Re-register the passkey
- From the same account, follow the tenant’s instructions to register a new passkey in Authenticator.
- If registration fails with an error like “passkey already exists,” delete any locally stored passkey in Authenticator again and retry registration. This situation can occur if the passkey was stored locally in the app but never successfully registered on the authentication server (for example, due to a timeout or provider not being permitted).
Retry sign-in with the new passkey
- Start a new sign-in flow for that specific tenant account.
- When prompted, choose to sign in with the new passkey in Authenticator and complete Face ID.

If the issue persists only for this tenant/account while others work, it can indicate a tenant configuration or attestation issue (for example, attestation or passkey provider not permitted). In that case, the tenant administrator should review their passkey configuration using the Microsoft Entra ID guidance for enabling and supporting passkeys in Authenticator.

References: