Databricks Account Admin architecture

Mysilvercloud — Thu, 22 Aug 2024 13:35:29 GMT

Hi,

I have a couple of question regarding the Databricks Account architecture. I was given an Azure admin user to create Databricks admin account. When open the Databricks admin account console, there are some metastores already & some workspaces, which I didn't create. When we created a workspace from non-admin user, the workspace will be automatically attached to the metastore.

1. Why are workspaces automatically attached to metastore?

2. why some workspaces are shown in admin account catalog, when I didn't create them? Here is the statement from Databricks docs:

Only account admins can create new workspaces. There are a few different methods you can use to create workspaces. See Create and manage workspaces for instructions on each method. You can also use the Workspaces section of the account console to view and manage all the workspaces in your account.

3. Why can I see metastores which were not created by me?

4. which workspaces will not be shown in admin console? outside of tenant, subscriptions or resource group

5. when creating External Location, which role is needed? Admin role or regular role? We have created Contributor role as mentioned in docs but it did not work via Terraform, we have to assign the admin role to the user.

Looking forward to hearing from you. Thank you in advance.

Re: Databricks Account Admin architecture

Mysilvercloud — Thu, 22 Aug 2024 13:49:11 GMT

Also another question is, I have assigned a user to be account admin, but he can not see the previews in the account console? Why is that?

Ok now is work, I guess Databricks API is broken!

topic Databricks Account Admin architecture in Administration & Architecture

Databricks Account Admin architecture

Re: Databricks Account Admin architecture