Skip to main content
Confirm the following before you start. The infrastructure itself - VNet, AKS cluster, identities, and storage - is created in Configure registry, Kubernetes, and networking; if you already have an AKS cluster, that page has an existing-cluster checklist so you can reuse it.

​
Tools

Run the deployment from any machine with these tools and a loaded kubeconfig (a Linux/macOS workstation, a build agent, or Azure Cloud Shell):
  • Azure CLI (az), logged in with permission to create resource groups, AKS clusters, Managed Identities, and role assignments.
  • kubectl, installed and configured.
  • helm v3+.
  • jq and envsubst utilities.

​
Azure permissions

The account running the deployment needs:
  • Owner (or equivalent) on the resource group - to create the VNet, AKS cluster, Managed Identities, and storage.
  • User Access Administrator - required for the role assignments (Network Contributor, Storage Blob Data roles, AcrPull).

​
Outbound network requirements

The cluster needs outbound HTTPS (443) to: The workspace query endpoint is public by default (protected by JWT auth), so DNS points at a public load balancer IP. You can instead make it private and keep all traffic inside your VNet - see the QueryRouter step in Deploy workspace and e6data.

​
What e6data provides during onboarding

​
Values to have ready

​
Next

Continue to Configure registry, Kubernetes, and networking.
Last modified on September 29, 2026