Move files from Azure Data Lake Gen2 into SharePoint
DocEvent polls a directory in your Azure Data Lake Storage Gen2 filesystem on a schedule and delivers each collected file into a Microsoft 365 SharePoint document library. Requires a storage account with the hierarchical namespace enabled.
From
Azure Data Lake Pull
To
SharePoint
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 SharePoint 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
SharePoint
Files are delivered into a SharePoint document library.
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 SharePoint
Delivery into a Microsoft 365 SharePoint document library through the Microsoft Graph API, using a reusable Microsoft connection rather than a secret pasted onto the endpoint. Pick the site, library and destination folder, and decide what happens when the name already exists — keep both, replace it (SharePoint keeps the version history), or fail the delivery. Large files are uploaded in chunks.
Common use cases
Real workflows that teams automate with a Azure Data Lake Pull → SharePoint channel.
- Publish analytics output from ADLS Gen2 into Microsoft 365
- Give business users reports produced by a data pipeline
- Bridge a hierarchical-namespace storage account to SharePoint
- Archive Data Lake output where staff can search and version it
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 SharePoint 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:
SharePoint
Delivery into a Microsoft 365 SharePoint document library through the Microsoft Graph API, using a reusable Microsoft connection rather than a secret pasted onto the endpoint. Pick the site, library and destination folder, and decide what happens when the name already exists — keep both, replace it (SharePoint keeps the version history), or fail the delivery. Large files are uploaded in chunks.
Files are delivered into a SharePoint document library.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 sources to SharePoint
- Amazon S3 → SharePoint
- HTTP Upload → SharePoint
- Email → SharePoint
- AS2 → SharePoint
- Filerouter (on-premise) → SharePoint
- FTP Pull → SharePoint
- SFTP Pull → SharePoint
- S3 Compatible (pull) → SharePoint
- GCS Blob Pull → SharePoint
- Azure Blob Pull → SharePoint
- Azure Files Pull → SharePoint
- SharePoint → SharePoint
- DocEvent Agent (on-prem) → SharePoint