Per-role identity
Each Sembric role uses a different OAuth machine-to-machine service principal that requests only the sql scope. Secrets are runtime-only references; source metadata stores only the principal’s client ID.
Integration · Databricks SQL warehouse with Unity Catalog
Governed Databricks access for AI agents
Connect a Databricks SQL warehouse and one Unity Catalog schema with a separate OAuth service principal per Sembric role.
Identity
How Sembric connects to Databricks
Your policies stay in force
Unity Catalog grants, row filters and column masks remain authoritative. Principals receive CAN USE on the warehouse and USE CATALOG, USE SCHEMA and SELECT on chosen tables only.
Enforcement
What Sembric checks and refuses
- Only the exact workspace origin is allowed, and redirects are refused so credentials cannot be forwarded.
- Statements use named parameters and bounded INLINE results through the SQL Statement Execution API; truncated or malformed results are refused.
- Full Unity Catalog types enter the reviewed fingerprint; nested or repeated fields start sensitive when a field name looks personal and cannot be measures or dimensions.
- A workspace read is reserved before every submitted statement, including each metadata page; polling and result chunks share that reservation.
Limits
What these controls don’t do
- Cancellation after 5–25 seconds and response limits do not cap scan bytes or DBUs.
Setup
Connecting Databricks
- Create a service principal per Sembric role with the SQL entitlement, CAN USE on the warehouse, and USE CATALOG, USE SCHEMA and SELECT on only the chosen tables or curated views.
- Generate a sql-scoped OAuth secret per principal and provision it on the runtime under a role-named reference.
- Allow the exact workspace origin, then have an owner enter the warehouse ID, catalog, schema and role mappings and test each one.
- Discover, review classifications and certify with an independent reviewer.
FAQ
Databricks questions
Do Unity Catalog row filters and column masks still apply?
Yes. Each query runs as the service principal mapped to the caller’s Sembric role, so Unity Catalog decides what that principal reads.
Does Sembric cap DBU spend?
No. Sembric bounds statement count, time and response size, but not scan bytes or DBUs. Keep Databricks-side controls in place.
Other integrations
Put your first certified data product in front of an agent.
Tell us which warehouse you run and what your agents need to answer. We will help you connect a source, certify a first surface and query it over MCP.