Unity catalog not visible

[RicardoCauduro]

I'm currently working with Databricks within Azure and encountering an issue with Unity Catalog in a newly created workspace.

My colleague initially deployed a Databricks workspace where Unity Catalog was provisioned and enabled by default. I recently created a second workspace, utilizing VNet injection, and I've noticed that Unity Catalog is not visible or available in this new workspace, unlike the first one.

What could be preventing Unity Catalog from being visible/enabled in this new VNet-injected workspace? Are there specific steps or configurations I might have missed during VNet injection that are crucial for Unity Catalog enablement? Also there´s no option to create a new catalog,

Both workspaces are in the same Azure region and are Premium tier and I'm workspace admin.

[szymon_dybczak · Accepted solution]

Hi @RicardoCauduro ,

Maybe your account admin disabled automatic assignment of newly created workspace to your unity catalog's metastore. 
Ask you account admin to check if your workspace has been assigned to metastore. If it hasn't been assigned you won't be able to see anything related to UC at your worksapce.

Your admin can assign your workspace to metastore in following way:

1. As an account admin, go to the Azure Databricks account console.

2. Click Catalog.

3. Select your metastore.

4. On the Configuration tab, under Workspace assignment select your workspace and assign it to metastore. 

[Khaja_Zaffer]

Hello like szymon suggested just try to check with the admin also as you share vnet injected workspace was it done recently if yes! Then

Might be you were missing two private endpoint of  storage account you needed to create 2 private endpoints, both configured on the same subnet with one of subresource type 'blob' and one subresource type 'dfs'.s

After this if you have any ill have with connecting to it via serverless, probably needs some NCC setup in the account console.

Good luck 

[RicardoCauduro]

Thank you for your reply. About the 2 endpoints, both were deployed. I made a test in my personal account, with the same config and the UC appears.... the issue might be related to admin privileges. I'll ask the admin account to help me and let you know soon about the results.

[szymon_dybczak]

Hi @RicardoCauduro ,

I'm quite sure it's permission related or not assigned workspace to metastore related issue. Keep us updated 😉

[RicardoCauduro]

I also think it´s permission...I made a test in my personal account, with the same config (2 workspaces, one with Vnet and another without) and the UC appears for both, but I'm the owner of the subscription. I've scheduled some time with the admin on monday, let's see if using his permission we can fix this.