> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/data-sources/azure-blob-storage.md).

# Azure Blob Storage

Connect an Azure Blob Storage container to Felt with a connection string to map its files.

{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}

Connect an [Azure Blob Storage](https://azure.microsoft.com/en-us/products/storage/blobs) container to add its spreadsheet, vector, and raster files to maps. Felt streams Cloud Optimized GeoTIFFs (COGs) directly, without processing them. See [Supported file types](/upload-anything/files/supported-file-types.md) and [Stream large rasters](/upload-anything/stream-large-rasters.md).

## Connect Azure Blob Storage

A public container needs no credentials. For a private container, [create a shared access signature](#credentials) for Felt first. Then follow the steps in [Add a source](/upload-anything/data-sources/add-a-source.md#connect-a-source) and select **Azure Blob Storage**.

In **Connection**, fill in these fields.

| Field                   | Required               | What to enter                                                                                                                                                       |
| ----------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Blob storage endpoint   | Yes                    | The container's URL, such as `https://my-account.blob.core.windows.net/my-container/my_prefix`. With a prefix, Felt reads only the blobs whose names start with it. |
| Azure connection string | For private containers | A connection string with a shared access signature, in the form `BlobEndpoint=…;SharedAccessSignature=…`.                                                           |

Optional: In **Extract attributes**, add regular expressions that turn parts of your file paths, such as a capture date, into attributes you can filter by. See [Stream large rasters](/upload-anything/stream-large-rasters.md#organize-your-raster-data).

## Credentials

Felt reads a private container with a [connection string](https://learn.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#create-a-connection-string-using-a-shared-access-signature) that includes a [shared access signature (SAS)](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview). Create the SAS for the whole storage account or for one container, with only **Read** and **List** permissions.

Choose an expiration date when you create the SAS. When the SAS expires, the source shows **Not connected**, so create a replacement before then and update the connection string in the source's **Settings**.

### Create an account-level SAS

1. In the Azure portal, open **Storage accounts** and select the account.
2. In the sidebar, open **Security + networking** and click **Shared access signature**.
3. Allow all services and resource types, and limit the permissions to **Read** and **List**.
4. Click **Generate SAS and connection string**.
5. Copy the **Connection string**. In Felt, paste it into **Azure connection string**, with no extra spaces.

### Create a container-level SAS

1. In the Azure portal, open **Storage accounts** and select the account.
2. In the sidebar, click **Storage browser**, then **Blob containers**.
3. Click the **···** menu on the container and click **Generate SAS**.
4. Limit the permissions to **Read** and **List**, then click **Generate SAS token and URL**.
5. Copy the **Blob SAS token**. In Felt, enter it in **Azure connection string** in this form, with your account name and no extra spaces:

   ```
   BlobEndpoint=https://my-account.blob.core.windows.net/;SharedAccessSignature=YOUR_SAS_TOKEN
   ```


---

# 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://help.felt.com/upload-anything/data-sources/azure-blob-storage.md?ask=<question>&goal=<user_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.