> For the complete documentation index, see [llms.txt](https://docs.earthscale.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthscale.ai/earthscale-documentation/access-your-own-data/azure-blob-storage.md).
# Azure Blob Storage
### Supported URL formats
Earthscale supports Azure URLs formatted like:
{% code overflow="wrap" %}
```
https://{storageaccount}.blob.core.windows.net/{path_can_contain_glob_patterns}
```
{% endcode %}
Values in curly brackets are placeholders.
You can get URLs like this from Azure Storage Explorer:
Or from the Azure Portal:
### Security
Earthscale uses OpenID Connect (OIDC) to securely access your cloud data using dedicated per-customer service accounts. This eliminates the need to share credentials while providing fine-grained access control over your cloud resources. It also lets you revoke access at any time if necessary.
### Granting Access
To grant Earthscale read-only access to an Azure Storage Container:
* Open [Earthscale](https://app.earthscale.ai/)
* Click on the user icon in the top-right corner of the left sidebar
* Click **"Cloud Access"**
* Select the **"Microsoft Azure"** tab
* Follow the instructions there, and make sure to notify us of your Azure Tenant ID so we can grant access on our side. You can send this information to [support@earthscale.ai](https://earthscale.ai/).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.earthscale.ai/earthscale-documentation/access-your-own-data/azure-blob-storage.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
