> 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/using-an-existing-1kosmos-tenant.md).

# Using an existing 1Kosmos tenant

#### Getting more from your Entra integration

1Kosmos supports additional configuration options for customers using Identity Verification by 1Kosmos through Microsoft Security Store. If you want the native Microsoft Entra integration and need capabilities beyond the standard offer, a private plan may fit your needs.

#### Understanding private plans

A [Microsoft private plan](https://learn.microsoft.com/en-us/marketplace/private-plans) is a procurement method that offers more customization around function and consumption than the standard pay-as-you-go offer. It includes a tailored version of Identity Verification by 1Kosmos, configured for your organization's specific requirements and made available only to your Azure tenant.

A private plan can help if you are:

* Evaluating Identity Verification by 1Kosmos and need capabilities the standard offer does not support, such as data residency, a dedicated environment, or custom contract terms.
* An existing 1Kosmos customer who wants to bring their current environment and contract onto full Microsoft Security Store functionality.

#### Seeing what's possible

Available capabilities:

* A dedicated environment: your own isolated 1Kosmos tenant, instead of a shared one.
* Regional data hosting: keep verification data within a specific country or region.
* Admin visibility: read access to session logs for your own debugging and audit needs.
* Enhanced privacy controls: options such as dropping personal data immediately after verification.
* Expanded identity verification methods: support for electronic ID (eID) verification for international employee populations.

#### Finding the right fit

The standard offer provides Identity Verification by 1Kosmos natively in Microsoft Entra, with core functionality at a low price and minimal configuration. If you need a standard, self-service integration, this may already meet your needs.

Some enterprise customers have requirements beyond what the standard offer includes. These customers can work with 1Kosmos directly while continuing to use the native Microsoft Entra integration.

If you are already a 1Kosmos customer, you can also configure the native Microsoft Entra integration to work with your existing environment and subscription.

[Contact your 1Kosmos sales representative to discuss your requirements and determine whether a private plan is the right fit.](https://www.1kosmos.com/talk-to-sales)


---

# 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/using-an-existing-1kosmos-tenant.md?ask=<question>&goal=<user_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.
