- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
The "could not be found" error indicates Databricks cannot locate the Access Connector resource in Azure. This happens before any ADLS permissions are checked. Because I lack full information on your setup, you can verify the below list (if you have already confirmed some of these things, there is no need to do them again):
Azure RBAC Role: The account signed into the Databricks Account Console must have at least the Reader role assigned on the Access Connector resource itself. Assigning "Storage Blob Data Contributor" on the storage account is a separate requirement and does not grant access to the connector.
Resource ID Accuracy: In your second error message, the Resource Group is named resourcesuntitycatalog. Ensure the full Access Connector resource ID is copied exactly from the Azure portal. Any typo or case-sensitivity mismatch will cause this failure.
Entra ID Tenant Alignment: Confirm the Azure Subscription hosting the Access Connector is in the exact same Microsoft Entra ID tenant as your Databricks account. A connector in a different tenant is invisible to the account.
Identity Type Selection: The empty space in the error string and Managed Identity ID: for Account Id: confirms Databricks is attempting to resolve a system-assigned identity. Verify that the system-assigned managed identity is enabled on the Access Connector.
