Deliver files from Azure Blob / Datalake to FTP servers
DocEvent polls a directory in your Azure Blob / Datalake storage (ADLS Gen2) on a schedule, collects new files and pushes each one to your FTP server. No Event Grid, no scripts — filename filtering, completed-file detection and a full audit trail.
From
Azure Blob / Datalake Pull
To
FTP
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blob / Datalakepull
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 / Datalake Pull to FTP routing works
Source
Azure Blob / Datalake
DocEvent checks a folder in your Azure Blob storage or Datalake (ADLS Gen2) on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
FTP Server
Files are pushed to any FTP server you configure.
1
File arrives via Azure Blob / Datalake Pull
Scheduled polling of an Azure Datalake Storage Gen2 filesystem — the hierarchical namespace on Azure Blob Storage — using the storage account name and access key. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
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 / Datalake Pull → FTP channel.
- Push ADLS Gen2 output to trading partner FTP drop zones
- Bridge Azure Blob / Datalake storage to legacy FTP-only systems
- Collect partner uploads from a Datalake directory 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 / Datalake Pull or FTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Azure Blob / Datalake
Scheduled polling of an Azure Datalake Storage Gen2 filesystem — the hierarchical namespace on Azure Blob Storage — using the storage account name and access key. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
DocEvent checks a folder in your Azure Blob storage or Datalake (ADLS Gen2) on a schedule and collects new files.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