> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/troubleshooting.md).

# Troubleshooting

Resolve common Managed Identity, federated-credential, and storage-access errors in a Serverless e6data deployment on Azure.

| 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.                              |

## See also

* [Configure Azure access](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md)
* [FAQs](/query-engine/guides/deployment/azure-serverless/faqs.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.