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

# Prerequisites

What you need before deploying a Serverless e6data workspace on Azure.

Before you begin, make sure you have:

* Access to the **Azure Portal** with permission to create Managed Identities and assign RBAC roles.
* Permission to grant access on the **Azure Storage Account** (ADLS Gen2) that e6data needs to read.
* An e6data account with permission to create a workspace.

Familiarity with the **Azure CLI** is optional - everything can be done in the Portal, but the CLI (and ARM/Terraform) are offered as alternatives for provisioning the Managed Identity.

## What happens next

Once these are in place: [create your workspace](/query-engine/guides/workspaces/create-and-manage-workspaces.md) → [configure Azure access](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md) → [connect ADLS and a catalog](/query-engine/guides/deployment/azure-serverless/connect-adls-and-catalog.md) → [create a cluster](/query-engine/guides/deployment/azure-serverless/create-cluster.md) → [run your first query](/query-engine/guides/deployment/azure-serverless/run-first-query.md).

## See also

* [Architecture](/query-engine/guides/deployment/azure-serverless/architecture.md)
* [Azure Serverless](/query-engine/guides/deployment/azure-serverless.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/prerequisites.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.