Databricks will be expanding networking billing for OpenSharing SecureConnect. Today, data providers are billed for data transfer (egress) when recipients access shared data through SecureConnect. Additional charge types and access scenarios, including charges billed to recipients, are planned.
The following table summarizes the planned charges, who is billed, and how each applies across access scenarios:
Charge type
Status
Cross-region or cross-cloud
Same-region (classic or open recipient)
Same-region (serverless recipient)
Data transfer
Available today
Bill to provider
Not applicable ¹
Not applicable ¹
Private Connectivity ²
Coming soon
Bill to provider
Bill to provider
Bill to recipient
Public Connectivity
Coming soon
Bill to recipient
Not applicable ³
Not applicable ⁴
¹ Data transfer (egress) does not apply when the recipient is in the same region as the provider.
² Applies only if the provider configures private connectivity by attaching a network connectivity configuration (NCC) to the metastore.
³ Databricks does not bill this charge. If recipients on classic compute or open recipients reach storage over the public network, their own cloud provider might bill them for network address translation (NAT) directly.
⁴ Same-region serverless recipients read from storage directly.
For rates, see Data transfer and connectivity pricing, or contact your Databricks account team.