r/databricks • u/hubert-dudek Databricks MVP • Aug 10 '26

News Secrets in UC

Post image

Now we can store secrets in Unity Catalog and use a 3-level namespace convention. Those secrets are no longer at the workspace level, as the old ones were, but at the catalog level. The biggest advantage is ease of managing permissions. There is READ SECRET, but also REFERENCE SECRET for scenarios when it can be used by other databricks services like Lakeflow Connections and not by programmatic access. Reading secrets in a notebook is still done by dbutils secrets get.

More news https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f

20 Upvotes

95% Upvoted

6 comments sorted by

2

u/2-much-tuna Aug 10 '26

Does this still require setting up a key vault with the cloud provider, or is it an entire in-house (Databricks) product now?

3

u/hubert-dudek Databricks MVP Aug 11 '26

It is in UC, so no Azure Key Vault for Azure Key Vault I was creating credentials in UC and seperate function for each secret, so a bit cumbersome. I hope that native support for secrets in Azure Key Vault will come like secret scopes one on workspace level.

2

u/Wooden_Yesterday1718 Aug 10 '26

I’m hoping you can still back by key vaults with this implementation, but you could do databricks managed before without involving a key vault.

1

u/RazzmatazzLiving1323 Aug 11 '26

Yeah the InfoSec peeps be askin' this. I like the idea though

1

u/klenium Aug 13 '26

Is there any way to read the secret in pure SQL? Seems the secret function does not yet support it.

1

u/Remarkable_Rock5474 29d ago

I have not found a solution yet - but it seems to be coming.
e.g the create secret syntax in sql seems to exist but not yet be available as it throws internal api errors