failed to create passkey

Question

when i was logging in to this site on my phone is tried to create a passkey but failed because something went wrong. any reasons for this?

Answer 1

Hi aa,

It might be because you did not have 2 factor authentication enabled, as Passkeys typically require that, hence the general message.

I hope this information helps. If you have any more questions, don't hesitate to reach out.

Otherwise, please take a moment to rate the answer. Wishing you good luck!

Answer 2

Hi aa,

To confirm, you have a passkey stored on your phone for this Microsoft account, and when you tried to scan to sign in, it did not work. Is that correct?

I’m eager to hear back and work together to find a solution.

Answer 3

There could be several reasons why you failed to create a passkey when trying to log in on your phone. Here are some common issues:

1. Local Storage Issue: Sometimes, the passkey may get stored locally in the Authenticator app but isn't registered on the authentication server. This can happen if the connection times out or if the passkey provider is not permitted.
2. Existing Passkey Conflict: If you see an error indicating that the passkey already exists, it may mean that a passkey was created locally in the Authenticator. In this case, you would need to delete the locally created passkey and try registering again.
3. Connectivity Problems: Ensure that your device has a stable internet connection while attempting to create the passkey, as connectivity issues can hinder the registration process.
4. Bluetooth Restrictions: If your organization has restricted Bluetooth usage, this could also affect the ability to register a passkey, especially if cross-device registration is required.

If you continue to experience issues, consider checking the settings in your Authenticator app or contacting support for further assistance.

---

References:

• Frequently asked questions about passkey support in Microsoft Authenticator
• Register passkeys in Authenticator on Android or iOS devices