| Issue | Suggested action |
|---|---|
| Permission denied | Verify the Storage Blob Data Reader role is assigned at the correct scope (storage account, container, or path). |
| Managed Identity not found | Confirm you’re using the correct Client ID / Principal ID from the identity’s Overview page. |
| Access issues persist | Check the storage account firewall and private-endpoint settings; ensure e6data’s compute can reach it. |
| Federated credential issues | The service account, namespace, and issuer URL must exactly match the federated-credential configuration. |
| Storage Credential not connecting | Re-check the Tenant ID and Client ID, and leave the Client Secret empty (access is keyless). |
| Still blocked | Contact e6data support with the identity details, error logs, and storage account info. |
Troubleshooting
Resolve common Managed Identity, federated-credential, and storage-access errors in a Serverless e6data deployment on Azure.
Last modified on September 29, 2026