AZURE BLOB PULL IN. SFTP OUT. NO SCRIPTS.
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 flat or Data Lake Gen2 storage accounts, with host-key verification and a full audit trail.
From
Azure Blob Pull
To
SFTP
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
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 both non-HNS (flat) and HNS (Data Lake Gen2) blob storage accounts - detected automatically.
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 an Azure Blob Storage container using the storage account name and access key. One source covers both account kinds: the kind is detected automatically, and on hierarchical-namespace accounts (Azure Data Lake Storage Gen2) archiving uses an atomic server-side rename. Collects from a folder (prefix) with filename pattern filtering and optional minimum-age/stable-size admission rules, then each collected file is deleted or moved to an archive prefix.
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 an Azure Blob Storage container using the storage account name and access key. One source covers both account kinds: the kind is detected automatically, and on hierarchical-namespace accounts (Azure Data Lake Storage Gen2) archiving uses an atomic server-side rename. Collects from a folder (prefix) with filename pattern filtering and optional minimum-age/stable-size admission rules, then each collected file is deleted or moved to an archive prefix.
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with both non-HNS (flat) and HNS (Data Lake Gen2) blob storage accounts - detected automatically.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
Related channel integrations
Other destinations from Azure Blob Pull