Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft Azure Foundations v6.0.0 · 2.1.11

Azure Databricks workspaces should be reached through private endpoints

  • Level 2
  • Analytics Services

This check looks at whether an Azure Databricks workspace has private endpoint connections so that users and clusters reach it over a private network. The safe setting is to use private endpoints instead of relying on public access.

Why it matters

A workspace reached over the public internet is open to sign-in attempts from anywhere. Private endpoints place the workspace entry point on your own virtual network, so traffic from users and from clusters stays on private addressing and public access can then be switched off.

Microsoft describes two kinds of Private Link for Databricks: front-end connections for users and back-end connections for clusters talking to the control plane. See Enable Azure Private Link back-end and front-end connections. Microsoft also notes that public access can only be blocked when both are configured.

How to check it yourself

In the Azure portal open the Azure Databricks workspace, choose Networking, and look under Private endpoint connections. An empty list means the workspace relies on public access. Also read the public network access setting on the same page.

az databricks workspace show --resource-group EXAMPLE_RG --name EXAMPLE_WORKSPACE \
  --query "{publicNetworkAccess:publicNetworkAccess, privateEndpoints:privateEndpointConnections}"

The command only reads workspace properties. Run read-only commands on a test environment or with a read-only role first.

How to fix it

Private Link needs the workspace to be deployed in your own virtual network (VNet injection). Back-end Private Link also needs secure cluster connectivity. With those in place, create a private endpoint in the portal under the workspace Networking page, or by script, and link a private DNS zone so names resolve to the private address.

az network private-endpoint create --resource-group EXAMPLE_RG \
  --name EXAMPLE-dbx-pe --vnet-name EXAMPLE_VNET --subnet EXAMPLE_PE_SUBNET \
  --private-connection-resource-id /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/EXAMPLE_RG/providers/Microsoft.Databricks/workspaces/EXAMPLE_WORKSPACE \
  --group-id databricks_ui_api --connection-name EXAMPLE-dbx-conn

Microsoft recommends a separate transit network for front-end endpoints. The commands write to your subscription, so you run them; ConfigCobra never changes your Azure.

What changes when you fix it

The affected parties are the data teams who open the workspace, the clusters that run in it, and the network team who owns the DNS and the virtual network.

  • Users must reach the workspace from a network that can resolve and route to the private endpoint, such as a VPN or a connected office network.
  • Private DNS has to be right, or the workspace name will fail to resolve for some users.
  • If you later turn public network access off, anyone outside the private path loses access, including tools that call the workspace from the internet.
  • An existing workspace may need to be redeployed if it was not created with VNet injection.

Test with a pilot workspace and a small group before you switch off public access.

Included in

BenchmarkCIS IDProfile
CIS Microsoft Azure Foundations v6.0.02.1.11Level 2

Check this on your Microsoft Azure

ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial