SharePoint
Connect SharePoint so your agents can read documents and lists from the sites your team uses every day. Common use cases include vendor master data, policies, and shared finance folders.
Audience: IT (the enabler) and builders
What it can do
- Read. Files and lists.
This integration does not support Write, Triggers, or Reply today.
Who connects this
Admin-enabled OAuth. IT registers an application in Microsoft Entra once. After that, a team admin or workspace admin connects the integration for a team or the whole workspace. Builders add it to their Projects without signing in.
Microsoft tenant ID trap. The OAuth flow uses tenant_id (the GUID, common, organizations, or consumers), not tenant_type (the SingleTenant / MultiTenant discriminator). Mixing the two produces AADSTS900023. The setup walkthrough below names which value to use.
IT registers the application in Microsoft Entra
Register an application, grant admin consent for the SharePoint scopes, and choose the right tenant configuration.
A team or workspace admin connects the integration
Once stage 1 is done, a team admin or workspace admin opens Integrations, selects Connect on the SharePoint card, and signs in with a Microsoft account that can read the sites. In Available to, they choose Team or Workspace. They then search for a site and pick the resources the integration should sync: entire document libraries, lists, or site pages. To sync one folder instead, open a document library, browse to the folder, and select Use folder. The folder and every subfolder under it sync, and choosing a folder replaces the other resource selections. If a site or folder you expect is missing, select the refresh button on the site list or the folder picker to load it again from Microsoft.
Builders add it to their Projects
In the Project context, builders add the integration with Add to project. They do not sign in to SharePoint.