Compare · Experience Cloud

SharePoint connectors for Experience Cloud, compared

Five apps that let Experience Cloud users work with files in SharePoint, compared on how a portal user reaches SharePoint, what they can do and what you install. Facts only, from each vendor's own pages.

The short answer

It comes down to how portal users reach SharePoint

All five keep portal files in SharePoint. They differ on whether a portal user needs a Microsoft account, who decides what that user can do, and whether a file passes through Salesforce first. Each row below is a need and the app built around it.

Portal users should need no Microsoft account, with each user's actions set in Salesforce

CloudFiles

Portal users reach SharePoint through CloudFiles' own connection; a permission set and the widget settings decide what each one can do.

Portal users already have Microsoft 365 accounts and should act as themselves in SharePoint

sFiles

sFiles' full Experience Cloud feature set runs on each portal user's own Microsoft 365 login.

You already run Share Connect and want Flow to route every upload

Experience Connect

An extension package for Share Connect; a Salesforce Flow picks the folder each upload lands in.

Portal users only upload and download, inside their own folder

24Files

Anonymous access through a shared service account, limited to each user's own folder.

Uploads should land in Salesforce first and move to storage on their own

XfilesPro

XfilesPro offloads each portal upload to external storage and keeps the file link in Salesforce.

Facts

Five apps, side by side

Stated as facts and not scored, from each vendor's own pages, with the same rows for every app. Experience Connect is Appiphony's extension package for Share Connect.

TopicCloudFilesby CloudFilessFilesby Upsource SolutionsExperience Connectby Appiphony, with Share Connect24Filesby 24FlowXfilesProby XfilesPro Labs
How portal users reach SharePointCloudFiles' own connection: an integration user or a service principalUsually one shared SharePoint account; each user's own Microsoft 365 login is optionalShare Connect routes each upload to SharePointA shared service account (anonymous access), or each user's own loginThe upload lands in Salesforce, then moves to storage
Microsoft account for each portal userNot neededNot needed for the Uploader and List View; needed for the full feature setNot stated for SharePointNot needed with anonymous accessNot stated
What portal users can doUp to seven actions per user (download, upload, create folder, delete, share, view analytics, view sharing settings), set by a permission setUpload, view and download; more with their own Microsoft 365 loginUpload, view and interact with filesUpload, download and preview; delete, move and rename optionalView, edit or download, as an admin sets
Where an upload landsThe folder the user is viewing, or a file request's folderThe record's folder, or a subfolder set by a formula fieldThe folder a Salesforce Flow picksThe user's own folderExternal storage, moved on upload
What you installCloudFiles, plus the External Users permission setsFiles EnterpriseShare Connect plus Experience Connect24FilesXfilesPro, with its Experience Cloud component

Frequently asked questions

For most teams, CloudFiles: portal users need no Microsoft account, a Salesforce permission set decides what each one can do, and it rates L5 (Extended) for Experience Cloud Support on our scored comparison, the highest of the five apps scored there. sFiles fits teams whose portal users already have Microsoft 365 accounts, Experience Connect fits teams already on Share Connect, and XfilesPro fits teams that want uploads to land in Salesforce first.

See the scored comparison→

Not with CloudFiles, with 24Files' anonymous access, or with sFiles' Uploader and List View. sFiles' full Experience Cloud feature set needs a Microsoft 365 account for each portal user. Appiphony and XfilesPro don't say either way for SharePoint.

Yes, with all five. CloudFiles, sFiles, 24Files and Experience Connect send the file to a SharePoint folder. XfilesPro takes the upload in Salesforce and offloads it to external storage straight away.

Out of the box, Experience Cloud keeps portal uploads in Salesforce's own file storage, and Files Connect, Salesforce's native bridge, cannot create files in external storage from the Salesforce UI. A custom build on Microsoft Graph can do anything, but you build and maintain the sign-in, permissions and folder logic yourself. The five apps above package that work.

Under 30 minutes: install CloudFiles from the AppExchange, connect SharePoint, add the CloudFiles widget to your Experience Cloud page and assign the CloudFiles External Users permission set.

Read the setup guide→

sFiles' AppExchange listing describes it as FedRAMP compliant, but no matching record appears on the FedRAMP Marketplace (checked 1 October 2026). CloudFiles makes no FedRAMP claim: it is independently audited for SOC 2 Type II, certified to ISO 27001:2022, ISO 27017:2015 and ISO 27018:2019, and compliant with HIPAA and GDPR.

CloudFiles, which makes one of the five apps. Every fact comes from the vendor's own public pages, listed under Sources, and nothing on this page is scored.

Sources

Where each fact comes from

Every fact on this page comes from the vendor's own public pages, read on 1 October 2026. CloudFiles makes one of the five apps, so its sources are listed the same way as everyone else's.

Is CloudFiles the right fit for your portal?

In a 30-minute call, the CloudFiles team will look at your Experience Cloud site and SharePoint setup and tell you plainly which of these apps, if any, fits it.