cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Unable to create metastore in account console with my Azure Account

mdpashainfo
New Contributor II

Azure Managed Identity Credential with Access Connector Id /subscriptions/c03723bd-79a8-401a-8392-a6aef2b0d7b9/resourceGroups/RG_databricks_masterclass/providers/Microsoft.Databricks/accessConnectors/ac_meta_new and Managed Identity ID: for Account Id: 79762b8f-76c6-4f21-8046-d0563bbb172f could not be found.

Getting above error message

1 ACCEPTED SOLUTION

Accepted Solutions

NinaThoni
Databricks Employee
Databricks Employee
Thanks for sharing the full error. This message means the access connector exists in Azure, but Databricks can't match it to your Databricks account. Usually one of two things causes that:
  1. The managed identity isn't enabled on the connector. The blank "Managed Identity ID" in the error points to this. In the Azure Portal, open the connector, go to Identity, and make sure the system-assigned identity is On. If you're using a user-assigned identity, provide its resource ID when you create the credential or metastore.
  2. The connector is linked to a different Databricks account. This can happen when one Azure tenant has more than one Databricks account. Check that the account ID in the error is the one shown in the account console you're signed into. If it is, and the identity is already on, the link has to be corrected on the Databricks side. Please open a support request with the connector resource ID, your Databricks account ID, and the identity type (system-assigned or user-assigned). If you'd rather I handle it, send me those three details and I'll take care of it.
Also make sure the connector is in the same region as the storage account, and that its managed identity has the Storage Blob Data Contributor role on that storage account.
Thanks again for raising it.

Cheers,
Nina

References
Nina Thoni
Databricks Senior Solutions Engineer

View solution in original post

2 REPLIES 2

NinaThoni
Databricks Employee
Databricks Employee
Thanks for sharing the full error. This message means the access connector exists in Azure, but Databricks can't match it to your Databricks account. Usually one of two things causes that:
  1. The managed identity isn't enabled on the connector. The blank "Managed Identity ID" in the error points to this. In the Azure Portal, open the connector, go to Identity, and make sure the system-assigned identity is On. If you're using a user-assigned identity, provide its resource ID when you create the credential or metastore.
  2. The connector is linked to a different Databricks account. This can happen when one Azure tenant has more than one Databricks account. Check that the account ID in the error is the one shown in the account console you're signed into. If it is, and the identity is already on, the link has to be corrected on the Databricks side. Please open a support request with the connector resource ID, your Databricks account ID, and the identity type (system-assigned or user-assigned). If you'd rather I handle it, send me those three details and I'll take care of it.
Also make sure the connector is in the same region as the storage account, and that its managed identity has the Storage Blob Data Contributor role on that storage account.
Thanks again for raising it.

Cheers,
Nina

References
Nina Thoni
Databricks Senior Solutions Engineer

mdpashainfo
New Contributor II

mdpashainfo_0-1793645648885.png

 

 

mdpashainfo_1-1793645648888.png

 

Resourceid: /subscriptions/c03723bd-79a8-401a-8392-a6aef2b0d7b9/resourceGroups/RG_databricks_masterclass/providers/Microsoft.Databricks/accessConnectors/ac_meta_new

 

mdpashainfo_2-1793645648891.png

 

 

Databricks Accountid:

https://accounts.azuredatabricks.net/?account_id=79762b8f-76c6-4f21-8046-d0563bbb172f

 

identity type: Screenshots provided in the beginning.

 

Object (principal) ID: 61624823-9f42-41d9-95d6-ea10fa7233cd