Verified ID identity verification overview in Microsoft Entra ID
In brief
The documentation expands profiles beyond account recovery to onboarding and access verification, and adds profile purposes, Evaluation/Production modes, supported methods, and prerequisites. It also documents public-cloud availability and automatic collection of verification history when a profile is created.
What Entra admins need to know
Admins evaluating profiles should review the required licensing, roles, cloud availability, and scenario-specific preparation.
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.
title: Verified ID identity verification overview in Microsoft Entra ID
description: Learn how Verified IDcentralized identity verification profiles, profile purposes, and modes support onboarding, recovery, and access verification in Microsoft Entra ID uses identity verification profiles to scope users to secure identity verification flows like account recovery.ID.
ms.reviewer: tilarso
ms.service: entra-id
ms.topic: concept-article
ms.custom: msecd-doc-authoring-108
ms.date: 04/30/11/03/2026
author: tilarso
ms.author: tilarso
ai-usage: ai-assisted
#customer intent: As an identity administrator, I want to understand how Verified ID identity verification works in Microsoft Entra ID so that I can evaluate how identity verification profiles apply to users in my organization.
Verified ID is an identity verification capability in Microsoft Entra ID — it provides a cryptographic proof of a user's verified identity but can't be used to satisfy authentication requirements like sign-in, MFA, or SSPR. Instead, Verified ID serves as the identity proofing layer for scenarios where a user's identity must be re-established — such as account recovery when all authentication methods are lost.
Identity verification profiles are the policy layer that controlscontrol which users can participate in Verified IDthese flows, which provider performs verification,verification method is used, and how identity claims are validated. Today,Profiles support account recovery, onboarding, and verification for access.
Prerequisites
During preview, identity verification profiles and their integrated journeys are available only in the Microsoft public cloud, not in national or sovereign clouds.
To view users' identity verification status and history, enable tenant-wide Collect identity verification history in the authentication methods policy under Authentication methods > Verified ID > Configure > Data collection.
:::image type="content" source="media/concept-authentication-verified-id/collect-identity-verification-history.png" alt-text="Screenshot of the Verified ID profiles are used for account recovery — enabling users who lose all authentication methods to regain access through government-issued identity verification. The profile framework is designed to support additionalConfigure tab with Collect identity verification scenarioshistory enabled under Data collection." lightbox="media/concept-authentication-verified-id/collect-identity-verification-history.png":::
Identity verification history collection becomes available when the setting is enabled. For the user-level views, see Identity verification status and history.
To view a user's identity verification status and history, use at least the Security Reader role.
Before creating a profile:
- Identify whether you need recovery, onboarding, or verification for access.
- For recovery, complete the Verified ID, Face Check, provider subscription, and account-matching preparation in Enable and test account recovery.
- Identify the
future.users to include in your evaluation. - Confirm that your tenant has access to shared profiles and that you have at least the Authentication Policy Administrator role to manage them.
- Microsoft Entra ID P1 or an eligible higher license for identity verification profiles. Review the identity verification licensing requirements for your scenario.
Identity verification profiles
An identity verification profile is a configuration object that defines identity verification behavior for a group of users. Profiles specify:
- Name and description — A display name and description that
identifiesidentify theprofile's purpose.profile. StateProfile purpose — The scenario the profile supports: All, Verification, Onboarding, or Recovery. See Credential support by scenario.- Profile mode — Whether the profile
is enabledoperates in Evaluation ordisabled.Production mode. - User group scope — Which users the profile applies to, defined through group-based assignment.
Identity verification providerVerification method — Thethird-partyidentity verification providerthat performs identity proofing, identified by a verifier DID (Decentralized Identifier) — a unique cryptographic identifieror supported tenant-issued credential used for theverifier in the credential exchange.selected purpose.- Face Check configuration — Settings for Microsoft Entra Verified ID Face Check behavior during verification.
- Profile configuration — The accepted credential issuer, how identity claims map to user properties, and the credential type for the exchange.
Usage configurations— The scenarios the profile applies to, such asrecovery. Additional scenarios may be supported in the future.- Priority — The processing order when a user matches multiple profiles.
Automatic creation throughProfile mode
Use Profile mode to test identity verification or make it operational for the selected Profile purpose.
| Mode | Behavior |
|---|---|
| Evaluation | The scenario can invoke identity verification, but verification doesn't complete the handoff to onboarding, account recovery, or resource access. |
| Production | Identity verification is fully operational for the selected profile purpose, enabling the handoff to the corresponding onboarding, account recovery, or resource-access journey. |
Successful verification in Evaluation mode doesn't mean onboarding or recovery completed or access was granted.
Credential support by scenario
Choose the purpose before selecting a verification method: All, Verification, Onboarding, or Recovery. Use this matrix to choose a credential for your scenario. Confirm release availability in your tenant before deployment.
| Credential | All-purpose profile | Verification for access | Recovery | Onboarding |
|---|---|---|---|---|
| Employee ID | Not supported. | Supported. | Not supported. | Not supported. |
| Custom-issued Verified ID | Not supported. | Supported. | Not supported. | Not supported. |
| Third-party Verified ID from Security Marketplace | Supported. | Supported. | Required. | Required. |
For recovery, keep the third-party provider and account-matching requirements. Don't substitute an employee credential or a custom-issued credential based only on the existence of a shared profile.
For resource-access verification, including risk-based policies, set Profile purpose to All or Verification. All supports identity verification providers only. To use tenant-issued credentials, select Verification. Onboarding and Recovery purposes are for their respective bootstrap journeys.
Create and manage identity verification profiles
Create and manage profiles are automatically created and configured when an Authentication Administrator sets up account recovery throughin the Microsoft Entra admin center (under EntraVerified ID > ID verification profiles > Profiles. On Getting started, review the setup checklist and select Create your first identity verification profile. If profiles already exist, select Profiles > Create profile instead.
Enter a Name and Description, select Profile purpose, and choose Profile mode. The shared wizard also includes user groups, the verification method, account validation, optional custom claim validation, and self-service issuance settings. Review those settings before completing profile creation.
For recovery, use your subscribed identity verification provider and check the user's First name and Last name against the claims returned by that provider. Review any custom claim-validation extension with its owner before using it.
User scope and profile selection
Configure user scope in the shared-profile wizard. Use Include > Select targets > Select groups to start with an evaluation group.
These profile exclusions are separate from the Conditional Access onboarding and recovery exclusion.
Use multiple profiles for different user populations, verification providers, or pilot groups. When a user belongs to groups that match multiple profiles, the system evaluates profiles in priority order and applies the first matching profile.
Lower priority numbers are evaluated first: priority 1 precedes priority 5. Priority numbers are unique, so ties aren't possible.
Review self-service issuance
Review whether to enable self-service issuance, the approved user scope, and the custom credential issuance destination before enabling the experience. My Account self-service issuance is separate from inline issuance during a protected journey. Don't assume that provider issuance destinations follow the same rules as custom credential destinations.
Keep recovery settings separate
Profile creation is separate from enabling the tenant's Account recovery policy and choosing actions after recovery. Configure those settings under Account recovery). The Account Recovery setup wizard handles profile creation, provider configuration, user group scoping,, not in the shared profiles blade. Temporary Access Pass (TAP) issuance is on by default. TAP-free registration and account validation rules.
Profile management in authentication method policy
The Verified ID authentication method policy provides visibility into profiles and user assignments.
FromFor account recovery setup, see Enable and configure account recovery. Creating a profile alone doesn't establish that the TAP-free path is supported for your users.
Test and manage the profile
Validate the profile before expanding your deployment:
- Confirm that the intended profile appears with the expected purpose and verification method.
- Test with a user in the intended scope and confirm that the expected provider handles verification.
- For recovery, test account matching and confirm that evaluation doesn't restore account access.
- Check that an out-of-scope user doesn't receive the intended recovery offer, using the eligibility guidance in the recovery user article.
Troubleshoot an unavailable identity verification profile
During onboarding, account recovery, or identity verification step-up, a user can receive the following sign-in error when no valid identity verification profile is available to them:
AADSTS10020005: No valid VidProfile data found for the tenant.
The message doesn't necessarily mean that the tenant has no profiles. Check whether a valid profile is available for the affected user and scenario:
ViewConfirm that the intended profiledetails—exists and supports the scenario and credential type. See Credential support by scenario.- Review the user's group assignments and applicable exclusions in the profile and Verified ID authentication method policy.
- Confirm that Verified ID is enabled for the intended users and review the saved profile configuration.
After correcting the configuration, provider, state,test the affected journey again with the user. The global Conditional Access exclusion doesn't supply a missing profile and priority of eachisn't a workaround for this error.
If you're an end user, contact your organization's support team with the error code, request ID, correlation ID, and timestamp from Troubleshooting details. Don't send identity documents, biometric images, or Temporary Access Pass values. Administrators can use those diagnostic details when escalating an unresolved error.
Usage scenarios
A profile supplies identity verification. Each scenario also needs its own configuration.
Account recovery
Account recovery helps users who lose all registered authentication methods regain access through identity verification. For scenario setup, see Enable and configure account recovery in Microsoft Entra ID.
Onboarding and verification for access
| Scenario | Purpose | Where to start |
|---|---|---|
| Integrated onboarding | Complete required identity verification before access and passkey bootstrap, with Lifecycle Workflows orchestration. | Onboard users with identity verification. |
| Verification for access | Require identity verification | High assurance overview. |
During preview, credential provenance is recorded only for passkey credentials. For more information, see Passkey credential provenance.
Profile properties
For Microsoft Graph API properties and values, see verifiedIdProfile resource type (beta). API property names, including the account validation claims mapping and custom authentication extension settings.
Scope user groups — Assign a group of users to a specific Verified ID profile, controlling which users can participate in the verified credential flow.
Create new assignments — Add new group-to-profile assignments for users who need access to a specific identity verification profile.
Global exclusion — Exclude specific groups from all identity verification profiles. Excluded users canstate, aren't participatethe profile creation controls described in any Verified ID-based flow, regardless of which profiles are configured.
Multiple profiles
Organizations can create multiple identity verification profiles to support different user populations. For example:
- A profile for corporate employees using one identity verification provider with exact name matching
- A profile for frontline workers using a different provider with relaxed matching
- A profile for a pilot group testing a new provider before broad deployment
When a user belongs to groups that match multiple profiles, the system evaluates profiles in priority order and applies the first matching profile.
Usage scenarios
Each identity verification profile includes one or more usage configurations that define which scenarios the profile applies to.
Account recovery
Account recovery is the primary usage scenario for Verified ID profiles today. When a user loses all registered authentication methods — such as when a device is lost, stolen, or compromised — account recovery uses the Verified ID profile to determine:
- Which identity verification provider verifies the user's identity
- How identity claims from the provider are matched against the user's Microsoft Entra ID profile
- Whether the profile operates in Evaluation mode (testing) or Production mode (full recovery)
For more information about configuring account recovery, see Enable and configure account recovery in Microsoft Entra ID.
Profile properties
The following properties define a Verified ID profile:
| Property | Description |
|---|---|
| name | Display name for the profile |
| description | Description of the profile's purpose |
| state | Whether the profile is enabled or disabled |
| priority | Processing order when multiple profiles match a user |
| verifierDid | The Decentralized Identifier (DID) representing the verifier in the credential exchange |
| faceCheckConfiguration | Settings for Entra Verified ID Face Check behavior |
| verifiedIdProfileConfiguration | The accepted issuer, claims binding, and credential type |
| verifiedIdUsageConfigurations | The scenarios the profile applies to (such as recovery) |
| lastModifiedDateTime | When the profile was last modified |
For the full API reference, see verifiedIdProfile resource type (beta).
Face Check
Face Check requires a Face Check license, available through Entra Suite or as a standalone license.
Common questions
Review profile deletion behavior and supported user-level overwrites.
How do I stop use of previously issued Verified IDs through a profile?
Delete the associated identity verification profile to stop use through that profile. Review the profile's dependencies before deleting it. Don't delete and recreate profiles merely to change navigation.
Deleting a profile doesn't mean deleting a credential from a user's wallet or revoking it with its issuer. Don't infer effects on unrelated verifiers, retained history, credential provenance, or existing sessions.
Can administrators overwrite identity verification events and credential provenance?
Administrators can overwrite identity verification events and credential provenance. These operations are separate from the user completing identity verification and from deleting a shared profile. See Manage identity verification for a user and the identity verification licensing requirements.
Related content
@@ -1,11 +1,14 @@ --- title: Verified ID identity verification overview in Microsoft Entra ID-description: Learn how Verified ID in Microsoft Entra ID uses identity verification profiles to scope users to secure identity verification flows like account recovery.+description: Learn how centralized identity verification profiles, profile purposes, and modes support onboarding, recovery, and access verification in Microsoft Entra ID. ms.reviewer: tilarso ms.service: entra-id ms.topic: concept-article ms.custom: msecd-doc-authoring-108-ms.date: 04/30/2026+ms.date: 11/03/2026+author: tilarso+ms.author: tilarso+ai-usage: ai-assisted #customer intent: As an identity administrator, I want to understand how Verified ID identity verification works in Microsoft Entra ID so that I can evaluate how identity verification profiles apply to users in my organization. @@ -15,91 +18,166 @@ ms.date: 04/30/2026 Verified ID is an identity verification capability in Microsoft Entra ID — it provides a cryptographic proof of a user's verified identity but can't be used to satisfy authentication requirements like sign-in, MFA, or SSPR. Instead, Verified ID serves as the identity proofing layer for scenarios where a user's identity must be re-established — such as account recovery when all authentication methods are lost. -Identity verification profiles are the policy layer that controls which users can participate in Verified ID flows, which provider performs verification, and how identity claims are validated. Today, Verified ID profiles are used for account recovery — enabling users who lose all authentication methods to regain access through government-issued identity verification. The profile framework is designed to support additional identity verification scenarios in the future.+Identity verification profiles control which users can participate in these flows, which verification method is used, and how identity claims are validated. Profiles support account recovery, onboarding, and verification for access.++## Prerequisites++During preview, identity verification profiles and their integrated journeys are available only in the Microsoft public cloud, not in national or sovereign clouds.++To view users' identity verification status and history, enable tenant-wide **Collect identity verification history** in the authentication methods policy under **Authentication methods** > **Verified ID** > **Configure** > **Data collection**.++:::image type="content" source="media/concept-authentication-verified-id/collect-identity-verification-history.png" alt-text="Screenshot of the Verified ID Configure tab with Collect identity verification history enabled under Data collection." lightbox="media/concept-authentication-verified-id/collect-identity-verification-history.png":::++> [!NOTE]+> Creating an identity verification profile automatically enables **Collect identity verification history** across your tenant. You don't need to enable collection separately when you create a profile.++Identity verification history collection becomes available when the setting is enabled. For the user-level views, see [Identity verification status and history](concept-authentication-methods-manage.md#identity-verification-status-and-history).++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.++Before creating a profile:++- Identify whether you need recovery, onboarding, or verification for access.+- For recovery, complete the Verified ID, Face Check, provider subscription, and account-matching preparation in [Enable and test account recovery](how-to-account-recovery-enable.md).+- Identify the users to include in your evaluation.+- Confirm that your tenant has access to shared profiles and that you have at least the [Authentication Policy Administrator](../role-based-access-control/permissions-reference.md#authentication-policy-administrator) role to manage them.+- Microsoft Entra ID P1 or an eligible higher license for identity verification profiles. Review the [identity verification licensing requirements](../../fundamentals/licensing.md#identity-verification) for your scenario.++<!-- TODO: Confirm minimum permissions to change collection settings or access reporting beyond user-level status/history, collection latency, backfill, retention, and the effect of turning collection off. Don't infer these behaviors from enabling collection. --> ## Identity verification profiles An identity verification profile is a configuration object that defines identity verification behavior for a group of users. Profiles specify: -- **Name and description** — A display name and description that identifies the profile's purpose.-- **State** — Whether the profile is enabled or disabled.+- **Name and description** — A display name and description that identify the profile.+- **Profile purpose** — The scenario the profile supports: **All**, **Verification**, **Onboarding**, or **Recovery**. See [Credential support by scenario](#credential-support-by-scenario).+- **Profile mode** — Whether the profile operates in **Evaluation** or **Production** mode. - **User group scope** — Which users the profile applies to, defined through group-based assignment.-- **Identity verification provider** — The third-party provider that performs identity proofing, identified by a verifier DID (Decentralized Identifier) — a unique cryptographic identifier for the verifier in the credential exchange.+- **Verification method** — The identity verification provider or supported tenant-issued credential used for the selected purpose. - **Face Check configuration** — Settings for Microsoft Entra Verified ID Face Check behavior during verification. - **Profile configuration** — The accepted credential issuer, how identity claims map to user properties, and the credential type for the exchange.-- **Usage configurations** — The scenarios the profile applies to, such as `recovery`. Additional scenarios may be supported in the future. - **Priority** — The processing order when a user matches multiple profiles. -### Automatic creation through account recovery+### Profile mode++Use **Profile mode** to test identity verification or make it operational for the selected **Profile purpose**.++| Mode | Behavior |+| --- | --- |+| **Evaluation** | The scenario can invoke identity verification, but verification doesn't complete the handoff to onboarding, account recovery, or resource access. |+| **Production** | Identity verification is fully operational for the selected profile purpose, enabling the handoff to the corresponding onboarding, account recovery, or resource-access journey. |++Successful verification in **Evaluation** mode doesn't mean onboarding or recovery completed or access was granted.++### Credential support by scenario++Choose the purpose before selecting a verification method: **All**, **Verification**, **Onboarding**, or **Recovery**. Use this matrix to choose a credential for your scenario. Confirm release availability in your tenant before deployment.++| Credential | All-purpose profile | Verification for access | Recovery | Onboarding |+| --- | --- | --- | --- | --- |+| Employee ID | Not supported. | Supported. | Not supported. | Not supported. |+| Custom-issued Verified ID | Not supported. | Supported. | Not supported. | Not supported. |+| Third-party Verified ID from Security Marketplace | Supported. | Supported. | Required. | Required. |++For recovery, keep the third-party provider and account-matching requirements. Don't substitute an employee credential or a custom-issued credential based only on the existence of a shared profile.++For resource-access verification, including risk-based policies, set **Profile purpose** to **All** or **Verification**. **All** supports identity verification providers only. To use tenant-issued credentials, select **Verification**. **Onboarding** and **Recovery** purposes are for their respective bootstrap journeys.++<a id="automatic-creation-through-account-recovery"></a>+<a id="profile-creation-in-microsoft-entra-verified-id"></a>+<a id="profile-management-in-authentication-method-policy"></a>+<a id="shared-identity-verification-profiles"></a>++## Create and manage identity verification profiles++Create and manage profiles in the Microsoft Entra admin center under **Verified ID** > **ID verification profiles** > **Profiles**. On **Getting started**, review the setup checklist and select **Create your first identity verification profile**. If profiles already exist, select **Profiles** > **Create profile** instead.++Enter a **Name** and **Description**, select **Profile purpose**, and choose **Profile mode**. The shared wizard also includes user groups, the verification method, account validation, optional custom claim validation, and self-service issuance settings. Review those settings before completing profile creation.++For recovery, use your subscribed identity verification provider and check the user's **First name** and **Last name** against the claims returned by that provider. Review any custom claim-validation extension with its owner before using it. -Identity verification profiles are automatically created and configured when an [Authentication Administrator](/entra/identity/role-based-access-control/permissions-reference#authentication-administrator) sets up account recovery through the Microsoft Entra admin center (**Entra ID** > **Account recovery**). The Account Recovery setup wizard handles profile creation, provider configuration, user group scoping, and account validation rules.+<a id="confirm-user-scope-and-profile-priority"></a>+<a id="multiple-profiles"></a>++### User scope and profile selection++Configure user scope in the shared-profile wizard. Use **Include** > **Select targets** > **Select groups** to start with an evaluation group. > [!IMPORTANT]-> Profiles created through account recovery don't require separate management in the authentication method policy settings. We recommend managing Verified ID assignment for recovery purposes through the Account Recovery setup wizard, which provides a guided experience for creating and configuring profiles.+> Exclusions apply globally across all identity verification profiles, not just the profile you're creating or editing. Groups excluded here are also reflected in the Verified ID authentication methods policy's **Exclude** settings. Don't use **Exclude** to remove a group from only one profile; use that profile's **Include** assignments to define its scope.++These profile exclusions are separate from the [Conditional Access onboarding and recovery exclusion](../conditional-access/policy-require-identity-verification.md#enable-the-global-onboarding-and-recovery-exclusion-preview). -### Profile management in authentication method policy+Use multiple profiles for different user populations, verification providers, or pilot groups. When a user belongs to groups that match multiple profiles, the system evaluates profiles in priority order and applies the first matching profile. -The Verified ID authentication method policy provides visibility into profiles and user assignments.+Lower priority numbers are evaluated first: priority 1 precedes priority 5. Priority numbers are unique, so ties aren't possible. -[](media/how-to-account-recovery-enable/vid-auth-method-policy.png#lightbox)+### Review self-service issuance -From the policy settings, administrators can:+Review whether to enable self-service issuance, the approved user scope, and the custom credential issuance destination before enabling the experience. My Account self-service issuance is separate from inline issuance during a protected journey. Don't assume that provider issuance destinations follow the same rules as custom credential destinations. -- **View profile details** — See the configuration, provider, state, and priority of each identity verification profile, including the account validation claims mapping and custom authentication extension settings.+### Keep recovery settings separate - [](media/how-to-account-recovery-enable/vid-profile-details.png#lightbox)+Profile creation is separate from enabling the tenant's Account recovery policy and choosing actions after recovery. Configure those settings under **Account recovery**, not in the shared profiles blade. Temporary Access Pass (TAP) issuance is on by default. TAP-free registration and stale-credential cleanup are preview choices. -- **Scope user groups** — Assign a group of users to a specific Verified ID profile, controlling which users can participate in the verified credential flow.-- **Create new assignments** — Add new group-to-profile assignments for users who need access to a specific identity verification profile.-- **Global exclusion** — Exclude specific groups from all identity verification profiles. Excluded users can't participate in any Verified ID-based flow, regardless of which profiles are configured.+For account recovery setup, see [Enable and configure account recovery](how-to-account-recovery-enable.md). Creating a profile alone doesn't establish that the TAP-free path is supported for your users. -> [!TIP]-> The authentication method policy view is useful for auditing profile assignments across the organization. For creating and configuring profiles, use the Account Recovery setup wizard.+### Test and manage the profile -### Multiple profiles+> [!NOTE]+> Changes to identity verification profiles can take 5-10 minutes to apply. After saving changes, allow time for them to take effect before testing the affected journey. -Organizations can create multiple identity verification profiles to support different user populations. For example:+Validate the profile before expanding your deployment: -- A profile for corporate employees using one identity verification provider with exact name matching-- A profile for frontline workers using a different provider with relaxed matching-- A profile for a pilot group testing a new provider before broad deployment+- Confirm that the intended profile appears with the expected purpose and verification method.+- Test with a user in the intended scope and confirm that the expected provider handles verification.+- For recovery, test account matching and confirm that evaluation doesn't restore account access.+- Check that an out-of-scope user doesn't receive the intended recovery offer, using the eligibility guidance in [the recovery user article](how-to-account-recovery-for-users.md).+- Review the Conditional Access scope for your scenario with the policy owner.+- Before enabling the profile for production users, set **Profile mode** to **Production** and test the complete journey for the selected **Profile purpose**. -When a user belongs to groups that match multiple profiles, the system evaluates profiles in priority order and applies the first matching profile.+### Troubleshoot an unavailable identity verification profile -## Usage scenarios+During onboarding, account recovery, or identity verification step-up, a user can receive the following sign-in error when no valid identity verification profile is available to them: -Each identity verification profile includes one or more usage configurations that define which scenarios the profile applies to.+`AADSTS10020005: No valid VidProfile data found for the tenant.` -### Account recovery+The message doesn't necessarily mean that the tenant has no profiles. Check whether a valid profile is available for the affected user and scenario: -Account recovery is the primary usage scenario for Verified ID profiles today. When a user loses all registered authentication methods — such as when a device is lost, stolen, or compromised — account recovery uses the Verified ID profile to determine:+- Confirm that the intended profile exists and supports the scenario and credential type. See [Credential support by scenario](#credential-support-by-scenario).+- Review the user's group assignments and applicable exclusions in the profile and Verified ID authentication method policy.+- Confirm that Verified ID is enabled for the intended users and review the saved profile configuration. -- Which identity verification provider verifies the user's identity-- How identity claims from the provider are matched against the user's Microsoft Entra ID profile-- Whether the profile operates in Evaluation mode (testing) or Production mode (full recovery)+After correcting the configuration, test the affected journey again with the user. The [global Conditional Access exclusion](../conditional-access/policy-require-identity-verification.md#enable-the-global-onboarding-and-recovery-exclusion-preview) doesn't supply a missing profile and isn't a workaround for this error.++If you're an end user, contact your organization's support team with the error code, request ID, correlation ID, and timestamp from **Troubleshooting details**. Don't send identity documents, biometric images, or Temporary Access Pass values. Administrators can use those diagnostic details when escalating an unresolved error.++## Usage scenarios++A profile supplies identity verification. Each scenario also needs its own configuration.++### Account recovery -For more information about configuring account recovery, see [Enable and configure account recovery in Microsoft Entra ID](how-to-account-recovery-enable.md).+Account recovery helps users who lose all registered authentication methods regain access through identity verification. For scenario setup, see [Enable and configure account recovery in Microsoft Entra ID](how-to-account-recovery-enable.md). > [!NOTE] > Identity verification providers are external services available through the Microsoft Security Store. Review your provider's privacy, data retention, and compliance policies before deploying a profile to production users. -## Profile properties+### Onboarding and verification for access++| Scenario | Purpose | Where to start |+| --- | --- | --- |+| Integrated onboarding | Complete required identity verification before access and passkey bootstrap, with Lifecycle Workflows orchestration. | [Onboard users with identity verification](../../id-governance/how-to-onboard-users-with-identity-verification.md). |+| Verification for access | Require identity verification after initial authentication for a protected resource or action. | [High assurance overview](../../verified-id/high-assurance.md). |++> [!IMPORTANT]+> When you use this profile for identity verification during resource access, configure the associated Conditional Access policy's **Conditions** > **Client apps** to select **Browser** and **Mobile apps and desktop clients**. The default configuration includes legacy client types that aren't supported for identity verification step-up and can cause the verification flow to fail. See [Configure a resource-access policy](../conditional-access/policy-require-identity-verification.md#configure-a-resource-access-policy). -The following properties define a Verified ID profile:+During preview, credential provenance is recorded only for passkey credentials. For more information, see [Passkey credential provenance](concept-authentication-passkeys-fido2.md#credential-provenance). -| Property | Description |-|---|---|-| **name** | Display name for the profile |-| **description** | Description of the profile's purpose |-| **state** | Whether the profile is `enabled` or `disabled` |-| **priority** | Processing order when multiple profiles match a user |-| **verifierDid** | The Decentralized Identifier (DID) representing the verifier in the credential exchange |-| **faceCheckConfiguration** | Settings for Entra Verified ID Face Check behavior |-| **verifiedIdProfileConfiguration** | The accepted issuer, claims binding, and credential type |-| **verifiedIdUsageConfigurations** | The scenarios the profile applies to (such as `recovery`) |-| **lastModifiedDateTime** | When the profile was last modified |+## Profile properties -For the full API reference, see [verifiedIdProfile resource type (beta)](/graph/api/resources/verifiedidprofile?view=graph-rest-beta&preserve-view=true).+For Microsoft Graph API properties and values, see [verifiedIdProfile resource type (beta)](/graph/api/resources/verifiedidprofile?view=graph-rest-beta&preserve-view=true). API property names, including `state`, aren't the profile creation controls described in this article. ## Face Check @@ -107,6 +185,20 @@ Verified ID profiles include Face Check configuration to verify proof of presenc Face Check requires a [Face Check license](/entra/verified-id/using-facecheck), available through Entra Suite or as a standalone license. +## Common questions++Review profile deletion behavior and supported user-level overwrites.++### How do I stop use of previously issued Verified IDs through a profile?++Delete the associated identity verification profile to stop use through that profile. Review the profile's dependencies before deleting it. Don't delete and recreate profiles merely to change navigation.++Deleting a profile doesn't mean deleting a credential from a user's wallet or revoking it with its issuer. Don't infer effects on unrelated verifiers, retained history, credential provenance, or existing sessions.++### Can administrators overwrite identity verification events and credential provenance?++Administrators can overwrite identity verification events and credential provenance. These operations are separate from the user completing identity verification and from deleting a shared profile. See [Manage identity verification for a user](concept-authentication-methods-manage.md#manage-identity-verification-for-a-user) and the [identity verification licensing requirements](../../fundamentals/licensing.md#identity-verification).+ ## Related content - [Account recovery overview](concept-account-recovery-overview.md)@@ -114,3 +206,4 @@ Face Check requires a [Face Check license](/entra/verified-id/using-facecheck), - [Frequently asked questions about account recovery](self-service-account-recovery.yml) - [What is Microsoft Entra Verified ID?](/entra/verified-id/decentralized-identifier-overview) - [verifiedIdProfile resource type (beta)](/graph/api/resources/verifiedidprofile?view=graph-rest-beta&preserve-view=true)+- [Identity verification status and history](concept-authentication-methods-manage.md#identity-verification-status-and-history). 

