Get started
SFTP / FTPS SERVER IN. SHAREPOINT OUT. NO SCRIPTS.

Upload over SFTP, land the file in a SharePoint document library

DocEvent hosts an SFTP, SCP and FTPS server that senders upload to, and delivers each completed upload into a Microsoft 365 SharePoint document library. SFTP-to-SharePoint with a reusable Microsoft Graph connection, retries and a full audit trail.
From
SFTP / FTPS Server
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 SFTP / FTPS Server to SharePoint routing works

Source

SFTP / FTPS Server

DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
DocEvent Channel
routes · retries · logs
Destination

SharePoint

Files are delivered into a SharePoint document library.
1

File arrives via SFTP / FTPS Server

A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
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 SFTP / FTPS Server → SharePoint channel.
  • Give an SFTP-only system or partner a path into Microsoft 365
  • Replace manual downloads and re-uploads into SharePoint
  • Connect your Microsoft account once and reuse it across endpoints
  • Per-sender logins on the upload, every file audited end to end
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP / FTPS Server or SharePoint side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
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 destinations from SFTP / FTPS Server
Other sources to SharePoint
View all 154 channel integrations

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

Get started for free