databricks Platform · Updated Jun 26, 2026

Customer-managed VPC will soon be required for classic workspaces

In a future release, Databricks plans to deprecate classic workspace creation with a Databricks managed VPC.

What it does

In a future release, Databricks plans to deprecate classic workspace creation with a Databricks managed VPC. New classic workspaces will require a customer managed VPC. For the simplest quick start, use a serverless workspace.

Why it matters

Compliance: Comply with specific cloud security and governance standards required by your organization.

Key capabilities

443: for Databricks infrastructure, cloud

443: for Databricks infrastructure, cloud data sources, and library repositories

3306: for the legacy Hive

3306: for the legacy Hive metastore

53: for DNS resolution when

53: for DNS resolution when you use custom DNS

6666: for secure cluster connectivity

6666: for secure cluster connectivity. This is only required if you use PrivateLink.

Architecture

Databricks Platform → Platform

In short

In a future release, Databricks plans to deprecate classic workspace creation with a Databricks managed VPC. New classic workspaces will require a customer managed VPC.

Read the full documentation ↗

Key takeaway

In a future release, Databricks plans to deprecate classic workspace creation with a Databricks managed VPC.

2026-06-26-customer-managed-vpc-will-soon-be-required-for-classic-workspaces Generated by the Databricks Updates Agent · browse all updates