> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/verifiable-credentials/setting-up-microsoft-verified-id-integration.md).

# Setting Up Microsoft Verified ID Integration

<figure><img src="/files/Lyj60ntQ1sg2ocbHPeAL" alt="Adding Verifiable Credentials to Microsoft Authenticator once verified with 1Kosmos"><figcaption></figcaption></figure>

This section outlines the end-to-end process for setting up and testing a Verified ID issuance and verification flow using **Microsoft Entra Verified ID**. It covers:

* Configuring the verification journey
* Deploying a sample VerifiedID application
* Testing credential issuance
* Provisioning Verifiable Credentials (VCs) into the Microsoft Authenticator app

#### Issuance Flow Overview

The Issuance Flow of Verified ID is categorized into two phases — the **Configuration** phase and the **Issuance** phase.

* **Configuration phase** — Administrative setup activities such as configuring the 1Kosmos app within Entra, retrieving the Client ID and Client Secret, and configuring the ID proofing flow.
* **Verified ID Issuance phase** — The end user performs the identity verification process by submitting their identity documents and selfie, and scans the QR code to provision the generated Verifiable Credential (VC) into the Microsoft Authenticator app.

**Configuration phase**

To set up the Verified ID issuance process, the administrator performs the following configuration steps in Entra and 1Kosmos:

1. Configure the 1Kosmos app in the Entra portal.
2. Retrieve the Client ID and Client Secret from Entra for the 1Kosmos application.
3. Define the ID proofing flow within the 1Kosmos platform.
4. Use the 1Kosmos **Verification Flows** page in the AdminX interface to create and manage verification journeys.
5. Complete the Entra integration setup to enable secure communication between Entra and 1Kosmos.

**Verified ID Issuance phase**

To complete the Verified ID issuance, the user performs the following steps to verify identity and receive the Verifiable Credential:

1. Enter your username to initiate the proofing process.
2. Enter the one-time password (OTP) sent for authentication.
3. In the generated proofing session, submit the required identity documents.
4. Provide a selfie for verification.
5. After successful verification, 1Kosmos generates a Verifiable Credential (VC) and retrieves the credential link from Entra.
6. Scan the displayed QR code using the Microsoft Authenticator to receive the Verifiable Credential.

The Verified ID is securely stored in the user's digital wallet.

#### Step 1: Configuring the Verification Journey

Use the 1Kosmos **Verification Flows** page in the AdminX interface to create and manage verification journeys. Two types of journey are supported — select a journey and create a verification flow for users:

* **KYC with Selfie** — Users are prompted to scan an identity document and then capture a selfie for comparison.
* **Document Verification Only** — Enables standalone document verification without any selfie or liveness check.

For more information, see [Configuring Verification Flows.](/identity-verification/configurations.md)

#### Step 2: Configuring Sample VerifiedID Application Settings

This section provides the steps to deploy the sample VerifiedID application and configure it with the required permissions.

1. Reach out to your 1Kosmos representative to deploy the sample VerifiedID application.
2. Follow the [Microsoft documentation ](broken://pages/BvUtXkDnVR2PcCC5klBO)to set up an application with the appropriate permissions.
3. Provide the Client ID and Client Secret to 1Kosmos to configure the sample app.
4. Once configured, you will be able to test the generation of Entra VerifiedID.

#### Step 3: Testing Generated Entra VerifiedID

{% hint style="info" %}
**Prerequisites** — Ensure users exist in the 1Kosmos user directory with the following fields: First Name, Last Name, Phone Number, Email, and Date of Birth (optional).&#x20;
{% endhint %}

1. Navigate to the Sample App.
2. Enter your email address.
3. Choose the type of document and the device you will use for verification.
4. You will receive a link to continue the process.
5. Follow the instructions under the **Verifying Identity** section to complete document verification.
6. After successful verification, you will be presented with an option to generate a VerifiedID.

#### Step 4: Provisioning VCs into Your Microsoft Authenticator App

1. Scan the QR code using the Microsoft Authenticator app.
2. Once the scan is successful, the verified ID is added to your wallet.
3. You can now request your end user to share their Verified Credential with you by sending a Presentation Request through Microsoft Entra.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/identity-verification/verifiable-credentials/setting-up-microsoft-verified-id-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
