- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2025 10:10 AM
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.
- Labels:
-
Unity Catalog