AZURE FILES PULL IN. AZURE BLOB OUT. NO SCRIPTS.

Move files from an Azure Files share to Azure Blob Storage

DocEvent polls your Azure Files (SMB) share on a schedule and delivers each new file into an Azure Blob Storage container. The application keeps writing to the share; the files land in the container your pipelines read.
From
Azure Files Pull
To
Azure Blob
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
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 Files Pull to Azure Blob routing works

Source

Azure Files

DocEvent checks your Azure Files share on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination

Azure Blob

Files are delivered into your Azure Blob Storage container - standard and Data Lake Gen2 accounts alike.
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 Azure Blob

Delivery into an Azure Blob Storage container, authenticated with the storage account name and access key. One endpoint type covers both standard (flat-namespace) storage accounts and hierarchical-namespace accounts (Azure Data Lake Storage Gen2). Configurable folder (prefix) inside the container, and a built-in connection test that verifies the account, container and key before the first file flows.

Common use cases

Real workflows that teams automate with a Azure Files Pull Azure Blob channel.
  • Archive output from a lift-and-shift SMB application into Blob storage
  • Feed an Azure data lake from software that only writes to a file share
  • Move share drops into cheaper object storage on a schedule
  • SMB in, Blob out - no sync tooling to run
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 Azure Blob 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:
Azure Blob
Delivery into an Azure Blob Storage container, authenticated with the storage account name and access key. One endpoint type covers both standard (flat-namespace) storage accounts and hierarchical-namespace accounts (Azure Data Lake Storage Gen2). Configurable folder (prefix) inside the container, and a built-in connection test that verifies the account, container and key before the first file flows.
Files are delivered into your Azure Blob Storage container - standard and Data Lake Gen2 accounts alike.
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