AZURE BLOB PULL IN. SHAREPOINT OUT. NO SCRIPTS.

Move files from Azure Blob Storage into SharePoint

DocEvent polls a folder in your standard (flat) Azure Blob container on a schedule and delivers each collected file into a Microsoft 365 SharePoint document library — both sides Microsoft, joined without a single line of code.
From
Azure Blob Pull
To
SharePoint
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
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 Blob Pull to SharePoint routing works

Source

Azure Blob

DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with both non-HNS (flat) and HNS (Data Lake Gen2) blob storage accounts - detected automatically.
DocEvent Channel
routes · retries · logs
Destination

SharePoint

Files are delivered into a SharePoint document library.
1

File arrives via Azure Blob Pull

Scheduled polling of an Azure Blob Storage container using the storage account name and access key. One source covers both account kinds: the kind is detected automatically, and on hierarchical-namespace accounts (Azure Data Lake Storage Gen2) archiving uses an atomic server-side rename. Collects from a folder (prefix) with filename pattern filtering and optional minimum-age/stable-size admission rules, then each collected file is deleted or moved to an archive prefix.
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 Blob Pull SharePoint channel.
  • Publish application output from Blob storage into Microsoft 365
  • Give business users a SharePoint view of files stored in Azure
  • Bridge a storage account to the library your team already uses
  • Archive blobs where they can be searched, versioned and shared
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 Blob Pull or SharePoint side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Azure Blob
Scheduled polling of an Azure Blob Storage container using the storage account name and access key. One source covers both account kinds: the kind is detected automatically, and on hierarchical-namespace accounts (Azure Data Lake Storage Gen2) archiving uses an atomic server-side rename. Collects from a folder (prefix) with filename pattern filtering and optional minimum-age/stable-size admission rules, then each collected file is deleted or moved to an archive prefix.
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with both non-HNS (flat) and HNS (Data Lake Gen2) blob storage accounts - detected automatically.
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

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

Get started for free