Private network gateway
Private network gateway is a Databricks compute / bi capability, introduced August 2026.
Managed gateway that connects Databricks serverless compute to resources in your own VPC, and to whatever that VPC routes to, through one subnet, a cross-account IAM role, and your existing network connectivity configuration.
- One of its three selling points is purely bureaucratic - serverless egress leaves from a stable set of IP addresses you own, so someone else's allowlist can finally be satisfied.
- A networking feature with no network UI - during the preview the account REST API is the only way to configure one, with no console screen and no Terraform.
- The docs announce that it is free and that this is temporary in the same sentence.
Limitations: On AWS, Private Preview by request through your Databricks account team; on Azure, Beta since September 3, 2026, enabled from the account console Previews page. It supports exactly one subnet in one Availability Zone, which must be in the same region as the network connectivity configuration; you configure it only through the account REST API, with no UI and no Terraform support; it reaches resources in your VPC and transitively connected networks but not cloud-managed services behind gateway or interface endpoints such as Amazon S3; it serves serverless Databricks Runtime products; and one NCC holds at most two gateways, each with at most two DNS resolvers and 100 destinations.
Open in REbricked →- Category
- Compute / BI
- Also known as
- private network gateway, serverless private network gateway, NCC gateway
- Verified
- 2026-09-20
Sources
- Official Official Databricks / Microsoft docs
- Official Databricks release notes: Private network gateway Private Preview (August 2026)
- Official Databricks docs: Configure a private network gateway
- Official Microsoft Learn: Private network gateway
- Official Azure Databricks release notes: Private network gateway is in Beta on Azure (September 3, 2026)