Data integration

Databricks

Pull Databricks billable usage so DBUs, jobs, and SQL warehouses are visible in the same FinOps workflows as your clouds.

Available on request. We're prioritizing AWS, Azure, GCP, and Oracle Cloud billing first. Databricks usage ingestion is available for design partners on request — talk to us to prioritize your account.

Connection

Billable usage / account API (read)

Access model

Read-only

Time to value

Typically same day after API token and account linkage

How OptCloud connects with Databricks

Databricks exposes billable usage downloads and account-level APIs for DBU consumption by workspace, SKU, and job. OptCloud uses a service principal or PAT with read scope to ingest usage, then joins optional cloud infrastructure cost (the VMs under the hood) when those accounts are also connected.

Required permissions

Account admin or usage reader capable of exporting billable usage
PAT / OAuth token limited to usage and metastore metadata — not notebook contents
Optional: linked AWS/Azure/GCP account for underlying VM cost

OptCloud does not need permission to run jobs or read notebook source.

Create a connection

1
Create a usage-scoped token
In the Databricks account console, create a service principal with access to billable usage and generate a token or OAuth client.
2
Add Databricks in OptCloud
Cloud Accounts → Add → Databricks. Enter workspace/account identifiers and the token.
3
Link the cloud account paying for compute
If clusters run on your cloud subscription, ensure that AWS/Azure/GCP connector is active so DBUs and IaaS aren’t double-counted incorrectly.
4
Map workspaces to owners
Assign workspace → team mappings for chargeback.
5
Validate DBU trends
Compare OptCloud’s Databricks spend to the Databricks account console for the same period.