Forum Discussion
Copilot Studio agents problems connecting to Sharepoint knowledge source
Hello,
Since last week users in my tenant are experimenting issues regarding the connection between copilot studio agents and Sharepoint. The agents are not able to extract information from Sharepoint sites, printing there is not information in the Sharepoint site regarding the user's question when that information is in Sharepoint. These agents used to work well till last week. Does have been any update in Microsoft 365 services that can be affecting these agents ability to retrieve information from Sharepoint?
2 Replies
Hello,
Since this is a sudden regression affecting multiple agents simultaneously across your tenant (agents that previously worked), one question first:
Which Copilot Studio experience did you use to build your agents — the classic experience (canvas with topics) or the new experience (production-ready preview)?
Microsoft's documentation confirms that some SharePoint features are not yet available in the new experience, and authentication and retrieval behaviors can differ between the two...
This will help narrow down the diagnosis.
In parallel, here are the points you can check :
- If a tenant admin recently enabled Restricted SharePoint Search, SharePoint access is completely blocked for Copilot Studio agents. Check : SharePoint Admin Center > Search > Restricted SharePoint Search.
- If a SharePoint site or folder used as a knowledge source was recently renamed, the existing source link breaks and causes a permission gap the agent silently returns no results.
Verify that the SharePoint URLs configured in your agents still match the current site/folder names.
- Check your M365 Admin Center > Health > Service health for any active incidents related to Copilot Studio or Microsoft Search.
- Verify that your Entra ID app registration still has Sites.Read.All and Files.Read.All granted. If consent was silently revoked, the agent returns no results without surfacing any error.
- A service-side indexing change can silently interrupt SharePoint content retrieval with no visible alert.
The recommended next step is to open a support ticket via the M365 Admin Center, referencing the exact date the regression started, so Microsoft can correlate it with any service-side changes on their end.
Hope you find this useful
We are using the classic experience.
About Restricted SharePoint Search, this is retired and we have not enabled the RCD at any moment.
No sites were renamed or links changed, also it is affecting multiple sites.
Service Health is correct, there are some advisories but not related.
Entra ID App registration is not realted, we are using M365 suite with Copilot Studio, an app was not created for this.
