- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Thank you for verifying those details! Looking closely at your first point, I spotted the exact reason why this is failing.
You mentioned that your user has the Reader role in the Storage Account IAM. However, to create the metastore, your user account must have the Reader role on the Access Connector resource itself.
Because your user lacks permission to "see" the Access Connector in Azure, the Databricks Account Console cannot verify its existence when you click create, resulting in the "could not be found" error.
How to Fix This:
Go to the Access Connector in Azure: Open the Azure Portal and navigate to your resource group (resourcesuntitycatalog), then click on your Access Connector (AccessConnectorUnityCatalog).
Assign the Role:
Click on Access control (IAM) on the left menu.
Click Add > Add role assignment.
Select the Reader role (or Contributor).
Assign it directly to your user account (adrinilmitraazure_gmail.com#EXT#@adrinilmitraazuregmail.onmicrosoft.com).
Refresh Your Session: This is a crucial step. After assigning the role, log out of the Databricks Account Console entirely and log back in. This forces Azure to generate a new authentication token that includes your new permissions.
Once you log back in with the fresh token, try creating the metastore again. The Account Console should now be able to successfully locate the Access Connector.
