Microsoft Entra Verified ID
Authentication

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 the profile'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 or disabled.Production mode.
  • User group scope — Which users the profile applies to, defined through group-based assignment.
  • Identity verification providerVerification method — The third-partyidentity verification provider that performs identity proofing, identified by a verifier DID (Decentralized Identifier) — a unique cryptographic identifieror supported tenant-issued credential used for the verifier 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 as recovery. 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.

ModeBehavior
EvaluationThe scenario can invoke identity verification, but verification doesn't complete the handoff to onboarding, account recovery

recovery, or resource access.

ProductionIdentity 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.

CredentialAll-purpose profileVerification for accessRecoveryOnboarding
Employee IDNot supported.Supported.Not supported.Not supported.
Custom-issued Verified IDNot supported.Supported.Not supported.Not supported.
Third-party Verified ID from Security MarketplaceSupported.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.

Screenshot that shows the Verified ID authentication method policy page with the Enable toggle, Include and Exclude tabs, group assignment table, and profile dropdown.stale-credential cleanup are preview choices.

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.
  • Review the Conditional Access scope for your scenario with the policy settings, administrators can:owner.
  • Before enabling the profile for production users, set Profile mode to Production and test the complete journey for the selected Profile purpose.

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 profile details —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 accessRequire identity verification profile,after initial authentication for a protected resource or action.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.

Screenshot that shows the Identity Verification Profile details panel with profile mode, profile details, user group, identity verification provider, account validation claims table, and custom authentication extension.

  • 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).this article.

    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

    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…