> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/services-and-dependencies/azure-regions.md).

# Azure regions

Azure regions supported for e6data Serverless and In Your VPC deployments.

e6data supports the following Azure regions. Pick a region close to where your data lives to minimize cost and latency.

## Generally available

These regions support both Serverless and In Your VPC deployments:

| Region          | Display name   |
| --------------- | -------------- |
| `eastus`        | East US        |
| `eastus2`       | East US 2      |
| `westus2`       | West US 2      |
| `westus3`       | West US 3      |
| `centralus`     | Central US     |
| `westeurope`    | West Europe    |
| `northeurope`   | North Europe   |
| `uksouth`       | UK South       |
| `southeastasia` | Southeast Asia |
| `eastasia`      | East Asia      |
| `australiaeast` | Australia East |
| `centralindia`  | Central India  |

## Available on request

These regions can be enabled on request. Contact your e6data CSM:

| Region               | Display name         |
| -------------------- | -------------------- |
| `germanywestcentral` | Germany West Central |
| `francecentral`      | France Central       |
| `swedencentral`      | Sweden Central       |
| `switzerlandnorth`   | Switzerland North    |
| `uaenorth`           | UAE North            |
| `southafricanorth`   | South Africa North   |
| `koreacentral`       | Korea Central        |
| `japaneast`          | Japan East           |
| `brazilsouth`        | Brazil South         |

## Considerations when choosing a region

* **Data locality** - pick the region where your ADLS Gen2 storage lives. Cross-region access works but adds latency and egress cost.
* **Compliance** - if you have data-residency requirements (GDPR, regional compliance), pick a region in the relevant geography.
* **Cost** - Azure prices vary by region; refer to Azure's pricing page for current rates.
* **Service availability** - some Azure services (e.g., specific VM SKUs) are not in every region; confirm your required compute SKU is available before committing.

## Cross-region scenarios

| Scenario                                          | Supported?                                                         |
| ------------------------------------------------- | ------------------------------------------------------------------ |
| Workspace and storage in same region              | Yes (recommended)                                                  |
| Workspace in one region, catalogs in another      | Yes - adds latency                                                 |
| Multiple workspaces, one per region               | Yes                                                                |
| Single workspace querying across multiple regions | Yes but lower performance; consider separate workspaces per region |

## See also

* [Azure setup](/query-engine/guides/deployment/azure-serverless.md)
* [Services and dependencies](/query-engine/reference/services-and-dependencies.md)


---

# 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.e6data.com/query-engine/reference/services-and-dependencies/azure-regions.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.