There are different things to check to resolve it: how is Databricks connecting to the storage, Is it Managed Identity & Azure Role Assignment, Access Keys, or Service Principals with secrets. It is advisable to use Managed Identity & Azure Role Assignment. If you are using Managed Identity, you can create a User-Assigned Managed Identity (UAMI) in the Azure Portal specifically for Databricks.

Assigned RBAC Roles in azure On the Storage Account, you assign the Storage Blob Data Contributor role to the Managed Identity. This gives the identity permission to read, write, and delete blobs without needing a password. Create a Databricks Access Connector in azure, then bridge the gap between Azure and Databricks.

Link the Managed Identity created to the Access Connector. This resource acts as the "handshake" that allows Databricks to use the identity. Within Databricks, register the identity as a governed object.

Create a Credential in Unity Catalog. Point the credential to the Resource ID of the Azure Access Connector. This tells Unity Catalog: "Whenever someone uses this credential, use the Managed Identity to authenticate." Then define the External Location with the specific path where the data lives and also map it to the storage credential.

I believe if all of this is done correctly, you should not have an issue.