Microsoft Entra ID
Authentication

Authentication methods policy

In brief

The article now covers user method usability, passkey credential assurance and provenance in preview, identity verification history, legacy policy migration, and limitations including individual-user targeting removal and a 20 KB policy size limit.

What Entra admins need to know

Review policies that target individual users or many groups, since registrations or policy saves may fail. Administrators can also use the documented portal views to assess usable methods and passkey details.

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.

ManageAuthentication methods policy overview

The Authentication methods policy in Microsoft Entra ID is a policy that lets administrators configure authentication methods for Microsoft Entra ID

Microsoft Entra ID allows the use of a range of authenticationusers and groups. You can configure methods to support a wide variety of sign-in scenarios. For an overview of the available options, see Authentication methods in Microsoft Entra ID. Administrators can specifically configure each method to meet theiryour organization's goals for user experience and security.

This topic explains how to managearticle covers the core policy and related user authentication methods for Microsoft Entra ID,information first, including method usability, credential provenance, and how configuration options affect user sign-inidentity verification history. The second section covers migration from legacy multifactor authentication (MFA) and self-service password reset scenarios. (SSPR) policies.

Authentication methods policy

Only the converged registration experience is aware of the Authentication methods policy. Users in scope of the Authentication methods policy but not the converged registration experience won't see the correct methods to register.

Known issues and limitations

  • In recent updates, we removed the ability to target individual users. Previously targeted users will remain in the policy, but we recommend moving them to a targeted group.
  • Registration of an authentication method can fail if many groups are included in the Authentication methods policy or a registration campaign. We recommend consolidating multiple groups into a single group for each authentication method. To maintain registration for users during consolidation, add the new group and remove current groups in the same operation.

Usable and non-usable methods for users

Administrators can view user authentication methods in the Microsoft Entra admin center. Usable methods are listed first, followed by non-usable methods.

Each authentication method can become nonusable for different reasons. For example, a Temporary Access Pass might expire, or a FIDO2 security key might fail attestation. The portal gets updated to explain why the method isn't usable.

Authentication methods that are no longer available due to Require re-register multifactor authentication also appear here.

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.

For the meanings of Low, Medium, and High, see Credential assurance classification. During preview, credential assurance classification and provenance are available only for passkeys.

:::image type="content" source="media/concept-authentication-methods-manage/credential-assurance.png" alt-text="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." lightbox="media/concept-authentication-methods-manage/credential-assurance.png":::

Credential provenance (preview)

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.

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.

Identity verification status and history

To view a user's identity verification status and history, use at least the Security Reader role.

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.

The user's Overview also summarizes identity verification status. Select View details in the Identity verification card to review more information.

:::image type="content" source="media/concept-authentication-methods-manage/user-overview-identity-verification.png" alt-text="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." lightbox="media/concept-authentication-methods-manage/user-overview-identity-verification.png":::

The Identity verification page shows the current status, verification event count, current event ID, and verification history.

ViewQuestion it answersInterpretation boundary
Current account verification statusWhat verification state applies to the account now?A past successful event doesn't necessarily establish the current effective state.
Verification historyWhich 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 provenanceHow was this particular passkey established?Account-level verification doesn't establish the provenance of every credential on the account.

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.

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.

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.

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.

For reporting entitlements, see Identity verification licensing.

Manage identity verification for a user

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:

  • Your organization performs robust in-person identity verification and needs to reflect that verification in the user's record.
  • Your organization uses a credential management service for credential issuance and lifecycle management and needs to reflect that process in the credential's provenance.

Review account-level verification events on the user's Identity verification page and credential-level provenance in the selected passkey's details under Authentication methods. An administrative overwrite isn't evidence that the user completed identity verification.

For operation-specific entitlements, see Identity verification licensing.

Migration from legacy policies

The following sections explain legacy policy settings, how policies work together, and migration states. For automated and manual migration procedures, see Migrate to the Authentication methods policy.

Legacy MFA and SSPR policies

Two other policies, located in Multifactor authentication settings and Password reset settings, provide a legacy way to manage some authentication methods for all users in the tenant. You can't control who uses an enabled authentication method, or how the method can be used.

:::image type="content" border="true" source="./media/concept-authentication-methods-manage/password-reset.png" alt-text="Screenshot of password reset settings.":::

How policies work together

Settings aren't synchronized between the policies, which allows administrators to manage each policy independently. Microsoft Entra ID respects the settings in all of the policies so a user who is enabled for an authentication method in any policy can register and use that method. To prevent users from using a method, it must be disabled in all policies.

Similarly, let's suppose you enable Voice calls for a group. After you enable it, you find that even users who aren't group members can sign-in with a voice call. In this case, it's likely those users are enabled for Mobile phone in the legacy SSPR policy or Call to phone in the legacy MFA policy.

Migration between policies

The Authentication methods policy provides a migration guide to help unify administration of all authentication methods. All desired methods can be enabled in the Authentication methods policy if the policy targets intended user groups, or all users. The authentication methods migration guide automates the steps to audit your current policy settings for MFA and SSPR, and consolidate them in the Authentication methods policy. You can access the guide from the Microsoft Entra admin center by browsing to Entra ID > Authentication methods > Policies.

:::image type="content" border="false" source="media/how-to-authentication-methods-manage/wizard-entry-point.png" alt-text="Screenshot of the Authentication methods policy blade with highlighted wizard entry point.":::

You can also migrate policy settings manually. The migration has three settings to let you move at your own pace, and avoid problems with sign-in or SSPR during the transition.

In the future, both of these features will be integrated with the Authentication methods policy.

Known issues and limitationsRelated content

  • In recent updates, we removed the ability to target individual users. Previously targeted users will remain in the policy, but we recommend moving them to a targeted group.
  • Registration of an authentication method can fail if many groups are included in the Authentication methods policy or a registration campaign. We recommend consolidating multiple groups into a single group for each authentication method. To maintain registration for users during consolidation, add the new group and remove current groups in the same operation.How to migrate MFA and SSPR policy settings to the Authentication methods policy

Usable and non-usable methods for users

Administrators can view user authentication methods in the Microsoft Entra admin center. Usable methods are listed first, followed by non-usable methods.

Each authentication method can become nonusable for different reasons. For example, a Temporary Access Pass might expire, or a FIDO2 security key might fail attestation. The portal gets updated to explain why the method isn't usable.

Authentication methods that are no longer available due to Require re-register multifactor authentication also appear here.

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…