Forum Discussion
SharePoint lists with Copilot Studio error
troyho You’re seeing this error because Copilot Studio is having trouble using the SharePoint link you entered.
A few things to check:
- Use a SharePoint site or library link, not a direct link to a single file (for example, use the site like .../sites/YourSite, not the .docx file itself).
- Make sure you’re signed in with an account that has permission to read that SharePoint site and its files.
- If the file is very large, Copilot Studio might not be able to use it.
I also ran into a similar issue myself: I had set the agent’s Authentication setting to No authentication and then tried to connect a SharePoint file. Because “No authentication” doesn’t allow Copilot Studio to read SharePoint or OneDrive content, I got an error. I fixed it by switching the authentication to a supported option (for example, Authenticate with Microsoft or manual authentication), and after that the SharePoint file connected and worked correctly.
For a step‑by‑step guide and all the technical details, please see Microsoft’s official article:
“Add SharePoint as a knowledge source – Microsoft Copilot Studio”
https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-add-sharepointThis page explains what types of SharePoint links are supported, how authentication should be configured, and how to set up permissions so Copilot Studio can read your SharePoint content.
First confirm that Dataverse search is enabled in the agent’s environment, then verify the affected account has Read access to each SharePoint list and that the agent uses Authenticate with Microsoft. SharePoint list knowledge requires Dataverse search, while Restricted SharePoint Search, missing permissions, or missing Sites.Read.All and Files.Read.All scopes under manual authentication can produce silent failures. A similar active issue is swallowing a Dataverse FederatedKnowledgeSearch 403 instead of displaying the authorization error, particularly in production or sandbox environments where users might lack the required Dataverse role. If these checks pass, capture the environment ID, UTC timestamp, session or correlation ID, and a HAR trace, then open a Copilot Studio support case because repeatedly recreating the connection will not resolve a service-side authorization failure.