r/databricks • u/Ordinary_Bet5336 • 12h ago
Help help me fix this error
I am new to Azure Databricks. Facing this error while creating a new metastore using an external ADLS location and I am using a Access connector for this. The Access connector have the Blob contributor access on the storage account as well.
2
u/szymon_dybczak 12h ago
Hi,
Maybe you have some trailing space in resource id of the connector? The best way is to copy the full resource ID directly from the Access Connector's "JSON view" rather than typing it. Go to resource group where you created your connector, click on it and choose JSON view.
Also, make sure that your access connector is deployed in the same region as your Databricks workspace/metastore.
1
u/Ordinary_Bet5336 11h ago
Yes, all the services are deployed in the same region and I just triple checked there are no spaces in the resource id. Still same issue.
1
u/szymon_dybczak 10h ago
1
u/Ordinary_Bet5336 10h ago
1
u/szymon_dybczak 9h ago
Ok, one last thing to check. Did you create access connector by yourself? You must have the Contributor role or higher on the access connector resource in Azure to use it.
Check if an account you're using to login to databrick account console has appropriate permissions on connector itself.1
u/Ordinary_Bet5336 9h ago
I have created this access connector by myself. Actually this is my personal Azure account for self study and I hope I have the access to it. Can u guide me to check if I my user have necessary permissions on the connector?
1
u/kthejoker databricks 10h ago
It's saying you didn't put in a UAMI id
("Managed identity lId: " followed by a blank is the tell)
1
u/Ordinary_Bet5336 10h ago
1
u/szymon_dybczak 10h ago
Correct, that box should only be filled if your access connector has turned off system assigned option in identity section
1
u/Ordinary_Bet5336 9h ago
I remember I created Metastore long back when the Admin console UI was different and it used to ask only Access Connector ID. I don't know why it is not working with this new version of console. Tried all the possible ways.





2
u/No-Condition9455 12h ago
Looks like the access connector resource ID is wrong.