Share via


Understand Databricks serverless networking costs

Data transfer and connectivity refer to moving data into and out of Databricks serverless environments. Networking charges for serverless products only apply to customers using Azure Databricks serverless compute. Customers using classic compute manage and pay networking costs directly to Azure. Serverless charges apply when serverless compute communicates with your resources and are billed directly by Azure.

Important

Starting April 7, 2026, configuring service endpoints requires Azure Network Security Perimeter. See Configure an Azure network security perimeter for Azure resources.

Note

When you add Azure resources to a Network Security Perimeter (NSP) and configure an inbound rule that allows the AzureDatabricksServerless service tag, Azure Databricks sends traffic over service endpoints. This doesn't incur charges. For the complete list of supported Azure services, see Configure an Azure network security perimeter for Azure resources. For cross-region storage access, data transfer charges still apply.

Identify billable serverless connections

Connection 3 in the diagram below shows Databricks serverless workloads, which run in the Databricks-managed cloud account and access your data or services. You are charged for the associated data transfer and connectivity costs.

Network connectivity overview diagram

To understand your usage, see Billable usage system table reference.

Types of connectivity charges

Databricks charges for the following types of connectivity:

Connection type Description Billed Timeline
Private Connectivity (/GB) See Azure Private Link pricing. Waived until further notice N/A
Private Connectivity (/hour) See Azure Private Link pricing. Yes Billing
Public Connectivity (/GB) See Azure NAT Gateway pricing. Yes Billing
Data Transfer (/GB) See Bandwith pricing. Yes Billing

For detailed pricing information, see Data transfer and connectivity.

Cost management best practices

For practical guidance on optimizing Databricks costs while maintaining performance, see Best practices for cost optimization.