> For the complete documentation index, see [llms.txt](https://docs.cow.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cow.tech/using-cow/navigation/integrations/azure-blob-csv/azure-blob-csv-permissions.md).

# Azure Blob CSV Permissions

The SAS permissions the Azure Blob CSV integration needs, and why.

The Azure Blob CSV integration reaches your CSV file through a SAS URL, so the SAS is the only access COW has. Scope it to the one file and grant only the permissions below.

| Area                | Permission | Why                                                                                         |
| ------------------- | ---------- | ------------------------------------------------------------------------------------------- |
| The CSV file (blob) | Read       | To download the file during **Test**, **Test Report** and every sync.                       |
| The CSV file (blob) | Write      | To upload the updated file when **Write Back to CSV** is on. Not needed without write-back. |

The SAS must also:

* allow HTTPS, because the URL must start with `https://`
* expire at least 12 months from the day you save the integration, because the settings screen rejects an earlier expiry

{% hint style="warning" %}
**Test** only reads the file, so it succeeds with a read-only SAS. If you turn on **Write Back to CSV**, check that the SAS includes **Write** as well.
{% endhint %}

{% hint style="info" %}
When the SAS is close to expiring, create a new one and paste the new URL into the integration's settings. Once the saved URL's expiry is less than 12 months away, the URL field shows an error and **Submit** stays disabled until you replace it.
{% endhint %}


---

# 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.cow.tech/using-cow/navigation/integrations/azure-blob-csv/azure-blob-csv-permissions.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.