Manage private endpoint rules
Important
Starting December 4, 2024, Databricks will begin charging for networking costs on serverless workloads that connect to external resources. Billing will be implemented gradually, and you might not be charged until after December 4, 2024. You won’t be charged retroactively for usage before billing is enabled. After billing is enabled, you may be charged for:
- Private connectivity to your resources over Private Link. Data processing charges for private connectivity to your resources over Private Link are waived indefinitely. Per-hour charges will apply.
- Public connectivity to your resources over NAT gateway.
- Data transfer charges incurred, such as when serverless compute and the target resource are in different regions.
This article describes how to manage private endpoint rules for private connectivity from serverless compute using the Azure Databricks account console. You can also use the Network Connectivity Configurations API.
To configure private connectivity for serverless compute, see Configure private connectivity from serverless compute.
View the status of a private endpoint rule
After you create a private endpoint rule, you can view its status on the Network Connectivity Config page under Private endpoint rules.
PENDING
: Pending approval on the resource.ESTABLISHED
: Established on the resource.REJECTED
: Rejected on the resource.DISCONNECTED
: Disconnected on the resource.EXPIRED
: Expired on the resource. A private endpoint rule expires after being in theREJECTED
,DISCONNECTED
, orPENDING
state for 14 days.
Remove private endpoint rules
You must be an Azure Databricks account admin to remove a private endpoint.
As an account admin, go to the account console.
In the sidebar, click Cloud Resources.
Click Network Connectivity Configs.
Select your NCC.
In Private endpoint rules, click the trash icon at the right of the rule you want to remove.
If the rule is in
ESTABLISHED
,REJECTED
, orDISCONNECTED
state, Databricks might retain the private endpoint on your cloud resource for 7 days before permanently deleting it.