Error while registering Security Key (FIDO2) – “We’re sorry, we ran into a problem” with Correction ID

Question

Error while registering Security Key (FIDO2) – “We’re sorry, we ran into a problem” with Correction ID

Satya 0

Hi Team,

I am trying to register a Security Key (FIDO2 – Yubico Security Key NFC Type-A) under My Security Info (aka.ms/mysecurityinfo), but I keep getting the following error popup:

“We’re sorry, we ran into a problem. Please choose ‘Next’ to try again.”

The error message shows:

Correlation ID: 6bac8660-e6d4-4be4-9ceb-affb2ffda117
Timestamp: 2025-11-14T08:08:07.45Z

I have already tried:

Using a different browser (Edge/Chrome)

Using an incognito window

Removing and re-adding the key

Trying from another PC

Checking if FIDO2 is enabled in Azure AD

Checking Authentication Methods policy

Ensuring the key is not previously registered

Still, the same issue occurs.

What I want to confirm:

Is this error related to a tenant policy, Conditional Access, or Authentication Methods policy?

Do I need to enable any extra settings under:

Azure AD → Security → Authentication methods → FIDO2 Security Key

Screenshot_14-11-2025_133856_mysignins.microsoft.com 1.jpeg

Azure AD → Devices → Device settings

Does Microsoft see any backend failure related to my Correction ID?

Is this a known issue with YubiKey Security Key NFC Type-A on certain tenants?

What steps should I follow to resolve this?

Please help me understand what is causing this registration failure and how to fix it.

Morgan Thorpe 0 Reputation points

2026-03-25T01:19:18.7633333+00:00

A Conditional Access policy that targets "User Actions" of "Register or join devices" seems to block registration of FIDO2 hardware based keys. Try exempting from that policy if you have one, and ensure there isn't any CA policy for User Actions of "Register Security Information" that's blocking. These correlation ID's should be found in your non-interactive sign-in logs.

1 answer

Your answer

Morgan Thorpe 0 Reputation points

2026-03-25T01:19:18.7633333+00:00

A Conditional Access policy that targets "User Actions" of "Register or join devices" seems to block registration of FIDO2 hardware based keys. Try exempting from that policy if you have one, and ensure there isn't any CA policy for User Actions of "Register Security Information" that's blocking. These correlation ID's should be found in your non-interactive sign-in logs.

Answer 1

Yes, this error is usually caused by a policy in the tenant.

It can come from Conditional Access, the FIDO2 authentication method settings, or the device settings that control whether security keys can be registered.

You should confirm that FIDO2 is enabled for your user under Authentication methods --> FIDO2 Security Key, and that security key registration is allowed under Devices --> Device settings. If either of those is restricted, the key will fail during registration.

The correlation ID helps identify the exact block, and it’s not a known issue with the YubiKey NFC Type-A.

The usual fix is checking those three areas for any restrictions and then trying the registration again once the policy conflict is resolved.

Share via

Error while registering Security Key (FIDO2) – “We’re sorry, we ran into a problem” with Correction ID

What I want to confirm:

1 answer

Your answer