Remote onboarding with Microsoft Entra Verified ID overview
In brief
The page now compares built-in identity-verification tasks with Lifecycle Workflows and custom onboarding portals using Verified ID REST APIs, including related configuration and journey considerations.
What Entra admins need to know
Administrators and solution architects can use the updated guidance to choose an onboarding approach and plan its configuration.
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.
Onboard new remote employees usingRemote onboarding with Microsoft Entra Verified ID verificationoverview
Overview
Remote onboarding users face significant challenges onboarding remotewith Microsoft Entra Verified ID uses government-issued, ID-based attestations to help establish trust with users who aren't yet inside theyour organization's trust boundary.
Choose between two onboarding patterns. If your organization uses Lifecycle Workflows in Microsoft Entra ID Governance, use the built-in identity-verification templates and tasks. If you have your own onboarding portal or solution and need to customize the experience, integrate with the Verified ID REST APIs.
Pattern 1: Built-in identity verification tasks with Lifecycle Workflows
Use this pattern to configure onboarding through the Pre-hire and New-hire identity-verification templates and tasks in Lifecycle Workflows, rather than implement the verification journey in a custom portal.
The pattern connects pre-hire identity verification with new-hire credential registration. An ID verification profile defines the verification journey, and the workflow uses that profile for its identity-verification tasks.
For this pattern, use an identity verification (IDV) partner offer with Security Store-based integration. The IDV partner gallery lists Security Store integration partners separately from Verified ID API-based integration partners. Review the relevant integration type when selecting a provider.
For configuration and the complete user journey, see Onboard users with identity verification (Preview). That guide covers:
- Pre-hire and new-hire workflow configuration.
- Inline passkey registration and the alternative that uses a Temporary Access Pass (TAP) with Conditional Access-protected registration.
- Device, passkey-policy, and guest-account eligibility considerations.
Pattern 2: Custom onboarding portal with Verified ID REST APIs
Use this pattern if you have your own onboarding portal or solution and want to customize the experience by using Microsoft Entra Verified ID can help customers facing these scenariosREST APIs. Your application coordinates identity verification, credential presentation, user matching, and the remaining onboarding logic.
For this pattern, select a provider that supports Verified ID API-based integration from the IDV partner gallery, and follow that partner's integration guidance. Don't assume that a partner supports both integration types just because it can use government-issued, ID-based attestations asappears in the gallery.
Custom-portal example
The following employee-onboarding example assumes a way to establish trust.
When to use this pattern
You have a modern Humanhuman resources (HR) system with APIsupport.Your HR system allows programmatic integration to query the HR system to perform accuratesupport for querying records and matching userprofile matching.Your organizationprofiles. The new hire's account isin the process of adopting passwordless technologies.
Solution
A custom portal for new employee onboarding.A backend job provides new hires with a uniquely identifiable link to the employee onboarding portal from (A) that represents the new hire’s specific process. For this use case, the account for the new hire shouldalreadybeprovisioned in Microsoft EntraID. Consider using Lifecycle WorkflowsID, and the organization uses TAP as part of its passwordless onboarding.A backend job sends the
triggering point of this flow.New hires select thenew hire a link to their onboarding process. Lifecycle Workflows can trigger this invitation, but the custom portal still implements the API-based flow described here.Stage Custom-portal behavior Invitation The backend sends an employee-specific link. The new hire opens it, and the onboarding portal validates the link. Identity verification and issuance The portal redirects the new hire to the IDV partner to complete verification and receive a Verified ID in (A)their wallet.Credential presentation The new hire returns to the onboarding portal and are guided through a wizard-like experience:New hires are redirected to acquire a verified ID frompresents theidentity verification partner. To learn more about the identity verification partners: https://aka.ms/verifiedidisvNew hires presentVerified ID. The portal uses the Verified IDacquired in step 1.System receivesservice to request presentation and receive the credential claims.
Account matching The application validates the claims fromagainst theidentity verification partner, performsHR record and locates the new hire's Microsoft Entra account.TAP generation The application uses Microsoft Graph to generate a TAP, then presents it to the new hire user account lookup, and validatesto continue onboarding.The sequence diagram shows this custom-portal example, not the
information.System executes the onboarding logic to locate the Microsoft Entra account of the user, and generate a temporary access pass using MS Graph.
:::::image type="contentcomplex" source="media/remote-onboarding-new-employees-id-verification/high-level-flow-diagram.png" alt-text="Diagram showing a Sequence diagram of custom-portal identity verification, HR matching, and TAP generation in Microsoft Entra ID." lightbox="media/remote-onboarding-new-employees-id-verification/high-level flow.level-flow-diagram.png":::
The participants are the new hire (browser and Microsoft Authenticator), the IDV partner as issuer (partner portal and Verified ID service), and the organization as verifier (onboarding portal, Verified ID service, HR system, and Microsoft Entra ID).
Issues
The browser opens the invitation, and the onboarding portal validates the link before redirecting the new hire to the IDV partner. The new hire submits a selfie and documents through the browser. The partner portal creates an issuance request with an ID token hint. Microsoft Authenticator consumes the request, accepts the credential, and receives it from the Verified ID service.
The partner redirects the new hire to the onboarding portal. The new hire selects the presentation link, and the portal creates a presentation request with the Verified ID service. Microsoft Authenticator consumes the request, and the new hire consents to present the credential. The service returns the presentation response to the onboarding portal. The portal validates the user record against the credential claims through the HR system, calls Microsoft Graph to generate a TAP in Microsoft Entra ID, and presents the TAP to the new hire so onboarding can continue. :::image-end:::
Custom-portal design considerations
These considerations apply to the custom application and HR matching in Pattern 2.
TheInvitation links: Make each linkused to initiate the process needs to meet some criteria:The link should bespecific toeachone remoteemployee.The link should beemployee, valid for only a shortperiod of time.It should becomeperiod, and invalid aftera user finishes going throughtheflow.The link should be designed to correlate toflow finishes. Correlate it with a unique HR record identifier.
AAccount validation: Precreate the Microsoft Entra accountshould be precreated for every user. The account should be usedand use it as part of thesiteportal's requestvalidation process.validation.Administrators frequently deal with discrepancies between users' information held in a company's IT systems, like human resource applications or identity management solutions,Name differences: HR records and government-issued documents can contain different names, such as "Jim" and "James." Ask candidates to use theinformation the users provide. For example, an employee might have "James" asname on theirfirst name but their profile has their name as “Jim”. For those scenarios:Atgovernment-issued documents at the beginning of the HRprocess, candidates must use their name exactly as it appears in government-issued documents. Taking this approach simplifies validation logic.process to simplify validation.- Matching attributes:Design validation
logic to includearound attributesthat are morelikely tohave an exactmatchagainstthe HRsystem. Common attributesrecord exactly. In addition to first and last name, examples include street address, date of birth, nationality,national/and a national or regional identificationnumber (if applicable), in addition to first and last name.number, where applicable. AsHuman review: Plan afallback, planfallback forhuman review to work through ambiguous/non-conclusive results. This process might include temporarily storing the attributes presented in the VCambiguous or nonconclusive matches, such as a phone call with the user.
- Regional coverage:Multinational organizations
maymight needto work withdifferent identityproofingverification partnersbased on the region of the user.for different user regions. Assume thatAuditing: Treat the initial user interactionbetween the user andas untrusted. Generate detailed audit logs for requests processed by the onboardingpartner is untrusted. The onboarding portal should generate detailed logs for all requests processed that could be used for auditing purposes.portal. Don't log TAP values, invitation links, or unnecessary credential claims.
Additional resourcesRelated content
Public architecture document for generalized account onboarding:Onboard users with identity verification (Preview)- Get started with the Verified ID REST APIs
- Plan your Microsoft Entra Verified ID verification solution
@@ -1,55 +1,91 @@ ----title: Onboard new remote employees using ID verification-description: A design pattern describing how to onboard new employees remotely+title: Remote onboarding with Microsoft Entra Verified ID overview+description: Compare built-in identity verification with Lifecycle Workflows and a custom onboarding portal that uses Microsoft Entra Verified ID REST APIs.+author: rogulati+ms.author: rogulati services: decentralized-identity ms.service: entra-verified-id ms.topic: concept-article-ms.date: 12/17/2024+ms.date: 11/03/2026+ms.custom: msecd-doc-authoring-1026+ai-usage: ai-assisted+#customer intent: As an identity administrator or solution architect, I want to choose an identity verification onboarding pattern so that I can use Lifecycle Workflows or build a custom onboarding experience. --- +# Remote onboarding with Microsoft Entra Verified ID overview -# Onboard new remote employees using ID verification+<a name="overview"></a> +Remote onboarding with Microsoft Entra Verified ID uses government-issued, ID-based attestations to help establish trust with users who aren't yet inside your organization's trust boundary. -## Overview+Choose between two onboarding patterns. If your organization uses Lifecycle Workflows in Microsoft Entra ID Governance, use the built-in identity-verification templates and tasks. If you have your own onboarding portal or solution and need to customize the experience, integrate with the Verified ID REST APIs. -Enterprises onboarding users face significant challenges onboarding remote users who aren't yet inside the trust boundary. Microsoft Entra Verified ID can help customers facing these scenarios because it can use government-issued, ID-based attestations as a way to establish trust. +## Pattern 1: Built-in identity verification tasks with Lifecycle Workflows -## When to use this pattern+Use this pattern to configure onboarding through the Pre-hire and New-hire identity-verification templates and tasks in Lifecycle Workflows, rather than implement the verification journey in a custom portal. -- You have a modern Human resources (HR) system with API support. -- Your HR system allows programmatic integration to query the HR system to perform accurate user profile matching.-- Your organization is in the process of adopting passwordless technologies.+The pattern connects pre-hire identity verification with new-hire credential registration. An ID verification profile defines the verification journey, and the workflow uses that profile for its identity-verification tasks. -## Solution+For this pattern, use an identity verification (IDV) partner offer with **Security Store-based integration**. The [IDV partner gallery](https://aka.ms/verifiedidisv) lists Security Store integration partners separately from Verified ID API-based integration partners. Review the relevant integration type when selecting a provider. -1. A custom portal for new employee onboarding.+For configuration and the complete user journey, see [Onboard users with identity verification (Preview)](~/id-governance/how-to-onboard-users-with-identity-verification.md). That guide covers: -1. A backend job provides new hires with a uniquely identifiable link to the employee onboarding portal from (A) that represents the new hire’s specific process. For this use case, the account for the new hire should already be provisioned in Microsoft Entra ID. Consider using [Lifecycle Workflows](~/id-governance/what-are-lifecycle-workflows.md) as the triggering point of this flow.+- Pre-hire and new-hire workflow configuration.+- Inline passkey registration and the alternative that uses a Temporary Access Pass (TAP) with Conditional Access-protected registration.+- Device, passkey-policy, and guest-account eligibility considerations. -1. New hires select the link to the portal in (A) and are guided through a wizard-like experience:- 1. New hires are redirected to acquire a verified ID from the identity verification partner. To learn more about the identity verification partners: <https://aka.ms/verifiedidisv>- 1. New hires present the Verified ID acquired in step 1.- 1. System receives the claims from the identity verification partner, performs the new hire user account lookup, and validates the information.- 1. System executes the onboarding logic to locate the Microsoft Entra account of the user, and [generate a temporary access pass using MS Graph](/graph/api/resources/temporaryaccesspassauthenticationmethod?view=graph-rest-1.0&preserve-view=true).+<a name="when-to-use-this-pattern"></a> - :::image type="content" source="media/remote-onboarding-new-employees-id-verification/high-level-flow-diagram.png" alt-text="Diagram showing a high-level flow.":::+## Pattern 2: Custom onboarding portal with Verified ID REST APIs -## Issues and considerations+Use this pattern if you have your own onboarding portal or solution and want to customize the experience by using Microsoft Entra Verified ID REST APIs. Your application coordinates identity verification, credential presentation, user matching, and the remaining onboarding logic. -- The link used to initiate the process needs to meet some criteria:- - The link should be specific to each remote employee.- - The link should be valid for only a short period of time. - - It should become invalid after a user finishes going through the flow.- - The link should be designed to correlate to a unique HR record identifier.-- A Microsoft Entra account should be precreated for every user. The account should be used as part of the site's request validation process.-- Administrators frequently deal with discrepancies between users' information held in a company's IT systems, like human resource applications or identity management solutions, and the information the users provide. For example, an employee might have "James" as their first name but their profile has their name as “Jim”. For those scenarios:- - At the beginning of the HR process, candidates must use their name exactly as it appears in government-issued documents. Taking this approach simplifies validation logic.- - Design validation logic to include attributes that are more likely to have an exact match against the HR system. Common attributes include street address, date of birth, nationality, national/regional identification number (if applicable), in addition to first and last name.- - As a fallback, plan for human review to work through ambiguous/non-conclusive results. This process might include temporarily storing the attributes presented in the VC or a phone call with the user.-- Multinational organizations may need to work with different identity proofing partners based on the region of the user.-- Assume that the initial interaction between the user and the onboarding partner is untrusted. The onboarding portal should generate detailed logs for all requests processed that could be used for auditing purposes.+For this pattern, select a provider that supports **Verified ID API-based integration** from the [IDV partner gallery](https://aka.ms/verifiedidisv), and follow that partner's integration guidance. Don't assume that a partner supports both integration types just because it appears in the gallery. -## Additional resources+<a name="solution"></a> -- Public architecture document for generalized account onboarding: [Plan your Microsoft Entra Verified ID verification solution](plan-verification-solution.md#account-onboarding)+### Custom-portal example++The following employee-onboarding example assumes a human resources (HR) system with API support for querying records and matching user profiles. The new hire's account is already provisioned in Microsoft Entra ID, and the organization uses TAP as part of its passwordless onboarding.++A backend job sends the new hire a link to their onboarding process. [Lifecycle Workflows](~/id-governance/what-are-lifecycle-workflows.md) can trigger this invitation, but the custom portal still implements the API-based flow described here.++| Stage | Custom-portal behavior |+|-------|------------------------|+| **Invitation** | The backend sends an employee-specific link. The new hire opens it, and the onboarding portal validates the link. |+| **Identity verification and issuance** | The portal redirects the new hire to the IDV partner to complete verification and receive a Verified ID in their wallet. |+| **Credential presentation** | The new hire returns to the onboarding portal and presents the Verified ID. The portal uses the Verified ID service to request presentation and receive the credential claims. |+| **Account matching** | The application validates the claims against the HR record and locates the new hire's Microsoft Entra account. |+| **TAP generation** | The application uses Microsoft Graph to [generate a TAP](/graph/api/resources/temporaryaccesspassauthenticationmethod?view=graph-rest-1.0&preserve-view=true), then presents it to the new hire to continue onboarding. |++The sequence diagram shows this custom-portal example, not the built-in Lifecycle Workflows templates.++:::image type="complex" source="media/remote-onboarding-new-employees-id-verification/high-level-flow-diagram.png" alt-text="Sequence diagram of custom-portal identity verification, HR matching, and TAP generation in Microsoft Entra ID." lightbox="media/remote-onboarding-new-employees-id-verification/high-level-flow-diagram.png":::+The participants are the new hire (browser and Microsoft Authenticator), the IDV partner as issuer (partner portal and Verified ID service), and the organization as verifier (onboarding portal, Verified ID service, HR system, and Microsoft Entra ID).++The browser opens the invitation, and the onboarding portal validates the link before redirecting the new hire to the IDV partner. The new hire submits a selfie and documents through the browser. The partner portal creates an issuance request with an ID token hint. Microsoft Authenticator consumes the request, accepts the credential, and receives it from the Verified ID service.++The partner redirects the new hire to the onboarding portal. The new hire selects the presentation link, and the portal creates a presentation request with the Verified ID service. Microsoft Authenticator consumes the request, and the new hire consents to present the credential. The service returns the presentation response to the onboarding portal. The portal validates the user record against the credential claims through the HR system, calls Microsoft Graph to generate a TAP in Microsoft Entra ID, and presents the TAP to the new hire so onboarding can continue.+:::image-end:::++<a name="issues-and-considerations"></a>++### Custom-portal design considerations++These considerations apply to the custom application and HR matching in Pattern 2.++- **Invitation links:** Make each link specific to one remote employee, valid for only a short period, and invalid after the flow finishes. Correlate it with a unique HR record identifier.+- **Account validation:** Precreate the Microsoft Entra account and use it as part of the portal's request validation.+- **Name differences:** HR records and government-issued documents can contain different names, such as "Jim" and "James." Ask candidates to use the name on their government-issued documents at the beginning of the HR process to simplify validation.+- **Matching attributes:** Design validation around attributes likely to match the HR record exactly. In addition to first and last name, examples include street address, date of birth, nationality, and a national or regional identification number, where applicable.+- **Human review:** Plan a fallback for ambiguous or nonconclusive matches, such as a phone call with the user.+- **Regional coverage:** Multinational organizations might need different identity verification partners for different user regions.+- **Auditing:** Treat the initial user interaction as untrusted. Generate detailed audit logs for requests processed by the onboarding portal. Don't log TAP values, invitation links, or unnecessary credential claims.++<a name="additional-resources"></a>++## Related content++- [Onboard users with identity verification (Preview)](~/id-governance/how-to-onboard-users-with-identity-verification.md)+- [Get started with the Verified ID REST APIs](get-started-request-api.md)+- [Plan your Microsoft Entra Verified ID verification solution](plan-verification-solution.md#account-onboarding) 