July 11, 2026
Salesforce SharePoint integration connects your Salesforce org to Microsoft SharePoint so teams can view, search, and manage SharePoint documents directly from Salesforce records - without copying files into Salesforce or paying for its pricier storage. The most common route is Salesforce Files Connect, the native feature built for exactly this, with third-party apps and custom Microsoft Graph API builds as alternatives for deeper needs.
This guide walks through the whole thing: what the integration does, the ways to build it, and a step-by-step Files Connect setup you can follow today.
Salesforce SharePoint integration is the connection between Salesforce and Microsoft SharePoint that lets users access and manage SharePoint files and data from inside Salesforce, without duplicating documents across both systems. Instead of downloading a contract from SharePoint and re-uploading it to an Opportunity, the file simply appears - as a reference - on the Salesforce record.
The native path is Salesforce Files Connect, which surfaces SharePoint content in Salesforce as external files. Files stay in SharePoint (your system of record for documents), while Salesforce shows, searches, and shares them. That keeps a single source of truth and avoids doubling your storage.
Teams pursue a Salesforce and SharePoint integration for a few practical reasons, and they tend to compound:
There's no single "SharePoint Salesforce integration" button - you choose a method based on whether you need file access, record data, or deep custom logic. Here's how the options compare.
MethodBest forEffortSalesforce Files Connect (native)Viewing and searching SharePoint files from Salesforce recordsLow - configuration, no codeAppExchange apps (e.g., document-management connectors)Auto-filing, folder structures, bulk file moves, richer UILow to medium - install and configureCustom build with Microsoft Graph APIBespoke logic, custom UI, non-standard data flowsHigh - Apex callouts and developmentMiddleware (MuleSoft, iPaaS)Multi-system document and data orchestrationMedium to high - platform-based
For most teams that just want SharePoint files to appear on Salesforce records, Salesforce Files Connect is the right starting point. Reach for an app or a custom build when you need automated filing, custom folder logic, or two-way data sync beyond files.
This walkthrough uses Salesforce Files Connect with SharePoint Online - the most common setup. Work through the steps in order; the authentication piece is where most people get stuck, so take it slowly.
Confirm the goal before you touch Setup. Most teams want read access to SharePoint files from Salesforce records. If you also need to write files back, auto-create folders, or sync record data, note that now - it may push you toward an app or custom build instead of Files Connect alone.
In Salesforce Setup, search for Files Connect and enable it. Then create a permission set with the "Files Connect Cloud" permission and assign it to the users who need SharePoint access. Files Connect only works for users who have that permission, so don't skip the assignment.
SharePoint Online authenticates through Microsoft, so you'll register an app in Microsoft Entra ID (Azure AD) and create a matching Authentication Provider in Salesforce. Copy the client ID and secret from Azure into the Salesforce auth provider, and paste Salesforce's callback URL back into the Azure app registration. Grant the app the SharePoint and Microsoft Graph permissions it needs to read files.
In Setup, create a new External Data Source of type "SharePoint Online" (or the current Files Connect option for Microsoft 365), point it at your SharePoint site URL, and link it to the authentication provider from Step 3. Set the identity type - named principal for a shared service account, or per-user for individual sign-in.
Open the external data source and authenticate with a Microsoft account that has SharePoint access. Salesforce runs the OAuth handshake with Microsoft; a successful connection means Files Connect can now see your SharePoint content. If it fails here, recheck the Azure permissions and the callback URL - that's the usual culprit.
Add the Files related list (or a Files Connect component) to the page layouts where users need documents - Opportunities, Accounts, Cases. Users can then browse SharePoint, attach file references to records, and open documents without leaving Salesforce. Global search will also return matching SharePoint files once indexing is enabled.
Before announcing it, test with a handful of real records and users across permission levels. Confirm the right people see the right files and that SharePoint permissions are respected. Then roll it out with a short guide so reps know where to find and attach documents. Getting this rollout right is the kind of adoption work our Salesforce integration team handles end to end.
Files Connect is free, native, and quick - but it has limits. It's built for file access, not automated filing or complex folder rules. When teams outgrow it, they move to an app or a custom build.
If your need is "let reps see and search SharePoint documents on Salesforce records," Files Connect covers it with no code and no extra license. It respects SharePoint permissions and keeps files in place. For a large share of orgs, this is the whole project.
Choose a document-management app when you need automated filing (every attachment routed to the right SharePoint folder), custom folder structures per record, or bulk migration of existing Salesforce files into SharePoint. Choose a custom Microsoft Graph API build when your logic is genuinely unique - a tailored UI, conditional routing, or two-way data sync that no app offers. Both need more setup than Files Connect, but they unlock automation Files Connect can't.
In practice, that automation looks like auto-filing every attachment to the right SharePoint folder, building a predefined folder structure per record with a Flow or Apex action, and bulk-migrating existing Salesforce files into SharePoint to free storage. Document-management apps for this typically run around $6–$12 per user per month; a custom build trades that subscription for engineering time. One detail worth knowing: even when a file lives in SharePoint, Salesforce usually keeps a Content Document Link on the record, so it still appears exactly where users expect.
The integration earns its keep differently for each team. A few patterns we see most often:
These map to the industries we work across, from manufacturing and field service to BFSI, where document-heavy processes span Salesforce and SharePoint.
Most Salesforce SharePoint integration issues come from a short list of avoidable mistakes. Plan around these from the start.
PitfallBetter practiceAuthentication misconfigured in AzureDouble-check client ID, secret, callback URL, and Graph permissionsForgetting the Files Connect permission setAssign it to every user who needs SharePoint accessMismatched permissions between systemsMap SharePoint and Salesforce access so users see only what they shouldExpecting automated filing from Files ConnectUse an app or custom build when you need routing and folder logicNo rollout planTrain users and document where files live and how to attach them
For platform specifics, the Salesforce Admins resources and Salesforce Developer blog cover Files Connect and external data sources, and Salesforce Ben and Apex Hours are strong for setup walkthroughs.
Yes. Salesforce integrates with SharePoint natively through Salesforce Files Connect, which surfaces SharePoint files on Salesforce records. For deeper needs, AppExchange apps and custom Microsoft Graph API builds extend the connection with automated filing and data sync.
Enable Files Connect in Salesforce, register an app in Microsoft Entra ID (Azure AD), create a matching authentication provider and a "SharePoint Online" external data source in Salesforce, authenticate with a Microsoft account, then add the Files related list to your page layouts.
Salesforce Files Connect is the native feature that connects Salesforce to external content systems like SharePoint and OneDrive. It lets users access, search, and share external files as references from within Salesforce, without storing the files in Salesforce.
Files Connect is included with most Salesforce editions that support external data sources, so the native route usually adds no license cost. AppExchange apps and custom builds carry their own pricing, and you'll still pay for SharePoint and Microsoft 365 on the Microsoft side.
With Files Connect, files stay in SharePoint - Salesforce shows references to them, not copies. That's the main advantage: one source of truth and no duplicated storage. Apps that copy or move files can change this, so confirm the storage behavior of any tool you add.
A Salesforce SharePoint integration pays off fast - lower storage costs, one home for every document, and reps who find files without leaving a record. Files Connect gets most teams there with configuration alone, while apps and custom Microsoft Graph API builds handle the automation-heavy cases. The key is matching the method to what your workflows actually need.
That's where we come in. Minuscule Technologies is a trusted Salesforce engineering partner with 160+ specialists and 75+ projects delivered since 2014, and we build Salesforce integrations and document-management connections for enterprises - including Nasdaq-listed firms - that need Salesforce and Microsoft working as one. From a quick Files Connect rollout to a custom SharePoint build with automated filing, we scope it, build it, and manage it so your teams just get the files they need.
Ready to connect Salesforce and SharePoint the right way? Talk to Minuscule Technologies and let's map your document workflows.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
