> For the complete documentation index, see [llms.txt](https://docs.slingdata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slingdata.io/connections/file-connections/azure.md).

# Azure Storage

Connect & Ingest data from / into a Azure Storage Account

## Setup

The following credentials keys are accepted:

* `account` **(required)** -> This is the Azure account string.
* `container` **(required)** -> This is the storage container.
* `conn_str` (optional) -> This is the Connection String from an [Account Access Keys](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal). Looks something like `DefaultEndpointsProtocol=https;AccountName=my_account;AccountKey=thisIsAFakeKeyxxxxxxxxxxxxx/MRHCrBw4BLmypbaJyVbvUWn4YZ1Nw==;EndpointSuffix=core.windows.net`. **Preferred when DuckDB/DuckLake reads the files** — DuckDB's azure secret accepts `CONNECTION_STRING`, not a raw account key.
* `sas_svc_url` (optional) -> This is the [Shared Access Signature (SAS)](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview) URL. For DuckDB/DuckLake reads, prefer embedding the SAS in `conn_str` (`SharedAccessSignature=…`) — DuckDB rejects a bare `SAS_TOKEN` secret parameter.
* `client_id` (optional) -> Application ID of an Azure service principal. Can also set via env var `AZURE_CLIENT_ID`
* `tenant_id` (optional) -> ID of the application's Microsoft Entra tenant. Can also set via env var `AZURE_TENANT_ID`
* `client_secret` (optional) -> A client secret generated for the App Registration. Can also set via env var `AZURE_CLIENT_SECRET`
* `client_certificate_path` (optional) -> Path to a PEM or PKCS12 certificate file including private key. Can also set via env var `AZURE_CLIENT_CERTIFICATE_PATH`
* `client_certificate_password` (optional) -> The password protecting the certificate file (PFX/PKCS12 only). Can also set via env var `AZURE_CLIENT_CERTIFICATE_PASSWORD`

### Using `sling conns`

Here are examples of setting a connection named `AZURE_STORAGE`. We must provide the `type=azure` property:

{% code overflow="wrap" %}

```bash
$ sling conns set AZURE_STORAGE type=azure account=<account> container=<container> sas_svc_url=<sas_svc_url>
$ sling conns set AZURE_STORAGE type=azure account=<account> container=<container> conn_str="<conn_str>"
```

{% endcode %}

### Environment Variable

See [here](https://docs.slingdata.io/connections/file-connections/pages/eAdVs2BHCgdr6RS8GoJC#dot-env-file-.env.sling) to learn more about the `.env.sling` file.

In JSON/YAML format:

{% code overflow="wrap" %}

```bash
export AZURE_STORAGE='{"type": "azure", "account": "<account>", "container": "<container>", "sas_svc_url": "<sas_svc_url>"}'
```

{% endcode %}

### Sling Env File YAML

See [here](https://docs.slingdata.io/connections/file-connections/pages/eAdVs2BHCgdr6RS8GoJC#sling-env-file-env.yaml) to learn more about the sling `env.yaml` file.

```yaml
connections:
  AZURE_STORAGE:
    type: azure
    account: <account>
    container: <container>
    sas_svc_url: '<sas_svc_url>'

  AZURE_STORAGE_2:
    type: azure
    account: <account>
    container: <container>
    conn_str: '<conn_str>'

  # Service principal with client secret
  AZURE_STORAGE_SP:
    type: azure
    account: <account>
    container: <container>
    client_id: your-client-id
    tenant_id: your-tenant-id
    client_secret: your-client-secret
```

If you are facing issues connecting, give [`sling assist`](/sling-cli/ai/assist.md) a try, or reach out to us at <support@slingdata.io>, on [discord](https://discord.gg/q5xtaSNDvp) or open a Github Issue [here](https://github.com/slingdata-io/sling-cli/issues).


---

# 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.slingdata.io/connections/file-connections/azure.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.