> 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/guides/deployment/azure-in-vpc.md).

# Azure In-VPC / CloudPrem

Deploy e6data inside your own Azure VNet on AKS - the end-to-end CloudPrem deployment, from infrastructure to your first query.

An **In-VPC** (CloudPrem) deployment runs the entire e6data Compute Plane inside **your own Azure VNet** on AKS. Compute and data stay in your subscription; the e6data Control Plane handles only admin operations, workspace management, access control, and observability. The workspace query endpoint is public by default and protected by JWT auth, or can be made private to your VNet.

{% hint style="info" %}
**Who this is for:** your infrastructure / platform team - you need Azure admin access to deploy into your own VNet (creating the VNet, AKS cluster, identities, and storage). **Before you start:** the Azure CLI, `kubectl`, and Helm, and familiarity with AKS.
{% endhint %}

{% hint style="info" %}
For a fully managed alternative with no infrastructure to run, see [Azure Serverless](/query-engine/guides/deployment/azure-serverless.md).
{% endhint %}

## What you'll deploy

{% stepper %}
{% step %}

### Review the architecture

See [Architecture](/query-engine/guides/deployment/azure-in-vpc/architecture.md) - what runs in your account vs. e6data's.
{% endstep %}

{% step %}

### Check prerequisites

See [Prerequisites](/query-engine/guides/deployment/azure-in-vpc/prerequisites.md) - required tools and onboarding items.
{% endstep %}

{% step %}

### Configure registry, Kubernetes, and networking

Follow [Configure registry, Kubernetes, and networking](/query-engine/guides/deployment/azure-in-vpc/configure-registry-kubernetes-networking.md) - Azure infrastructure (VNet, AKS, identities, ADLS storage) and the base cluster components (Karpenter, cert-manager, operator, CRDs).
{% endstep %}

{% step %}

### Deploy workspace and e6data

Follow [Deploy workspace and e6data](/query-engine/guides/deployment/azure-in-vpc/deploy-workspace-and-e6data.md) - the workspace namespace, TLS, identity, and components.
{% endstep %}

{% step %}

### Register a catalog

See [Register a catalog](/query-engine/guides/deployment/azure-in-vpc/register-catalog.md) - connect your data.
{% endstep %}

{% step %}

### Create a cluster

See [Create a cluster](/query-engine/guides/deployment/azure-in-vpc/create-cluster.md) - provision compute.
{% endstep %}

{% step %}

### Run your first query

See [Run your first query](/query-engine/guides/deployment/azure-in-vpc/run-first-query.md) - validate the install.
{% endstep %}
{% endstepper %}

Ongoing operations are covered in [Component versions and operations](/query-engine/guides/deployment/azure-in-vpc/component-versions-and-operations.md), [Delete workspace](/query-engine/guides/deployment/azure-in-vpc/delete-workspace.md), and [Troubleshooting](/query-engine/guides/deployment/azure-in-vpc/troubleshooting.md).

## See also

* [Deployment models](/query-engine/get-started/deployment-models.md) - Serverless vs. In Your VPC.
* [Azure Serverless](/query-engine/guides/deployment/azure-serverless.md) - the fully managed alternative.

Once your cluster is running, [run your first query](/query-engine/guides/deployment/azure-in-vpc/run-first-query.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/guides/deployment/azure-in-vpc.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.