Content & Documents · Integration
Microsoft SharePoint
Add Microsoft SharePoint to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft SharePoint integration so your product works with the documents your customers already keep in their own sites, rather than pulling copies into storage you then have to secure. SharePoint permissions are inherited, broken and re-granted at site, library, folder and item level, and this is the easiest thing in the category to get subtly wrong, so access runs through each customer's own grant and your product can never read what the connected account could not read itself. fastn handles per-tenant OAuth, token refresh, upload sessions for large files, paging across libraries and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own SharePoint sites so your product reads and writes files in their document libraries in place.
File a generated document into the right library and folder, with the site's existing permissions applied.
Read and update list items so structured content in SharePoint drives what your product shows.
Trigger your product when a file or list item changes, so nothing depends on a nightly crawl.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent searches the sites a user can already see and cites the documents it used.
An agent uploads or updates a document within scoped permissions, with each write logged.
An agent reacts to a new file in a library and runs the next step of an approval.
Example prompt
Find the latest signed contract for this client in the deals library and summarise its renewal terms.
Set up Microsoft SharePoint in 4 steps
- 01Open the Microsoft SharePoint connector from your fastn dashboard.
- 02Have each customer authenticate their own tenant and choose which sites your product may access.
- 03Map the libraries, lists and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Microsoft SharePoint integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft SharePoint integration without building it. Your customers connect their own Microsoft SharePoint account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft SharePoint update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft SharePoint connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Microsoft OneDrive
Microsoft Word
BoxOften used alongside
Tools the same teams tend to run next to Microsoft SharePoint, across other categories.
Shopify
Stripe
Jira
AsanaMicrosoft SharePoint integration FAQ
How do I add a Microsoft SharePoint integration to my product?
Enable the Microsoft SharePoint connector in your fastn dashboard, then let each customer authenticate their own Microsoft SharePoint account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft SharePoint client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Microsoft SharePoint account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft SharePoint account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Microsoft SharePoint integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent searches the sites a user can already see and cites the documents it used.
Who maintains the Microsoft SharePoint integration?
fastn does. When Microsoft SharePoint changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Microsoft SharePoint integration run under?
Each customer's own Microsoft SharePoint grant. Where Microsoft SharePoint holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Microsoft SharePoint automatically?
Where Microsoft SharePoint supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Microsoft SharePoint integration?
A common starting point: connect their own SharePoint sites so your product reads and writes files in their document libraries in place. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Microsoft SharePoint integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft SharePoint does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft SharePoint to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.