Secrets in Unity Catalog

Secrets in Unity Catalog is a Databricks data governance capability, introduced July 2026.

Secrets stored and governed as securable objects in Unity Catalog, using the three-level namespace (catalog.schema.secret) and the same privileges and auditing as any other data asset.

• Your API keys finally get the same treatment as your tables: a secret becomes a first-class Unity Catalog securable at catalog.schema.secret, so the GRANTs and audit logs you already use for data now cover credentials - no more workspace-scoped secret scopes off to the side. 🔗
• It entered Public Preview on July 10, 2026, replacing off-to-the-side workspace secret scopes with a first-class governed securable. 🔗
• The preview barely had time to be a preview - it was declared generally available on August 3, 2026, under a month after showing up in Public Preview. 🔗

⚠ Limitations: Not supported on SQL warehouses or in global/cluster init scripts; retrieval needs Databricks Runtime 17.3 LTS or above, or serverless environment version 4 or above. They don't appear in global search, BROWSE on a catalog doesn't apply, and there's no information schema yet; the API needs the unity-catalog OAuth scope. Up to 100 secrets per schema and 1,000 per metastore. 🔗

Category

Data governance

Introduced

July 2026🔗

Also known as

Unity Catalog secrets, UC secrets

Verified

2026-08-20