ContextQMD
Back to Cube

Dedicated Infrastructure on Azure

docs-mintlify/admin/deployment/dedicated/azure/index.mdx

1.6.501.7 KB
Original Source

On Azure, Cube offers single-tenant Dedicated Infrastructure operated by Cube, and Bring Your Own Cloud (BYOC) operated inside your own Azure subscription. Both options support private network connectivity to your data sources.

Backend connectivity (Cube → your network)

Use these options to give Cube private access to your data sources, auth providers, BI APIs targeted by Semantic Layer Sync, and anything else Cube needs to query. See Backend and frontend connectivity for the full picture.

  • Azure Private Link — connect to data sources exposed through Azure Private Link Services without routing traffic over the public internet.
  • VNet Peering — establish a VNet peering connection between the Cube VNet and your own VNet.

Frontend connectivity (your clients → Cube)

Expose Cube's APIs to your applications, browsers, BI tools, embedded analytics clients, and Semantic Layer Sync-generated configs over a private network. The pattern mirrors the AWS implementation documented in Private API Connectivity on AWS; contact us to enable the equivalent on Azure for your tenant.

Bring Your Own Cloud

If you'd like the entire Cube data plane to live inside your own Azure subscription, see Bring Your Own Cloud on Azure.