For a SharePoint integration with Salesforce, you have three options: Salesforce Files Connect, a Power Automate flow, or a Zapier zap. Files Connect lets people find, open and share SharePoint files from inside Salesforce. Power Automate and Zapier can make a SharePoint folder when a Salesforce record is made. Where it stops: Files Connect shows files but doesn't build folders, a shared copy doesn't get later edits, and none of them builds the client's documents or checks them. AI agents make the folder, build the documents from your template, and put the link on the account.
What a SharePoint integration with Salesforce has to do
Sales lives in Salesforce. Client files live in SharePoint. Without a SharePoint integration with Salesforce, people hunt for the right folder, save files in the wrong place, and make new client folders by hand.
A good connection does two things. Each client in Salesforce gets the right folder in SharePoint, set up the same way each time. And people can get from the Salesforce account to the client's files in one click.
Three ways to connect Salesforce and SharePoint
One is built into Salesforce, one comes from Microsoft, and one uses Zapier.
Salesforce Files Connect
- How it works
- An admin turns on Files Connect, signs Salesforce in to SharePoint Online through Azure, and adds SharePoint as an outside data source. Then people find, open and share SharePoint files from Files home and the feed in Salesforce, and can search them there.
- Good for
- Teams who keep files in SharePoint and want reps to reach them from Salesforce.
- Where it breaks
- It shows and shares files; Salesforce's guide has no step for making folders in SharePoint. A shared copy doesn't get later edits made in SharePoint. Files from SharePoint can't be previewed in Salesforce, and files in folders with # or % in the name can't be opened.
A Power Automate flow
- How it works
- A flow uses Microsoft's Salesforce connector, which can start when a record is made or changed, and the SharePoint connector, which can create a new folder or a file. For example: a new account in Salesforce makes a client folder in SharePoint.
- Good for
- Teams on Microsoft 365 who want to build the steps themselves.
- Where it breaks
- The Salesforce connector is Premium, and your Salesforce account needs API access; Microsoft says trial accounts don't work. Its known issues say the changed-record trigger can't see a new attachment, and older connections can lose their sign-in if unused for a long time.
A Zapier zap
- How it works
- Zapier's Salesforce and SharePoint templates add SharePoint list items from Salesforce records, add SharePoint documents to Salesforce deals, or attach new SharePoint files to Salesforce. A zap you build can also use SharePoint's Create Folder action.
- Good for
- Simple one-way moves, like one folder per new client.
- Where it breaks
- Salesforce is a Premium app on Zapier, and on the Free plan Zapier checks for new data every 15 minutes. Each zap is one trigger and one action, so subfolders, files and the link back on the account are each more steps to build and watch.
Arkeo agents
- How it works
- When a deal closes in Salesforce, agents make the client folder in SharePoint, build the client's documents from your template, fill in the status and client name on each file, and post the link back on the Salesforce account as a note.
- Good for
- Teams who build the same client documents again and again, and need them right.
- Where it breaks
- Anything your rules keep for a person, like a final review before a document goes to the client, goes to your team in one message.
Set up Salesforce Files Connect: five steps
Salesforce's Files Connect guide has the full screens. These are the parts, in order.
- 1Check your edition
Files Connect for cloud sources like SharePoint Online comes with Professional, Enterprise, Performance, Unlimited and Developer editions.
- 2
Turn on Files Connect and set copy or reference
Turn it on in Setup and give the right people access with permission sets or profiles. Decide how files are shared: a copy stored in Salesforce, or a reference that points back to SharePoint.
- 3
Sign Salesforce in to SharePoint through Azure
Make an authentication provider in Salesforce, register an app for it in the Azure portal, and give that app SharePoint permissions.
- 4
Add SharePoint as a data source
Define SharePoint Online as an external data source using that provider. Optional: make an external object so SharePoint files show up in normal Salesforce search.
- 5
Have each person sign in, then test
If each person signs in on their own, they add their SharePoint sign-in in their personal settings. Then open one client file from Files home to test it.
Where the Salesforce SharePoint integration stops
Each option links the two programs in one direction. The work left is building and keeping each client's folder and documents right.
Files Connect shows files. It doesn't make them. Salesforce's guide covers finding, opening and sharing SharePoint files, and has no step for making folders or files. In copy mode, a file shared in Salesforce doesn't get later edits made in SharePoint, and everyone in a Chatter group it is shared with can open it, even without SharePoint access. In reference mode there are no previews and each person has to sign in. Files in folders with # or % in the name can't be opened.
Sign-in is a common problem. In a Salesforce community thread on Files Connect, an admin hit the known "External data source is unavailable" error, and the fix offered was a set of Azure permissions that Salesforce's guide doesn't list. Microsoft's own known issues for its Salesforce connector say older connections can lose their sign-in after sitting unused.
Flows and zaps move one thing at a time. A flow can make a folder, but the trigger for a changed record can't see a new attachment, and fields that hold more than one choice can't be written. Each zap is one trigger and one action.
And nobody builds the documents. Someone still makes the client's files from the template, fills them in, and puts the link back on the account.
The agents that do it
Each agent does one job from start to finish, in your own SharePoint. Your team talks to them in Slack or Teams.
Days of building becomes a review.
- Reads the client fileper client
- Builds it from your templateper document
- Checks your wording word for wordevery time
Days of building becomes a review.
- Takes the client package from SharePointper client
- Builds the manual from your master templateabout 9 minutes
- Checks fixed policy text word for wordeach file
Questions
Is my customers' information safe?
Yes. Agents work in your own Salesforce and SharePoint and see only what their job needs. Customer details never go into public AI. Agents connect to AI through business-grade connections audited under SOC 2.
Can Salesforce save files to SharePoint?
Not with Files Connect alone; it shows and shares SharePoint files. To make folders or files in SharePoint when something happens in Salesforce, use a Power Automate flow, a Zapier zap, or agents.
Does Salesforce Files Connect work with OneDrive?
Yes. Salesforce's Files Connect guide lists OneDrive for Business as a data source, set up the same way as SharePoint Online.
Why can't I open some SharePoint files in Salesforce?
Salesforce's guide says files in SharePoint folders with # or % in the name show up but can't be opened. In reference mode, each person also has to add their own SharePoint sign-in.
What does it cost?
You get the price on the call, along with the hours it saves your team.