File inbound AS2 documents into SharePoint
Receive AS2 messages from your trading partners and file each decrypted, verified payload into a Microsoft 365 SharePoint document library. DocEvent runs the AS2 endpoint and the MDN receipts; the documents simply appear in SharePoint, versioned and searchable.
From
AS2
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 AS2 to SharePoint routing works
Source
AS2
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.
DocEvent Channel
routes · retries · logs
Destination
SharePoint
Files are delivered into a SharePoint document library.
1
File arrives via AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
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 AS2 → SharePoint channel.
- Archive partner EDI documents in a SharePoint library for compliance
- Give business users a browsable record of everything received over AS2
- Land purchase orders in the Microsoft 365 library the team already uses
- Keep an auditable AS2 archive without building storage for 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 AS2 or SharePoint side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.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
- Filerouter (on-premise) → SharePoint
- FTP Pull → SharePoint
- SFTP Pull → SharePoint
- S3 Compatible (pull) → SharePoint
- GCS Blob Pull → SharePoint
- Azure Blob Pull → SharePoint
- Azure Data Lake Pull → SharePoint
- Azure Files Pull → SharePoint
- SharePoint → SharePoint
- DocEvent Agent (on-prem) → SharePoint