Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Files API 3.0 requires network connectivity both from your network to Azure Databricks and from Azure Databricks to your storage.
Connectivity from your network
If you allow public internet access to your workspace but restrict it with a firewall, allowlist the control plane IP ranges for your region to use Files API 3.0:
Allowlist the IPs under Control Plane IPs, including default storage and webapp. See Inbound to Azure Databricks control plane.
If you do not allow internet access to Azure Databricks and connect through a front-end private link, create a second front-end private link for performance-intensive services to use Files API 3.0. See Configure inbound Private Link for performance-intensive services.
Connectivity to your storage
Files API 3.0 also requires network connectivity to your storage. Use the following guidance to determine which IPs or identities to allowlist in your storage firewalls.
If you allow public access to your storage but apply network restrictions, for in-region storage, add your storage accounts to an Azure network security perimeter (NSP), then allowlist the AzureDatabricksServerless service tag. The network security perimeter must stay in Transition mode. Otherwise, allowlist the Azure Databricks outbound IPs.
If you do not allow public access to your storage, configure a private link to your Azure storage. See Configure private connectivity to Azure resources.
Note
Serverless network billing applies. See Understand Databricks networking costs.