Unity catalog is not automatically created when a new databricks environment is created

Question

Unity catalog is not automatically created when a new databricks environment is created

David Aston 0

When we create a new databricks instance, the unity catalog is not automatically created. This is odd, as usually it is created as part of the install. Guidance would be appreciated as to how to install the catalog against our new environment.

1 answer

Your answer

Answer 1

Vinodh247 39,201 MVP Volunteer Moderator

UC is not automatically created when a new databricks workspace is provisioned. It must be manually set up at the account level.

Steps:

In the Databricks Account Console, go to Data > Metastores > Create Metastore.

Specify name, region (must match workspace), and storage root (S3/ADLS).

Assign the metastore to your workspace.

Grant storage permissions to the workspace’s identity or IAM role

After that, UC will appear under Data Explorer in your workspace.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

David Aston 0 Reputation points

2025-10-26T11:34:28.25+00:00

This is how it used to work, but now the catalog should be automatically provisioned. This is not happening on our environment. So is a setting needed? Or a specific subscription?
David Aston 0 Reputation points

2025-10-26T11:37:23.4733333+00:00

On November 9, 2023, Databricks started to enable new workspaces for Unity Catalog automatically, with a rollout proceeding gradually. If your workspace was enabled for Unity Catalog automatically, this article does not apply to you.

Share via

Unity catalog is not automatically created when a new databricks environment is created

1 answer

Your answer