> 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/configuration-reference/azure-configuration.md).

# Azure configuration

Reference for the Azure resources and configuration values used in an In-VPC e6data deployment on AKS.

This reference summarizes the Azure resources and configuration an In-VPC (CloudPrem) deployment on AKS uses. For the step-by-step build, see [Configure registry, Kubernetes, and networking](/query-engine/guides/deployment/azure-in-vpc/configure-registry-kubernetes-networking.md).

## Common variables

| Variable                     | Meaning                                         |
| ---------------------------- | ----------------------------------------------- |
| `WORKSPACE_NAME`             | The e6data workspace name                       |
| `TENANT_NAME`                | Your e6data tenant identifier (from onboarding) |
| `CLUSTER_NAME`               | The AKS cluster name                            |
| `RESOURCE_GROUP`             | Resource group containing the cluster           |
| `LOCATION`                   | Azure region                                    |
| `SUBSCRIPTION_ID`            | Azure subscription ID                           |
| `AZURE_STORAGE_ACCOUNT_NAME` | ADLS Gen2 account for workspace metadata        |

## Requirements and resources

| Area        | Configuration                                                                                                                                                                                                                                  |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AKS cluster | OIDC issuer and Workload Identity enabled (`--enable-oidc-issuer --enable-workload-identity`)                                                                                                                                                  |
| Identity    | A User-Assigned Managed Identity, federated with the workspace service accounts                                                                                                                                                                |
| Storage     | ADLS Gen2 account with **Storage Blob Data Contributor** assigned to the identity                                                                                                                                                              |
| Networking  | An Azure Load Balancer fronting the workspace endpoint - **public by default** (protected by JWT auth), or internal/private with the `azure-load-balancer-internal` annotation. The cluster identity needs **Network Contributor** on the VNet |
| Registry    | ACR pull access (a pull token, or `AcrPull` on the kubelet identity)                                                                                                                                                                           |

Outbound access on port 443 is required to `app.e6.run`, `e6labs.azurecr.io`, `mcr.microsoft.com`, `quay.io`, and the monitoring endpoint (if enabled). The public endpoint is the only inbound path; make it internal if you need all traffic to stay within the VNet.

## See also

* [Configure registry, Kubernetes, and networking](/query-engine/guides/deployment/azure-in-vpc/configure-registry-kubernetes-networking.md)
* [Kubernetes configuration](/query-engine/reference/configuration-reference/kubernetes-configuration.md)
* [Environment variables](/query-engine/reference/configuration-reference/environment-variables.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/configuration-reference/azure-configuration.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.