Microsoft Entra ID
Authentication

Passkeys (FIDO2) authentication method in Microsoft Entra ID

In brief

The documentation describes credential provenance and High, Medium, and Low assurance classifications for individual passkeys, including their lifecycle, registration history, and administrative overrides.

What Entra admins need to know

Administrators can review these details per passkey, but assurance labels do not by themselves confirm usability, successful verification, or Conditional Access access. No action is required.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

For more details, see Get started with phishing-resistant MFA deployment in Microsoft Entra ID.

Credential provenance (preview)

Credential provenance records how a passkey was established, including its relationship to identity verification at registration. It's separate from the user's current account verification status and from passkey device or provider attestation.

An account can have passkeys with different provenance. Review the passkey involved in an operation rather than treating every credential on the account as equivalent.

On the user's Authentication methods page, select a passkey to open its details. The details show Credential assurance, registration history, and Credential provenance for that credential. A visible assurance label doesn't prove a successful verification ceremony.

The following illustrative example shows Employee ID under Verified with and Temporary Access Pass under Derived from. These edited example values aren't evidence of a live verification or registration event.

:::image type="content" source="media/concept-authentication-passkeys-fido2/passkey-credential-provenance.png" alt-text="Illustrative screenshot of John Doe's passkey details showing High assurance, Employee ID under Verified with, and Temporary Access Pass under Derived from." lightbox="media/concept-authentication-passkeys-fido2/passkey-credential-provenance.png":::

The user's separate Identity verification page shows account-level verification status and history. It isn't part of the authentication method details.

Administrators can overwrite credential provenance. An administrative overwrite is separate from the user completing identity verification and doesn't prove a successful verification ceremony. For administrative operations and entitlements, see Manage identity verification for a user and Identity verification licensing.

Usability is separate from assurance. Method details retain assurance information for an unusable method so that an administrator can investigate it. A displayed assurance label doesn't establish that the passkey can currently sign in or that an access policy will grant access.

If provenance information is missing, don't infer that identity verification succeeded or failed. Check whether the credential and registration path are supported. Missing information isn't the same as a recorded change to a credential's trust context.

For account-level records, see Identity verification status and history. For reporting entitlements, see Identity verification licensing. For investigation guidance, see Identity verification reporting.

Credential assurance classification (preview)

Credential assurance describes how a passkey is tied to identity verification. Review the classification of the individual passkey rather than treating every credential on a verified account as equivalent.

ClassificationMeaning for passkeys during preview
HighA new passkey is registered through an identity-verified registration journey. Its provenance records identity verification and an intact chain of trust.
MediumAn existing passkey is used in conjunction with identity verification, rather than a new passkey being registered in the identity-verified journey.
LowNo identity-verification provenance is recorded for the passkey, or its recorded chain of trust is broken.

Using an existing passkey with identity verification results in Medium assurance. It isn't the same as registering a new High assurance passkey through an identity-verified journey.

During preview, this classification and credential provenance apply only to passkeys. An absent classification for another authentication method doesn't establish Low assurance. Account-level identity verification status and history are separate from the classification of a particular passkey.

Assurance classification is also separate from device or provider attestation, method usability, and the outcome of a Conditional Access policy. A High label doesn't by itself grant access.

Credential assurance lifecycle

A passkey's assurance can change when its supporting identity verification changes. Expiration or invalidation lowers High or Medium assurance to Low. Successful reverification restores the affected passkey's previous assurance level. These changes apply only to passkeys whose provenance relies on that verification, not every passkey on the account.

Use the following table to distinguish identity verification from credential registration and later changes to trust:

Event or journeyEffect on passkey assurance
Identity verification with an existing passkey.The existing passkey used with identity verification has Medium assurance. This isn't a new identity-verified passkey registration.
New passkey registration through an identity-verified registration journey.The new passkey has High assurance when its provenance records identity verification and an intact chain of trust.
Identity-verified onboarding with new passkey registration.The new passkey has High assurance when registered through the supported identity-verified journey. Completing identity verification alone doesn't establish that passkey registration finished.
Identity-verified recovery with replacement passkey registration.The replacement passkey has High assurance when registered through the supported identity-verified journey. Verification history on the account and provenance on the replacement passkey are separate records.
Supporting identity verification expires.Affected High and Medium assurance passkeys become Low. A historical successful verification event doesn't establish that the supporting verification is still valid.
Supporting identity verification is invalidated.Affected High and Medium assurance passkeys become Low. Review the current verification state as well as the passkey's provenance and classification.
The user completes reverification.A previously High assurance passkey returns to High without new passkey registration. A previously Medium assurance passkey returns to Medium, not High.

Review individual passkeys after each change. Don't assume that verifying an account gives every existing passkey High assurance, or that a change in assurance means a passkey is unusable. For the account-level evidence, see Identity verification status and history.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…