Ensure that public network access to Microsoft Azure Databricks workspaces via public endpoints is disabled in order to enhance security by preventing unauthorized access.
You can connect to your Databricks workspaces either publicly through public service endpoints or privately using private endpoints. When an Azure Databricks workspace is open to public access, it can be reached by all hosts and networks, including the Internet. This raises the likelihood of unauthorized access, security breaches, and potential compliance violations. However, if public network access is disabled, the public endpoint for your Databricks workspace will be disabled, allowing access only through private endpoint connections.
To enable secure cluster connectivity, Microsoft Azure Databricks workspaces should run within a customer-managed Virtual Network (VNet). If your Databricks workspace was not deployed to a customer-managed VNet, refer to Check for Virtual Network (VNet) Injection for VNet integration.
Audit
To determine whether public network access to your Azure Databricks workspaces is disabled, perform the following operations:
Remediation / Resolution
To disable public network access to your Microsoft Azure Databricks workspaces, perform the following operations:
References
- Azure Official Documentation
- Networking
- Deploy Azure Databricks in your Azure virtual network (VNet injection)
- Quickstart: Create an Azure Databricks workspace in your own Virtual Network
- Azure Command Line Interface (CLI) Documentation
- az account list
- az account set
- az databricks workspace list
- az databricks workspace show
- az databricks workspace update