> 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/faqs.md).

# FAQs

Common questions about data access, permissions, and revocation for a Serverless e6data deployment on Azure.

**Why does e6data need access to my Azure storage?** To read and analyze the data in your ADLS Gen2 account. e6data requires only the **Storage Blob Data Reader** role - it cannot modify or delete your data.

**Can e6data modify or delete my data?** No. The role grants read-only access. Access is also keyless - it uses Workload Identity federation, so no credentials are stored.

**Can I limit access to specific containers or paths?** Yes. Azure RBAC lets you scope the role assignment at the storage-account, container, or blob-path level.

**How do I revoke access?** Remove the **Storage Blob Data Reader** role assignment from the Managed Identity - in the Portal (Storage Account → **IAM** → Remove) or with the CLI:

```bash
az role assignment delete --role "Storage Blob Data Reader" --assignee <CLIENT_ID> --scope <STORAGE_SCOPE>
```

## See also

* [Configure Azure access](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md)
* [Troubleshooting](/query-engine/guides/deployment/azure-serverless/troubleshooting.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/faqs.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.