> 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/run-first-query.md).

# Run first query

Confirm your Serverless e6data deployment on Azure works by running a query against your catalog.

With a catalog connected and a cluster running, run a query to confirm the deployment works end to end.

## Run a query

1. In the Compute Plane, open the **SQL Editor**.
2. Select the cluster you created and the catalog you connected.
3. Run a simple query against a table you can see:

```sql
SELECT * FROM your_catalog.your_schema.your_table LIMIT 10;
```

4. Confirm results return in the results pane.

If the query succeeds, your Azure Serverless deployment is working: the cluster reached your catalog metadata and read your ADLS Gen2 data through the Storage Credential.

## If the query fails

* An access error usually means the Managed Identity is missing the **Storage Blob Data Reader** role, or the Storage Credential isn't connected - revisit [Configure Azure access](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md).
* A connection or schema error usually points to the catalog - revisit [Connect ADLS and a catalog](/query-engine/guides/deployment/azure-serverless/connect-adls-and-catalog.md) and use **Test Connection**.
* See [Troubleshooting](/query-engine/guides/deployment/azure-serverless/troubleshooting.md) for the full list.

## Next steps

* [Query editor](/query-engine/guides/querying/query-editor.md)
* [Connect a BI tool](/query-engine/developers/bi-tool-recipes/tableau.md)
* [Create and manage clusters](/query-engine/guides/clusters/create-and-manage-clusters.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/run-first-query.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.