Passkey (FIDO2) authentication method
Observed content change
Read to decideNew content in “Credential provenance (preview)” and 2 more; read it to see whether it concerns you.
Changed article references · 7 added · 0 removed
- Added image: Illustrative screenshot of John Doe's passkey details showing High assurance, Employee ID under Verified with, and Temporary Access Pass under Derived from.
media/concept-authentication-passkeys-fido2/passkey-credential-provenance.png - Added link: Identity verification licensing
../../fundamentals/licensing#identity-verification - Added link: Identity verification status and history
concept-authentication-methods-manage#identity-verification-status-and-history - Added link: identity verification status and history
concept-authentication-methods-manage#identity-verification-status-and-history - Added link: Manage identity verification for a user
concept-authentication-methods-manage#manage-identity-verification-for-a-user - Added link: Identity verification reporting
howto-authentication-methods-activity#identity-verification-reporting - Added link:
media/concept-authentication-passkeys-fido2/passkey-credential-provenance.png#lightbox
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: Note During preview, credential provenance and credential assurance classification are available only for passkeys. Status and provenance reporting don't provide credential-provenance policy enforcement.]
Before: No saved wording on this side.
After: Note During preview, credential provenance and credential assurance classification are available only for passkeys. Status and provenance reporting don't provide credential-provenance policy enforcement.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: The user's separate Identity verification page shows account-level verification status and history. It isn't part of the authentication method details.]
Before: No saved wording on this side.
After: The user's separate Identity verification page shows account-level verification status and history. It isn't part of the authentication method details.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: For account-level records, see Identity verification status and history. For reporting entitlements, see Identity verification licensing. For investigation guidance, see Identity verification reporting.]
Before: No saved wording on this side.
After: For account-level records, see Identity verification status and history. For reporting entitlements, see Identity verification licensing. For investigation guidance, see Identity verification reporting.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: Classification Meaning for passkeys during preview High A new passkey is registered through an identity-verified registration journey. Its provenance records identity verification and an intact chain of trust. Medium An existing passkey is used in conjunction with identity verification, rather than a new passkey being registered in the identity-verified journey. Low No identity-verification provenance is recorded for the passkey, or its recorded chain of trust is broken.]
Before: No saved wording on this side.
After: Classification Meaning for passkeys during preview High A new passkey is registered through an identity-verified registration journey. Its provenance records identity verification and an intact chain of trust. Medium An existing passkey is used in conjunction with identity verification, rather than a new passkey being registered in the identity-verified journey. Low No identity-verification provenance is recorded for the passkey, or its recorded chain of trust is broken.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: Use the following table to distinguish identity verification from credential registration and later changes to trust:]
Before: No saved wording on this side.
After: Use the following table to distinguish identity verification from credential registration and later changes to trust:
[added: Event or journey Effect 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.]
Before: No saved wording on this side.
After: Event or journey Effect 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
Source: Microsoft source · © Microsoft · MIT.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- today 03:28 UTC
- Source update metadata
- 17 Nov 08:34 UTC
- First observed on this installation
- 8 Oct 23:13 UTC
- Last successful check
- today 03:28 UTC
- Next check due
- 19 Nov 03:28 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.