Is Files Connect enough on its own?

For Salesforce admins, IT and security reviewers, and whoever signs off the budget.

What it actually does

Files Connect is Salesforce's own bridge to Box, Google Drive, SharePoint Online, OneDrive for Business and Quip. It's included with the platform from Professional edition up. Nothing to buy to find out if it's enough.

Reading is largely solved: browse, open and download an external file from a record. Writing is not. Salesforce's own FAQ states it plainly: “The Salesforce UI doesn’t feature those write capabilities.” Creating or updating an external file only works through the Chatter REST API, which means a developer builds it; an admin cannot configure it.

In our own test of that API path, against a live Developer Edition org, it can create and update a file. DELETE is advertised in the API's own Allow header but refused, with 403 and {"errorCode":"FUNCTIONALITY_NOT_ENABLED","message":"Content Hub Delete External Item is not enabled for this organization or this user."} (Developer Edition; unverified on Enterprise). A created file can't be given a name: it lands with the literal filename null, and because of that, creating a second file in the same folder collides with {"errorCode":"CONTENT_HUB_UNEXPECTED_EXCEPTION","message":"Object already exists"} (Developer Edition; unverified on Enterprise). Net effect: the write path exists, but it's close to unusable for creating more than one file per destination.

Source: CloudFiles Files Connect test, Developer Edition, 17 Aug 2026.

What “reading” doesn't include: preview

Browsing and downloading an external file works. Previewing one inside Salesforce does not.

In our own test, six files spanning roughly 50 bytes to 2 GiB across four types (PDF, DOCX, ZIP, TXT), all produced the same overlay: “No preview available”, with a single button, “Open in Microsoft SharePoint Online.” Salesforce previews native files of the same types without difficulty, so this isn't a size threshold; it's categorical. Downloads worked fine at every size we tried (see below).

If you're picturing “our documents, viewable inside Salesforce,” the honest answer is that the preview pane never renders external content, and the only way to actually look at one leaves Salesforce for SharePoint Online. (SharePoint Online only; tested in a Developer Edition org against a Microsoft 365 E5 Developer tenant.)

Source: CloudFiles Files Connect test, Developer Edition, 17 Aug 2026.

Size limits, tested directly

Downloads and uploads don't share a limit. Test each direction separately.

Download: no cap found. Files of 45 MB, 55 MB, 250 MB and 2 GiB all downloaded byte-exact (MD5 match) in our own test, and the 2 GiB file's zip integrity checked out too. The 45 MB and 55 MB results were re-pulled from the live API on 17 Aug 2026 and matched again; the 250 MB and 2 GiB fixtures used for that first pass are no longer available to re-check byte-for-byte a second time, so treat the 2 GiB result as sound but not yet doubly confirmed.

Upload: capped at 75 MB, named in the error: {"errorCode":"INVALID_FIELD","message":"This file exceeds the maximum size limit of 75MB"}. (Developer Edition; unverified on Enterprise.)

You can pull a 2 GB file out and cannot push a 100 MB file in. If a spec sheet says “file size limit,” ask which direction it means.

Source: CloudFiles Files Connect test, Developer Edition, 17 Aug 2026.

Search, tested directly

• Full-text search works, including over a document's body text, and it's reachable from the Salesforce UI, but only inside the connected source's own file-picker search box. Salesforce's global search does not surface external content at all.
• No fuzzy matching: a single typo returns nothing.
• A query names exactly one external data source; nothing in the syntax lets you search two at once.
• Search isn't limited to folders you can actually browse: it found a file inside a folder that can't be opened at all (the # case below).

Source: CloudFiles Files Connect test, Developer Edition, 17 Aug 2026.

What standing it up requires

• OAuth 2.0, through an auth provider configured before the external data source itself.
• An identity model: Per User (everyone authenticates individually, preserves SharePoint's own permission model) or Named Principal (one shared credential, simpler, collapses that model into one account).
• The Files Connect Cloud permission, for users and for admins configuring data sources.
• Customize Application, to set it up.

Chatter is not a requirement, despite older guidance suggesting the write path depends on it. In our own test we disabled Chatter org-wide and re-ran eight checks: browsing, both search modes, download, a record's external-files count, the Files UI's connected-source display, and an API write. Every one kept working.

Source: CloudFiles Files Connect test, Developer Edition, 18 Aug 2026.

Where it quietly stops

• Only document libraries are supported; other SharePoint list types are not.
• A folder named with # silently returns its parent folder's contents instead of its own, not an error, just the wrong files, confirmed in our own test. A folder named with % always appears empty, also confirmed. Neither is announced anywhere in the UI.
• SharePoint Managed Metadata / Taxonomy fields are not supported.

Salesforce's FAQ also publishes a 50 MB download cap, a “SharePoint 2013 only” line, and says Updated By and Name don't support the = operator, all attributed to the Secure Agent, a component Salesforce retired on 1 October 2021 and states is not required for SharePoint Online. We tested all three ourselves, in a live Developer Edition org against a Microsoft 365 E5 Developer tenant: there is no download cap we could find (2 GiB downloaded byte-exact); modern team sites and communication sites both work (SharePoint Online only); and = works fine on Name; the real gap is that the external object has no Updated By field to filter on at all.

Sources: Files Connect FAQ, quoted, retrieved 21 Aug 2026; CloudFiles Files Connect test, Developer Edition, 17 Aug 2026.

Copy versus reference

Files Connect offers two sharing modes, and the admin picks one for the org.

Sources: Access and Share Files Connect External Files, retrieved 21 Aug 2026; CloudFiles Files Connect test, Developer Edition, 17 Aug 2026. It's a ratio, not a ceiling, and it doesn't change by edition.

What your answer means

• Read-only, no creating or updating files from Salesforce
• Standard objects, nothing custom
• No folder-as-a-unit, no automation, no portal or Experience Cloud users
• Your own real files, tested by you, comfortably under whatever size you actually verified

All true? Files Connect is enough. Stop. No third-party app needed, no procurement.

Any untrue? The gap is real. It closes only by building on the Chatter REST API yourself, or by an external app doing the write path, folders, automation or portal access for you.

Where this stops

This page settles Files Connect specifically. It says nothing about how files attach to records, identity beyond Files Connect's own model, migration, or cost; those are the guide's other questions. CloudFiles sells one of the external apps a gap here eventually points toward, and every claim above is Salesforce's own, dated, and checkable without us.