Unity Catalog location with multiple workspaces and resource groups

[fred41]

We're planning on adding additional workspaces in different Azure resource groups to separate lines of business with the goal of Unity Catalog spanning these workspaces. Each Resource Group will contain a workspace and a data lake. When it comes to Unity Catalog should the metastore have it's own separate storage account? Should it be in its own resource group?

[fred41]

Just following up on this. We put the metastore in an existing storage account attached to the primary workspace. We're setup with with vnet injection so it did require allowing the primary workspace vnet permission to the others. It's been working great, no complaints about this configuration so far.

[Ismail1]

We've done similar on AWS, If this is regarding setting up backend storage for the metastore it can have a separate one (Ideally it should). Each catalog for each business unit/ workspace can have its own backend data lake too. This one would override the central one for storing managed table data. Metadata would point only to the root backend. Not sure if I answered your question. Or whether this is still an issue.