Authentication methods policy
Observed content change
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant; check the dates against your plans.
Changed article references · 11 added · 1 removed
- Removed link: Authentication methods in Microsoft Entra ID
overview-authentication - Added image: Illustrative screenshot of John Doe's authentication methods showing a usable passkey with High assurance and an expired Temporary Access Pass with no assurance level.
media/concept-authentication-methods-manage/credential-assurance.png - Added image: Screenshot of John Doe's user overview with the example account [email protected], an identity verification status summary, and an Identity verification card with View details.
media/concept-authentication-methods-manage/user-overview-identity-verification.png - Added link: Identity verification licensing
../../fundamentals/licensing#identity-verification - Added link: Verified ID audit activities
../monitoring-health/reference-audit-activities#verified-id - Added link: Security Reader
../role-based-access-control/permissions-reference#security-reader - Added link: Credential assurance classification
concept-authentication-passkeys-fido2#credential-assurance-classification-preview - Added link: Passkey credential provenance
concept-authentication-passkeys-fido2#credential-provenance - Added link: Identity verification collection prerequisites
concept-authentication-verified-id#prerequisites - Added link: Migrate to the Authentication methods policy
how-to-authentication-methods-manage - Added link:
media/concept-authentication-methods-manage/credential-assurance.png#lightbox - Added link:
media/concept-authentication-methods-manage/user-overview-identity-verification.png#lightbox
[added: The Authentication methods policy in Microsoft Entra ID is a policy that lets administrators configure authentication methods for users and groups. You can configure methods to meet your organization's goals for user experience and security.]
Before: No saved wording on this side.
After: The Authentication methods policy in Microsoft Entra ID is a policy that lets administrators configure authentication methods for users and groups. You can configure methods to meet your organization's goals for user experience and security.
[added: This article covers the core policy and related user authentication information first, including method usability, credential provenance, and identity verification history. The second section covers migration from legacy multifactor authentication (MFA) and self-service password reset (SSPR) policies.]
Before: No saved wording on this side.
After: This article covers the core policy and related user authentication information first, including method usability, credential provenance, and identity verification history. The second section covers migration from legacy multifactor authentication (MFA) and self-service password reset (SSPR) policies.
[added: The following illustrative example shows Credential assurance for a passkey on the user's Authentication methods page. Usability and assurance are separate: an assurance label doesn't establish that a method can currently sign in.]
Before: No saved wording on this side.
After: The following illustrative example shows Credential assurance for a passkey on the user's Authentication methods page. Usability and assurance are separate: an assurance label doesn't establish that a method can currently sign in.
[added: For the meanings of Low, Medium, and High, see Credential assurance classification. During preview, credential assurance classification and provenance are available only for passkeys.]
Before: No saved wording on this side.
After: For the meanings of Low, Medium, and High, see Credential assurance classification. During preview, credential assurance classification and provenance are available only for passkeys.
[added: Credential provenance records how a passkey was established and is separate from the user's account-level identity verification status. During preview, credential provenance is available only for passkeys.]
Before: No saved wording on this side.
After: Credential provenance records how a passkey was established and is separate from the user's account-level identity verification status. During preview, credential provenance is available only for passkeys.
[added: To review credential assurance and provenance, open the user's Authentication methods page and select a passkey to view its details. The method details show Credential assurance, registration history, and Credential provenance. For more information, see Passkey credential provenance.]
Before: No saved wording on this side.
After: To review credential assurance and provenance, open the user's Authentication methods page and select a passkey to view its details. The method details show Credential assurance, registration history, and Credential provenance. For more information, see Passkey credential provenance.
[added: To view a user's identity verification status and history, use at least the Security Reader role.]
Before: No saved wording on this side.
After: To view a user's identity verification status and history, use at least the Security Reader role.
[added: Open the user's Identity verification page to review current identity verification status and verification history. This is a separate page in the user's navigation, not part of Authentication methods or an authentication method's details.]
Before: No saved wording on this side.
After: Open the user's Identity verification page to review current identity verification status and verification history. This is a separate page in the user's navigation, not part of Authentication methods or an authentication method's details.
[added: The user's Overview also summarizes identity verification status. Select View details in the Identity verification card to review more information.]
Before: No saved wording on this side.
After: The user's Overview also summarizes identity verification status. Select View details in the Identity verification card to review more information.
[added: The Identity verification page shows the current status, verification event count, current event ID, and verification history.]
Before: No saved wording on this side.
After: The Identity verification page shows the current status, verification event count, current event ID, and verification history.
[added: Note A planned enhancement to source information for identity verification events will identify the verification type: EmployeeID, Tenant Issued, or Identity Verification Partner. These details aren't yet available.]
Before: No saved wording on this side.
After: Note A planned enhancement to source information for identity verification events will identify the verification type: EmployeeID, Tenant Issued, or Identity Verification Partner. These details aren't yet available.
[added: Note To view status and history, first enable tenant-wide Collect identity verification history. See Identity verification collection prerequisites. Check Identity verification licensing to confirm that reporting is available for your organization. An unavailable view isn't evidence that verification failed.]
Before: No saved wording on this side.
After: Note To view status and history, first enable tenant-wide Collect identity verification history. See Identity verification collection prerequisites. Check Identity verification licensing to confirm that reporting is available for your organization. An unavailable view isn't evidence that verification failed.
[added: View Question it answers Interpretation boundary Current account verification status What verification state applies to the account now? A past successful event doesn't necessarily establish the current effective state. Verification history Which verification events or changes are recorded for this user? History isn't a complete audit-retention guarantee or proof that every recorded verification is still valid. Credential provenance How was this particular passkey established? Account-level verification doesn't establish the provenance of every credential on the account.]
Before: No saved wording on this side.
After: View Question it answers Interpretation boundary Current account verification status What verification state applies to the account now? A past successful event doesn't necessarily establish the current effective state. Verification history Which verification events or changes are recorded for this user? History isn't a complete audit-retention guarantee or proof that every recorded verification is still valid. Credential provenance How was this particular passkey established? Account-level verification doesn't establish the provenance of every credential on the account.
[added: The first two views are on Identity verification. Credential provenance is in the passkey's details under Authentication methods, not in the account-level verification history.]
Before: No saved wording on this side.
After: The first two views are on Identity verification. Credential provenance is in the passkey's details under Authentication methods, not in the account-level verification history.
[added: Current status and historical events describe different points in the verification lifecycle. Credential or document issuance, verification recorded by Microsoft Entra ID, expiration, and later credential presentation aren't the same event. Don't treat a later presentation date as the date of the original identity proofing.]
Before: No saved wording on this side.
After: Current status and historical events describe different points in the verification lifecycle. Credential or document issuance, verification recorded by Microsoft Entra ID, expiration, and later credential presentation aren't the same event. Don't treat a later presentation date as the date of the original identity proofing.
[added: Verification and passkey registration are separate outcomes. Completing verification doesn't establish that onboarding or recovery finished, that every existing method is usable, or that access was granted. For method-level context, see Passkey credential provenance.]
Before: No saved wording on this side.
After: Verification and passkey registration are separate outcomes. Completing verification doesn't establish that onboarding or recovery finished, that every existing method is usable, or that access was granted. For method-level context, see Passkey credential provenance.
[added: For service-level operations and failure investigation, see Verified ID audit activities. Audit events don't replace the account's current verification status or an individual passkey's credential assurance.]
Before: No saved wording on this side.
After: For service-level operations and failure investigation, see Verified ID audit activities. Audit events don't replace the account's current verification status or an individual passkey's credential assurance.
[added: For reporting entitlements, see Identity verification licensing.]
Before: No saved wording on this side.
After: For reporting entitlements, see Identity verification licensing.
[added: Administrators can overwrite identity verification events and credential provenance to align the recorded information with their organization's verification and credential management processes. This is useful when:]
Before: No saved wording on this side.
After: Administrators can overwrite identity verification events and credential provenance to align the recorded information with their organization's verification and credential management processes. This is useful when:
[added: Your organization performs robust in-person identity verification and needs to reflect that verification in the user's record.]
Before: No saved wording on this side.
After: Your organization performs robust in-person identity verification and needs to reflect that verification in the user's record.
Source: Microsoft source · © Microsoft · MIT.
Read the current Microsoft source · Link to this observation · Compare any two versions
Other changed sections
- Migration from legacy policies
- Manage authentication methods for Microsoft Entra ID
Observation details
- Observed by ChangeIntel
- today 08:42 UTC
- Source update metadata
- today 08:34 UTC
- First observed on this installation
- 5 Oct 17:20 UTC
- Last successful check
- today 08:42 UTC
- Next check due
- today 14:42 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.