Challenge isolating databricks workspace with single unity catalog metstore for multiple workspaces

[iskidet01]

Hello Community,

I am currently managing multiple workspaces for various projects and facing challenges in achieving data asset isolation between these workspaces. My goal is to ensure that data sharing happens exclusively through Delta Sharing.

The current limitation with Unity Catalog is that all assets in the same metastore become visible across all workspaces. While I want to maintain centralized governance with a single Unity Catalog metastore, I also need to ensure that each workspace's data assets remain isolated and accessible only to the respective workspace.

I would greatly appreciate any architectural strategies or best practices to achieve workspace-specific data isolation while leveraging same Unity Catalog.

Thank you,
iskidet

[Stefan-Koch · Accepted solution]

Hi iskidet01

You can use use workspace-catalog bindings. https://learn.microsoft.com/en-us/azure/databricks/catalogs/#workspace-catalog-binding. 

When you create a catalog, you can assign it to specific workspace, instead of "All workspaces have access"