SFTP to SharePoint Online integration

SharePoint Online does not provide a native SFTP or FTPS endpoint. SFTPPlus MFT connects those protocols to SharePoint using Microsoft Graph and Entra ID OAuth2. You install and operate SFTPPlus MFT on your own Windows or Linux system, on premises or in your cloud infrastructure.

Choose your workflow ​

Receive partner uploads into SharePoint. Partners connect to the SFTP or FTPS server hosted by SFTPPlus MFT. Their files arrive in a local staging folder, and an automated transfer forwards them to a SharePoint document library. Your partners can keep using their existing file transfer tools. A cloud application can use the same workflow to send delivery receipts to a SharePoint library.

Fetch files from an existing SFTP server. SFTPPlus MFT initiates the connection to your partner's server and transfers files to SharePoint. You do not need to provide an incoming SFTP endpoint for this workflow.

Send SharePoint files to another system. SFTPPlus MFT checks a SharePoint folder and downloads files to a local application folder or sends them to a remote SFTP or FTPS server. For example, an on-premise ERP or finance application can receive reports that branch offices publish in SharePoint. These are illustrative workflows, not customer case studies.

Authentication and setup ​

Use the dedicated SharePoint Online location for new integrations. It authenticates as an application, using a tenant ID, application ID, and client secret configured in the location's password option. Protect that secret and plan for its expiry and replacement. You do not need to disable MFA for a human user account.

Your Microsoft 365 administrator must register the application in Entra ID, grant consent for Microsoft Graph application permissions (Sites.Selected), and explicitly grant access to each required site. Consent alone does not provide site access. Follow Microsoft's selected permissions procedure for the site grant. The legacy SharePoint appinv.aspx procedure belongs to the retired ACS model and should not be used for this setup.

Create one SFTPPlus location per SharePoint site. You can reuse that location in multiple transfers to different document libraries or folders within the same site. A transfer path such as /Reports/2026 contains the document library and folder, without the site name or browser URL parameters. Paths are case sensitive. If you have an older WebDAV integration, use the OAuth2 migration guide.

Deployment and licence choices ​

SFTPPlus MFT is software that your team operates, including its host, network access, configuration, and updates. Your business applications can run on premises or with another cloud provider while SharePoint Online remains hosted by Microsoft. Here, on-premise refers to the business application or the SFTPPlus host; on-premise SharePoint Server requires a separate integration. Provide storage for incoming partner uploads and agree how long to retain staged files after delivery.

See the SharePoint licence guide for the roles used by each workflow. Ask us to confirm the licences for your deployment, including any high availability requirements. The pricing page lists software and annual support and maintenance costs. Hosting, implementation assistance, and taxes are separate considerations.

Check suitability before production ​

The connector supports SharePoint Online in Microsoft's global service. For government cloud or on-premise SharePoint Server, discuss your environment with us. The Online connector's setup does not apply directly to on-premise SharePoint Server.

Deleting a SharePoint file or folder through SFTPPlus permanently removes it, without sending it to the recycle bin. To prevent data loss, configure the transfer to archive source files after successful delivery instead of deleting them. The archive keeps a recoverable copy, serving a similar purpose to a recycle bin. Use a test library and retain source files during evaluation. Move and rename operations stay within one document library.

Uploads can be up to 250 GB per file, subject to SharePoint's limit. SFTPPlus MFT can handle source directories with more than 1,000 items. Keep monitored folders focused: filtering large directories can require additional Graph requests. See the SharePoint capability reference for details.

Try one transfer ​

Start with a small, non-sensitive test file and one transfer direction.

1. Install the current trial software on the system that will run the transfers, and record its version.
2. Ask your Microsoft 365 administrator to register the Entra application, grant consent, and grant access to your test site as described above.
3. Create a SharePoint Online location with the site URL, tenant ID, application ID, and client secret.
4. Configure one transfer between your test source and destination. Keep source deletion disabled and use a dedicated destination folder.
5. Start the transfer. Check that the destination contains the expected file and contents, and that the SFTPPlus transfer log records successful delivery.

A successful evaluation means verifying a delivered file, not just establishing a connection. Next, test your real file sizes, scheduling, existing destination files, recovery after an interrupted connection, and retention rules. If you need help, send support the product version, transfer direction, and relevant error text with secrets removed.

Common questions ​

Is this live/direct access to SharePoint through an SFTP filesystem?

No. Access is staged: SFTPPlus MFT moves files between configured locations rather than exposing SharePoint directly as an SFTP filesystem. Partner uploads are staged before forwarding, and SharePoint downloads are checked periodically or on a schedule. You can apply file filters and enforce additional permissions within SFTPPlus MFT at each stage, adding security controls over which files are transferred and who can access them.

Can files move in both directions?

Yes, configure separate transfers for each direction. Use separate source and destination folders to avoid transfer loops. This is not a promise of automatic conflict resolution when both sides edit the same file.

What happens to existing files?

Selection, overwriting, and source retention depend on your transfer configuration. Agree the intended behaviour, then test with a duplicate filename before using production documents.

Could we use Microsoft tools instead?

Power Automate and Logic Apps offer an SFTP-SSH connector for connecting to an existing SFTP server. An existing Microsoft workflow may be sufficient for a simple exchange. Compare its connector limits, run monitoring, recovery behaviour, and licensing against your workload. SFTPPlus MFT provides server and client roles on infrastructure you operate, with transfer logs and product support. A custom Graph integration gives your developers control, while leaving them responsible for authentication, retries, monitoring, and ongoing API maintenance, alongside the SFTP endpoint.