Azure Blob Storage
Write files to an Azure Blob Storage container in CSV or JSONL format. Use SignalSmith to export model results, audience lists, or enriched data as blobs for downstream consumption.
Prerequisites
- An Azure Storage account with a Blob container
- A storage account name and account key (or connection string)
- The container must already exist
Authentication
Azure Blob Storage uses Account Key authentication.
- In the Azure Portal, go to your storage account
- Navigate to Access keys under Security + Networking
- Copy the Storage account name and one of the Account keys
- Enter both values in SignalSmith
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Container Name | Text | Yes | The Azure Blob Storage container to write files to (e.g., my-data-container) |
| Path Prefix | Text | No | Optional prefix for all blob paths within the container. Default: signalsmith/ |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| File Format | Select | Yes | Output file format: CSV or JSONL (Newline Delimited JSON). Default: CSV |
| Enable Gzip Compression | Toggle | No | Compress files with gzip before uploading. Default: On |
Supported Operations
Sync Modes: Insert, Mirror
Audience Sync Modes: Add, Upsert, Mirror
Features
- Field Mapping: No — Azure Blob Storage writes all mapped fields as file columns
- Schema Introspection: No — Azure Blob Storage is a file-based destination without schema discovery
How It Works
SignalSmith writes data as blobs to the configured Azure container:
- Data is serialized into the selected format (CSV or JSONL)
- If gzip compression is enabled, the file is compressed before upload
- Blobs are uploaded to
https://{account}.blob.core.windows.net/{container}/{path_prefix}/{sync_id}/{filename} - Each sync run produces a new set of blobs
For Mirror mode, SignalSmith replaces the previous set of blobs with the latest complete dataset.
Troubleshooting
Authentication failed
Verify the storage account name and account key are correct. Account keys can be regenerated in the Azure Portal — if regenerated, update the key in SignalSmith.
Container not found
The container must exist before syncing. Create it in the Azure Portal under your storage account’s Containers section.
Access denied
If using Azure RBAC instead of account keys, ensure the identity has the Storage Blob Data Contributor role on the container.
Network restrictions
If the storage account has firewall rules enabled, ensure SignalSmith’s IP addresses are allowlisted, or the account allows access from all networks.