> 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/integrations/identity-verification/microsoft-entra-vid-partner.md).
# Microsoft Entra - VID Partner
This topic explains how to configure 1Kosmos for Microsoft Entra Account Recovery using the Microsoft Security Store.
**Identity Verification by 1Kosmos** is available in the Microsoft Security Store as a pre-built integration with Microsoft Entra ID. This integration enables organizations to securely recover user accounts using biometric and document-based identity proofing.
This integration eliminates reliance on traditional self-service password reset (SSPR), which often fails in complete account lockout scenarios. Instead, it uses self-service account recovery, a phishing-resistant way for users to recover their identity securely.
You can find **Identity Verification by 1Kosmos** in the [Microsoft Security Store](https://securitystore.microsoft.com/solutions/onekosmosinc1744391571698.1kosmos_verification) or [Microsoft Marketplace](https://marketplace.microsoft.com/en-us/product/saas/onekosmosinc1744391571698.1kosmos_verification?tab=Overview).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.1kosmos.com/integrations/identity-verification/microsoft-entra-vid-partner.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
