Authentication methods policy
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit d55e854 · +95 −26 lines · also on GitHub
11
---
2
−title: Manage authentication methods
3
−description: Learn about the authentication methods policy and different ways to manage authentication methods.
2
+title: Authentication methods policy
3
+description: Learn about the Authentication methods policy, user method usability, passkey provenance, identity verification history, and legacy policy migration.
44
ms.topic: concept-article
5
−ms.date: 03/04/2025
5
+ms.date: 11/10/2026
66
ms.reviewer: jpettere
7
−ms.custom: sfi-image-nochange
8
−# Customer intent: As an identity administrator, I want to understand what authentication options are available in Microsoft Entra ID and how I can manage them.
7
+ms.custom: sfi-image-nochange, msecd-doc-authoring-108
8
+author: tilarso
9
+ms.author: tilarso
10
+ai-usage: ai-assisted
11
+# Customer intent: As an identity administrator, I want to understand the Authentication methods policy and related user authentication information so that I can manage authentication methods and plan migration from legacy policies.
912
---
10
−# Manage authentication methods for Microsoft Entra ID
13
+# Authentication methods policy overview
1114
12
−Microsoft Entra ID allows the use of a range of authentication methods to support a wide variety of sign-in scenarios. For an overview of the available options, see [Authentication methods in Microsoft Entra ID](overview-authentication.md). Administrators can specifically configure each method to meet their goals for user experience and security. This topic explains how to manage authentication methods for Microsoft Entra ID, and how configuration options affect user sign-in and password reset scenarios.
15
+<a id="manage-authentication-methods-for-microsoft-entra-id"></a>
1316
17
+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.
18
+
19
+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.
20
+
1421
## Authentication methods policy
1522
1623
The Authentication methods policy is the recommended way to manage authentication methods, including modern methods like passwordless authentication. [Authentication Policy Administrators](~/identity/role-based-access-control/permissions-reference.md#authentication-policy-administrator) can edit this policy to enable authentication methods for all users or specific groups.
⋯ 10 unchanged lines
2734
2835
Only the [converged registration experience](concept-registration-mfa-sspr-combined.md) 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.
2936
30
−## Legacy MFA and SSPR policies
37
+### Known issues and limitations
38
+- 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.
39
+- 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.
3140
41
+ >[!NOTE]
42
+ >You might not be able to save updates to the Authentication methods policy if it targets many groups and the policy size exceeds 20 KB. To avoid this limitation, consolidate targeted groups as much as possible.
43
+
44
+### Usable and non-usable methods for users
45
+
46
+Administrators can view user authentication methods in the Microsoft Entra admin center. Usable methods are listed first, followed by non-usable methods.
47
+
48
+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.
49
+
50
+Authentication methods that are no longer available due to **Require re-register multifactor authentication** also appear here.
51
+
52
+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.
53
+
54
+For the meanings of **Low**, **Medium**, and **High**, see [Credential assurance classification](concept-authentication-passkeys-fido2.md#credential-assurance-classification-preview). During preview, credential assurance classification and provenance are available only for passkeys.
55
+
56
+:::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":::
57
+
58
+### Credential provenance (preview)
59
+
60
+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.
61
+
62
+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](concept-authentication-passkeys-fido2.md#credential-provenance).
63
+
64
+### Identity verification status and history
65
+
66
+To view a user's identity verification status and history, use at least the [Security Reader](../role-based-access-control/permissions-reference.md#security-reader) role.
67
+
68
+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.
69
+
70
+The user's **Overview** also summarizes identity verification status. Select **View details** in the **Identity verification** card to review more information.
71
+
72
+:::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":::
73
+
74
+The **Identity verification** page shows the current status, verification event count, current event ID, and verification history.
75
+
76
+> [!NOTE]
77
+> 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.
78
+
79
+> [!NOTE]
80
+> To view status and history, first enable tenant-wide **Collect identity verification history**. See [Identity verification collection prerequisites](concept-authentication-verified-id.md#prerequisites). Check [Identity verification licensing](../../fundamentals/licensing.md#identity-verification) to confirm that reporting is available for your organization. An unavailable view isn't evidence that verification failed.
81
+
82
+| View | Question it answers | Interpretation boundary |
83
+| --- | --- | --- |
84
+| Current account verification status | What verification state applies to the account now? | A past successful event doesn't necessarily establish the current effective state. |
85
+| 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. |
86
+| Credential provenance | How was this particular passkey established? | Account-level verification doesn't establish the provenance of every credential on the account. |
87
+
88
+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.
89
+
90
+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.
91
+
92
+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](concept-authentication-passkeys-fido2.md#credential-provenance).
93
+
94
+For service-level operations and failure investigation, see [Verified ID audit activities](../monitoring-health/reference-audit-activities.md#verified-id). Audit events don't replace the account's current verification status or an individual passkey's credential assurance.
95
+
96
+For reporting entitlements, see [Identity verification licensing](../../fundamentals/licensing.md#identity-verification).
97
+
98
+
99
+### Manage identity verification for a user
100
+
101
+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:
102
+
103
+- Your organization performs robust in-person identity verification and needs to reflect that verification in the user's record.
104
+- Your organization uses a credential management service for credential issuance and lifecycle management and needs to reflect that process in the credential's provenance.
105
+
106
+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.
107
+
108
+For operation-specific entitlements, see [Identity verification licensing](../../fundamentals/licensing.md#identity-verification).
109
+
110
+## Migration from legacy policies
111
+
112
+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](how-to-authentication-methods-manage.md).
113
+
114
+### Legacy MFA and SSPR policies
115
+
32116
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.
33117
34118
>[!Important]
⋯ 7 unchanged lines
42126
43127
:::image type="content" border="true" source="./media/concept-authentication-methods-manage/password-reset.png" alt-text="Screenshot of password reset settings.":::
44128
45
−## How policies work together
129
+### How policies work together
46130
47131
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.
48132
⋯ 13 unchanged lines
62146
63147
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.
64148
65
−## Migration between policies
149
+### Migration between policies
66150
67151
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](https://entra.microsoft.com) by browsing to **Entra ID** > **Authentication methods** > **Policies**.
68152
69
−:::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."
153
+:::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.":::
70154
71155
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.
72156
⋯ 24 unchanged lines
97181
> - The SSPR administrator policy: admins can continue to register and use any methods listed under the legacy SSPR administrator policy or methods they're enabled to use in the Authentication methods policy.
98182
>
99183
> In the future, both of these features will be integrated with the Authentication methods policy.
100
−
101
−## Known issues and limitations
102
−- 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.
103
−- 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.
104
−
105
− >[!NOTE]
106
− >You might not be able to save updates to the Authentication methods policy if it targets many groups and the policy size exceeds 20 KB. To avoid this limitation, consolidate targeted groups as much as possible.
107
−
108
−## Usable and non-usable methods for users
109
−
110
−Administrators can view user authentication methods in the Microsoft Entra admin center. Usable methods are listed first, followed by non-usable methods.
111
−
112
−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.
113
−
114
−Authentication methods that are no longer available due to **Require re-register multifactor authentication** also appear here.
115184
116185
## Related content
117186
⋯ 4 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy today 17:04 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.