Destinations
Azure Blob Storage
Use an Azure storage account and container as a destination via account-key or SAS token.
Last updated 2026-05-25
On this page
ZenTransfer writes to an Azure Blob Storage container. Useful for workflows already running in Azure or where Azure compliance / data-residency is required.
What you need¶
- An Azure subscription with a storage account
- A blob container inside that storage account
- An account key, SAS token, or other credential with write access
- The storage account name and container name
Setup¶
Step 1: Create or pick a container¶
In the Azure Portal:
- Open your storage account → Containers
- Create a new container for ZenTransfer (e.g.
zentransfer) - Note the storage account name and container name
Step 2: Get a credential¶
Choose one:
- Account key — simplest, broad access; rotate periodically
- SAS token — scoped permissions and expiry; recommended for least-privilege
A working SAS for ZenTransfer needs at minimum the Write and Create blob permissions for the target container.
Step 3: Configure in ZenTransfer¶
- Log in to your Dashboard
- Under Cloud Storage, find Azure Blob
- Enter the storage account name, container name, and credential
- Save and enable the destination
Step 4: Test¶
Send a single test file and confirm it appears in the container.
Blob naming¶
The filename (after rename, if configured) becomes the blob name. There is no automatic folder structure — use rename templates with date or job variables for organisation.
Tiers and lifecycle¶
ZenTransfer writes to the storage account's default access tier (typically Hot). Use Azure lifecycle management rules to transition older blobs to Cool or Archive automatically — this is configured in Azure, not in ZenTransfer.
