Get started
AZURE DATA LAKE PULL IN. AZURE BLOB OUT. NO SCRIPTS.

Move files from Azure Data Lake Gen2 to Azure Blob Storage

DocEvent polls a directory in your Azure Data Lake Storage Gen2 filesystem on a schedule and delivers each new file into an Azure Blob Storage container - a different account, subscription or tenant. ADLS-to-Blob transfer with completed-file detection, no scripts and a full audit trail.
From
Azure Data Lake 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 Data Lake Pull to Azure Blob routing works

Source

Azure Data Lake

DocEvent checks a folder in your Azure Data Lake Storage Gen2 filesystem on a schedule and collects new files. Requires a storage account with hierarchical namespace (HNS) enabled.
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 Data Lake Pull

Scheduled polling of an Azure Data Lake Storage Gen2 filesystem using the storage account name and access key. Requires a storage account with the hierarchical namespace (HNS) enabled; flat (non-HNS) Blob storage accounts are not supported by this source. 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 Data Lake Pull → Azure Blob channel.
  • Publish ADLS analytics output into a partner-facing Blob container
  • Copy between hierarchical and flat storage accounts on a schedule
  • Fan data engineering output into other subscriptions or tenants
  • Account-to-account movement with an audit trail, not a script
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 Data Lake Pull or Azure Blob side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Azure Data Lake
Scheduled polling of an Azure Data Lake Storage Gen2 filesystem using the storage account name and access key. Requires a storage account with the hierarchical namespace (HNS) enabled; flat (non-HNS) Blob storage accounts are not supported by this source. 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 Data Lake Storage Gen2 filesystem on a schedule and collects new files. Requires a storage account with hierarchical namespace (HNS) enabled.
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

Related channel integrations

Other destinations from Azure Data Lake Pull
Other sources to Azure Blob
View all 154 channel integrations

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

Get started for free