Collect files from Azure Blob Storage into an on-premise folder

DocEvent polls a folder in your Azure Blob container and delivers every new file into a folder on your own server via the Filerouter agent — outbound HTTPS only, no VPN, no scripts, fully audited.
From
Azure Blob Pull
To
Filerouter (on-premise)
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 Filerouter (on-premise) 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

Filerouter

Files are delivered into a local folder on your own server by the Filerouter agent.
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 Filerouter (on-premise)

The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.

Common use cases

Real workflows that teams automate with a Azure Blob Pull Filerouter (on-premise) channel.
  • Land cloud files on an on-premise server without opening firewall ports
  • Feed a legacy application that only reads a local directory
  • Mirror a blob container prefix into a datacentre folder on a schedule
  • Replace mapped drives and azcopy scripts with a managed agent
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 Filerouter (on-premise) 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:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.
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

You focus on integration,
we'll focus on delivery.

Get started for free