AZURE BLOB PULL IN. FTP OUT. NO SCRIPTS.
Deliver files from Azure Blob Storage to FTP servers
DocEvent polls a folder in your Azure Blob container on a schedule, collects new files and pushes each one to your FTP server. No Event Grid, no scripts - works with both flat and Data Lake Gen2 accounts, with filename filtering and a full audit trail.
From
Azure Blob Pull
To
FTP
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 FTP 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
FTP Server
Files are pushed to any FTP server you configure.
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 FTP
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Common use cases
Real workflows that teams automate with a Azure Blob Pull → FTP channel.
- Push blob container output to trading partner FTP drop zones
- Bridge standard Azure storage to legacy FTP-only systems
- Collect partner uploads from a container prefix and republish over FTP
- Retire azcopy-and-cron scripts with a managed collection schedule
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 FTP 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:
FTP Server
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Files are pushed to any FTP server you configure.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