New feature
GA
Network connectivity configuration
Network connectivity configuration is a Databricks compute / bi capability, introduced October 2023.
Account-level, regional object that manages serverless compute networking - the private endpoints (Private Link) and stable firewall identities serverless compute uses to reach your resources - and is attached to one or more workspaces in a region.
- Before NCCs, Azure customers allowlisted serverless SQL in their storage firewalls by copying subnet IDs straight out of the Azure Databricks documentation.
- The stable IPs were not so stable - the Public Preview's legacy list was decommissioned, and anyone still allowlisting those copied IPs can expect serverless compute to hit 403 Forbidden.
- A network object that also attaches to a data catalog - an NCC can be attached to a metastore to give OpenSharing SecureConnect private connectivity.
Limitations: An NCC is regional and attaches only to workspaces in its own region. Per account, up to 10 NCCs per region and up to 50 workspaces per NCC; private endpoints are capped per region across all NCCs (on AWS 30 for S3 and 100 for VPC resources; on Azure 100). These are fixed limits.
Open in REbricked →- Category
- Compute / BI
- Also known as
- NCC, NCCs, network connectivity configurations, serverless network connectivity, Serverless secure connectivity
- Verified
- 2026-09-27
Sources
- Official Official Databricks / Microsoft docs
- Official Microsoft Learn: Serverless compute plane networking (What is an NCC?)
- Official Databricks release notes: serverless firewall configuration via NCCs extended to jobs, notebooks, pipelines and model serving (May 31, 2024)
- Official Databricks REST API: Network Connectivity Configuration
- Official Databricks docs: What is serverless egress control? (network policies, a separate object)
- Official Databricks docs: Private network gateway, which reuses your existing NCC