> 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/recovering-user-accounts-in-microsoft-entra.md). # Recovering user accounts in Microsoft Entra Microsoft Entra Account Recovery follows a structured, multi-step process. 1Kosmos powers the identity verification step at the core of this flow. {% embed url="" %} **Step 1: Initiating account recovery in Entra** * The user loses access to their account and initiates account recovery in Microsoft Entra ID * Microsoft redirects the user to 1Kosmos **Step 2: Verifying user identity** The user completes identity proofing using: * Government-issued ID verification * Biometric liveness detection * 1:1 facial matching (selfie to ID comparison) * Deepfake and injection attack detection **Step 3: Issuing the Verified ID** * 1Kosmos issues a Microsoft Verifiable Credential * The Verifiable Credential is stored in the user's Microsoft Authenticator * No sensitive personal data is exposed **Step 4: Restoring Access** * Microsoft validates the credential * Microsoft issues the user a Temporary Access Pass * The user re-enrolls authentication methods --- # 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/recovering-user-accounts-in-microsoft-entra.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.