Send files from Azure Data Lake Gen2 to an AS2 partner
DocEvent polls a directory in your Azure Data Lake Storage Gen2 filesystem on a schedule and transmits each collected file to your trading partner over AS2 — signed, encrypted and MDN-tracked. Requires a storage account with the hierarchical namespace enabled.
From
Azure Data Lake Pull
To
AS2
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
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 AS2 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
AS2
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.
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 AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Common use cases
Real workflows that teams automate with a Azure Data Lake Pull → AS2 channel.
- Transmit EDI produced by an analytics pipeline in ADLS Gen2
- Give a hierarchical-namespace storage account AS2 connectivity
- Send partner documents from a Data Lake directory on a schedule
- Bridge Azure data engineering output to a trading partner
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 AS2 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:
AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.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