Collect files from an Azure Files share into an on-premise folder
DocEvent polls a directory in your Azure Files share 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 Files Pull
To
Filerouter (on-premise)
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 Files Pull to Filerouter (on-premise) routing works
Source
Azure Files
DocEvent checks your Azure Files share on a schedule and collects new files.
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 Files Pull
Scheduled polling of an Azure Files (SMB) share 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 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 Files Pull → Filerouter (on-premise) channel.
- Pull share files down into the folder your ERP already watches
- Sync a cloud file share to the on-premise server that needs the files
- Retire scripted share downloads on office servers
- Distribute files from a central share to branch-office servers
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 Files Pull or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Azure Files
Scheduled polling of an Azure Files (SMB) share 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 your Azure Files share on a schedule and collects new files.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
Related channel integrations
Other destinations from Azure Files Pull
Other sources to Filerouter (on-premise)
- Amazon S3 → Filerouter (on-premise)
- HTTP Upload → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- SFTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- GCS Blob Pull → Filerouter (on-premise)
- Azure Blob / Datalake Pull → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)