Pull files from an Azure Files share onto your own machine
DocEvent polls your Azure Files share on a schedule and the DocEvent Agent saves each collected file into a local folder on your own machine. Enrolled once, managed entirely from the web console, fully audited.
From
Azure Files Pull
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) routing works
Source
Azure Files
DocEvent checks your Azure Files share on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a Azure Files Pull → DocEvent Agent (on-prem) channel.
- Collect share drops into a local folder — no download scripts
- Land Azure Files content on the machine that processes it
- Manage the collection schedule and delivery folder from the console
- Keep an office server in sync with a share directory — no VPN
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
- Amazon S3 → DocEvent Agent (on-prem)
- HTTP Upload → DocEvent Agent (on-prem)
- Email → DocEvent Agent (on-prem)
- Filerouter (on-premise) → DocEvent Agent (on-prem)
- FTP Pull → DocEvent Agent (on-prem)
- SFTP Pull → DocEvent Agent (on-prem)
- S3 Compatible (pull) → DocEvent Agent (on-prem)
- GCS Blob Pull → DocEvent Agent (on-prem)
- Azure Blob / Datalake Pull → DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)