Collect files from Azure Blob Storage and deliver over SFTP
DocEvent polls your Azure Blob container on a schedule and delivers every new file to an SFTP server over SSH. Secure Azure-to-SFTP delivery from standard (flat) storage accounts, with host-key verification and a full audit trail.
From
Azure Blob Pull
To
SFTP
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How Azure Blob Pull to SFTP routing works
Source
Azure Blob
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.
DocEvent Channel
routes · retries · logs
Destination
SFTP Server
Files are pushed securely to an SFTP server over SSH.
1
File arrives via Azure Blob Pull
Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to SFTP
SSH key or password authentication. Standard port 22. Configurable remote path.
Common use cases
Real workflows that teams automate with a Azure Blob Pull → SFTP channel.
- Deliver blobs to banks or insurers that only accept SFTP
- Automate regulated submissions straight from Azure storage
- Replace scheduled azcopy scripts with managed SFTP delivery
- Move partner files from a container into an SFTP drop with host-key pinning
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Azure Blob Pull or SFTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Azure Blob
Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.Destination:
SFTP Server
SSH key or password authentication. Standard port 22. Configurable remote path.
Files are pushed securely to an SFTP server over SSH.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages