Draftt’s access is read-only. The connector only ever receives
USE CATALOG, USE SCHEMA, and SELECT — it can never write, modify, or delete data. You choose exactly which tables Draftt syncs, and your OAuth secret is encrypted at rest and never shown again after you save.What you’ll need
- Account or workspace admin — to create the service principal Draftt authenticates as.
- Metastore admin, or the owner of the target schema and tables — to grant the service principal read access to your data.
- A running SQL warehouse (serverless or pro).
- Access to the Draftt dashboard (Integrations > Azure Databricks).
Setup
Connect to your workspace
In Databricks:
- Create a Databricks-managed service principal under Settings > Identity and access > Service principals > Manage > Add service principal. See Microsoft’s guide, Add service principals to your account.
- Give it the Databricks SQL access entitlement.
- Generate an OAuth secret under Service principals > Manage > (your principal) > Secrets > Generate secret. Copy the Secret and Client ID now — the secret is shown only once.
- Grant the principal
CAN_USEon your warehouse under SQL Warehouses > (your warehouse) > Permissions.
- Enter the Workspace host (host only, no
https://, e.g.adb-1234567890.azuredatabricks.net), the Client ID, and the OAuth secret. - Click Test connection.
A personal access token (PAT) is supported as a legacy alternative, but OAuth M2M is recommended for production because it isn’t tied to an individual user’s token lifetime.
Enter the catalog and schema
Enter the catalog and schema that hold your inventory (for example
inventory and assets), then run these grants in a Databricks SQL editor so Draftt can reach them:Grant read access
Grant Draftt read access to the schema, then select the table that holds your components, devices, or servers (for example To limit access to a single table, grant
components) and validate that Draftt can read it:SELECT ON TABLE instead of ON SCHEMA.What Draftt reads
Draftt’s access is read-only (SELECT-only). It reads the table and column metadata and the rows of the inventory tables you select, and nothing outside the granted schema or tables. It cannot create, modify, or delete anything.Troubleshooting
Authentication failed: Check the client ID and OAuth secret (or PAT) and confirm the secret hasn’t expired. Cannot access the SQL warehouse: Verify the warehouse exists and the service principal hasCAN_USE on it.
Missing Unity Catalog permissions: Grant USE CATALOG, USE SCHEMA, and SELECT on the target catalog, schema, and table.
Warehouse is stopped or starting: Wait for it to start (serverless warehouses start on demand) and retry.
Could not reach the workspace: Check the workspace host value and your network connection.