Azure Managed Identity Credential with Access Connector Id <Resource_ID>for Account Id:<AccoutnID>could not be found

Question

Azure Managed Identity Credential with Access Connector Id <Resource_ID>for Account Id:<AccoutnID>could not be found

Bhanu S 0

I have created a databricks workspace, deployed a storage account.

I have created a access connector and provide Storage Blob Data Contributor.

While I try to create a credential in Azure Databricks, I get below error:

Azure Managed Identity Credential with Access Connector Id <Resource_ID>for Account Id:<AccoutnID>could not be found

User's image

Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator

2026-03-23T15:38:50.0066667+00:00
Hi Bhanu S

This error occurs when Unity Catalog cannot locate the specified Access Connector in the Databricks account context, even though the connector exists in Azure and has the required RBAC permissions.

To proceed, ensure the following:

The Databricks workspace is attached to the correct Databricks account where Unity Catalog is enabled.

The Access Connector is created in the same Azure tenant and subscription as the Databricks workspace.

The Access Connector has System‑Assigned Managed Identity enabled.

The managed identity of the Access Connector is granted Storage Blob Data Contributor on the target storage account.

The user creating the credential has Account Admin or Metastore Admin privileges.

The full Access Connector resource ID is used when creating the storage credential (including subscription, resource group, and resource name).

Once the Databricks account context and Access Connector configuration are aligned, the storage credential can be created successfully using Azure Managed Identity.

Hope this helps, Please let us know if you have any questions and concerns.
Bhanu S 0 Reputation points

2026-03-23T23:59:02.5266667+00:00

-> Databricks is attached to correct workspace which I have deployed

-> Only one subscription and tenant I have. Also I verified that all the resources are in same subscription and tenant

-> Access connector is having system assigned managed identity

-> The user is having metastore admin privileges as well, I have checked in accounts console.

-> I am directly copying it from access connector resource page. It has below format:

/subscriptions/########################/resourceGroups/#####################/providers/Microsoft.Databricks/accessConnectors/##################
Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator

2026-03-24T20:58:26.0233333+00:00
Hi Bhanu S,

In some cases, the Databricks UI can fail to resolve the Access Connector even when the configuration is correct, while the CLI/API path succeeds because it bypasses UI‑level validation.

When using a system‑assigned Access Connector, only the access_connector_id is required (the same value you’re already using in the UI).

High‑level steps:

Install and configure the Databricks CLI https://learn.microsoft.com/en-us/azure/databricks/dev-tools/cli/

Create the storage credential using a JSON payload that includes only the Access Connector ID

Verify the credential appears under Data → Storage Credentials in the workspace

If the credential is created successfully via CLI, it confirms the issue is UI‑side rather than a permissions or identity problem.

Hope this helps, Please let us know if you have any questions and concerns.
Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator

2026-03-25T22:16:32.5933333+00:00

Hi Bhanu S,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

1 answer

Your answer

Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator

2026-03-23T15:38:50.0066667+00:00

Hi Bhanu S

This error occurs when Unity Catalog cannot locate the specified Access Connector in the Databricks account context, even though the connector exists in Azure and has the required RBAC permissions.

To proceed, ensure the following:

The Databricks workspace is attached to the correct Databricks account where Unity Catalog is enabled.

The Access Connector is created in the same Azure tenant and subscription as the Databricks workspace.

The Access Connector has System‑Assigned Managed Identity enabled.

The managed identity of the Access Connector is granted Storage Blob Data Contributor on the target storage account.

The user creating the credential has Account Admin or Metastore Admin privileges.

The full Access Connector resource ID is used when creating the storage credential (including subscription, resource group, and resource name).

Once the Databricks account context and Access Connector configuration are aligned, the storage credential can be created successfully using Azure Managed Identity.

Hope this helps, Please let us know if you have any questions and concerns.
Bhanu S 0 Reputation points

2026-03-23T23:59:02.5266667+00:00

-> Databricks is attached to correct workspace which I have deployed

-> Only one subscription and tenant I have. Also I verified that all the resources are in same subscription and tenant

-> Access connector is having system assigned managed identity

-> The user is having metastore admin privileges as well, I have checked in accounts console.

-> I am directly copying it from access connector resource page. It has below format:

/subscriptions/########################/resourceGroups/#####################/providers/Microsoft.Databricks/accessConnectors/##################
Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator

2026-03-24T20:58:26.0233333+00:00

Hi Bhanu S,

In some cases, the Databricks UI can fail to resolve the Access Connector even when the configuration is correct, while the CLI/API path succeeds because it bypasses UI‑level validation.

When using a system‑assigned Access Connector, only the access_connector_id is required (the same value you’re already using in the UI).

High‑level steps:

Install and configure the Databricks CLI https://learn.microsoft.com/en-us/azure/databricks/dev-tools/cli/

Create the storage credential using a JSON payload that includes only the Access Connector ID

Verify the credential appears under Data → Storage Credentials in the workspace

If the credential is created successfully via CLI, it confirms the issue is UI‑side rather than a permissions or identity problem.

Hope this helps, Please let us know if you have any questions and concerns.
Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator

2026-03-25T22:16:32.5933333+00:00

Hi Bhanu S,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

This error in azure Databricks typically means the Access Connector is not correctly linked or discoverable for your Azure Storage Account at credential creation time. The most common causes are: the Access Connector is in a different region or subscription than the Databricks workspace, the managed identity is not properly assigned to the connector, or RBAC has not fully propagated. Ensure the Azure Databricks Access Connector is in the same region as the workspace, has the correct system/user-assigned identity enabled, and that identity has “Storage Blob Data Contributor” on the storage account. Also wait a few minutes after role assignment, as propagation delay often causes this exact error.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Bhanu S 0 Reputation points

2026-03-23T08:42:20.4733333+00:00

Thanks for sharing the information.

Access connector, storage account and Databricks workspace are in the same region "Central India"

And I can see the access connector for Databricks uses System Managed Identity. Role is also properly configured for the access connector to the storage account

Share via

Azure Managed Identity Credential with Access Connector Id <Resource_ID>for Account Id:<AccoutnID>could not be found

1 answer

Your answer