> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/other-deployment-options/docker-and-on-premise/setup/microsoft-azure-setup/database-azure-cosmosdb.md).
# Database - Azure CosmosDB
Following are steps for Azure Cosmos DB deployment for integration with DecisionRules.
After navigating to Azure Cosmos DB, hit Create. Choose **Azure DocumentDB (with MongoDB compatibility)**.
{% hint style="danger" %}
**From version 1.21.0, we recommend using the Azure DocumentDB (formerly vCore) type instead of RU-based type for new environments, following Microsoft’s own recommendation.**
{% endhint %}
DocumentDB (with MongoDB Compatibility)
## Azure DocumentDB (formerly vCore)
Assign your resource group, give the cluster a name, choose a location and choose the cluster tier and version if necessary.
Basic settings
Next go to the Networking tab and fill in the settings.
{% hint style="warning" %}
It is recommended to use a Private Endpoint connection but for hassle free non-Prod environment deployments a Public Endpoint is also an option.
{% endhint %}
Create your private endpoint, making sure it shares the same virtual network as your future server container.
Networking settings and Private Endpoint
For the Global distribution, Encryption and Tags choose whatever fits your use-case. Review the account and create.
{% hint style="danger" %}
If you use Azure DocumentDB (formerly called vCore-based Cosmos DB) you need to specify the **DB\_TYPE** environmental variable in your server container with value **COSMOSDB\_VCORE**. More information here: [Environment Variables](/doc/other-deployment-options/docker-and-on-premise/containers-environmental-variables.md)
{% endhint %}
## RU-based
Assign your resource group, give the account a name, choose a location and choose the **Serverless** capacity mode.
{% hint style="info" %}
Serverless Capacity mode has much lower operating costs compared to the Provisioned Throughput option. If for whatever reason you decide to go with the Provisioned Throughput option anyways, make sure to set the limit to a minimum of 12000 RUs.
{% endhint %}
Basic settings
Set your Global Distributions settings if needed. Next go to the Networking tab and fill in the settings.
{% hint style="warning" %}
It is recommended to use a Private Endpoint connection but for hassle free non-Prod environment deployments a Public Endpoint is also an option.
{% endhint %}
Create your private endpoint, making sure it shares the same virtual network as your future server container.
Networking settings and Private Endpoint
For the Backup Policy, Encryption and Tags choose whatever fits your use-case. Review the account and create.
#### Where to find a connection string
After the database account has been created, navigate to Settings / Connection strings. The connection string can be found under **Primary/Secondary connection string**.
{% hint style="danger" %}
If you use RU-based Cosmos DB you need to specify the **DB\_TYPE** environmental variable in your server container with value **COSMOSDB**. More information here: [Environment Variables](/doc/other-deployment-options/docker-and-on-premise/containers-environmental-variables.md)
{% endhint %}
---
# 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.decisionrules.io/doc/other-deployment-options/docker-and-on-premise/setup/microsoft-azure-setup/database-azure-cosmosdb.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.
