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.
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 direcly by Azure.
Note
In-region storage access from serverless uses service endpoints and is not charged by Databricks.
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.
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 | In progress |
| Data Transfer (/GB) | See Bandwith pricing. | Yes | In progress |
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.