Azure Blob Storage
Read data files directly from Microsoft Azure Blob Storage. Files are read in place and can be joined with datasets from other connectors.
When to use
- Analytical files (Parquet, CSV, JSON) stored in an Azure Blob container.
- Cross-source analysis combining Azure-hosted files with databases or other object storage.
Before you begin
Choose one authentication method and prepare the corresponding secret with read access to the target container:
- Account key — the storage account's access key.
- SAS token — a shared access signature scoped to the container, ideally read-only and time-limited.
- Connection string — the account's full connection string.
A container-scoped, read-only SAS token is the least-privilege option.
Connection settings
| Field | Required | Description |
|---|---|---|
| Account name | Yes | The Azure Storage account name. |
| Container | Yes | The blob container that holds the files. |
| Account key | One of | The storage account access key. |
| SAS token | One of | A shared access signature, e.g. ?sv=.... |
| Connection string | One of | The full account connection string. |
Provide exactly one of the three credential fields. All secret values are stored encrypted.
Test and save
Enter the fields and use Test connection. On success, define the object path to read.
Capabilities
- Execution model: Federated. Files can be joined with datasets from other connectors.
- Access: Read-only.
- Formats: Parquet, CSV, and JSON are read directly.
Troubleshooting
- Authentication fails — verify the chosen credential; for a SAS token, confirm it has not expired and grants read/list on the container.
- Container not found — check the account name and container name.
- Access denied — the credential lacks read permission on the target blobs.