Databricks workspaces should not allow public network access
This check looks at whether an Azure Databricks workspace accepts connections from the public internet. The safe setting is for public network access to be disabled, so the workspace is reached only through private connections.
Why it matters
An Azure Databricks workspace holds notebooks, jobs, cluster configuration and often credentials or links to data stores. If the workspace front end is reachable from any internet address, the only barrier between an outsider and the sign-in page is identity. A leaked password, a stolen token or a missing conditional access rule then becomes enough to reach the data platform.
Microsoft documents that Private Link can be used to limit the source of inbound requests to the Databricks control plane, and that it can also block all public internet access to a workspace. Turning public network access off means users must connect from your own network, through a private endpoint, instead of from anywhere. Microsoft Learn describes the options on its front-end network security page, including IP access lists as a weaker alternative when private connectivity is not possible.
Reducing exposure at the network layer also limits how much damage a single compromised credential can do.
How to check it yourself
Portal path: in the Azure portal open Azure Databricks, select the workspace, then Networking. On the Firewall and virtual network or Public access tab, read the value of Allow Public Network Access. Repeat for every workspace in every subscription you manage.
Read-only command (Azure CLI with the databricks extension, run on a test subscription first):
az extension add --name databricks
az databricks workspace list --query "[].{name:name, group:resourceGroup, publicAccess:publicNetworkAccess}" --output tableA workspace showing Disabled has the safe setting. Enabled means it fails the check.
How to fix it
Portal steps: open the workspace, go to Networking, set Allow Public Network Access to Disabled and save. Before you do that, make sure a private endpoint is in place so your users and automation have a way in. Microsoft's front-end documentation explains how to set up inbound Private Link for a workspace.
Script option (run it yourself with sufficient rights; ConfigCobra itself never changes your Azure environment). Replace the placeholder names:
az databricks workspace update --resource-group <resource-group> --name <workspace-name> --public-network-access DisabledIf the update is rejected, review the workspace's required network rule setting in the Microsoft documentation, because a workspace using private access has specific requirements. Afterwards, rerun the read-only list command above to confirm the value.
What changes when you fix it
Everyone who opens the workspace from outside your network is affected: data engineers, analysts and any scheduled tool that calls the workspace over the public internet will stop being able to connect. Browser sign-in from home networks, hosted CI pipelines and external BI tools are the usual casualties. Provide them with a route first, such as a VPN, ExpressRoute, a jump host or a private endpoint reachable from their network.
Jobs that run inside the workspace are not interrupted by the change itself, but anything that calls the workspace's REST API from outside your network will begin to fail. Plan the change for a quiet period, test with one pilot workspace, and keep a documented way to switch the setting back if an urgent outage occurs.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft Azure Foundations v6.0.0 | 2.1.10 | Level 1 |
More checks in Analytics Services
- Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet)CIS 2.1.1
- Ensure that Network Security Groups are Configured for Databricks SubnetsCIS 2.1.2
- Ensure that Traffic is Encrypted Between Cluster Worker NodesCIS 2.1.3
- Ensure that Users and Groups are Synced from Microsoft Entra ID to Azure DatabricksCIS 2.1.4
- Ensure that Unity Catalog is Configured for Azure DatabricksCIS 2.1.5
Check this on your Microsoft Azure
ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.