Copilot Studio SharePoint Knowledge Works for You but Not for Other Users: A Checklist
By Mirko Peters ·
Your Copilot Studio agent answers from SharePoint in your own tests, but colleagues get the fallback message. Check sign-in, permissions, search index, protected files and tenant settings in this order.
You built a Copilot Studio agent, connected a SharePoint site or library, and tested it. It answers well. Then a colleague opens the same agent in Teams or Microsoft 365 Copilot and gets the generic fallback message, such as "I'm not sure how to help with that" or "Sorry, I am not able to find a related topic".
Key points
- SharePoint knowledge runs as the person who is chatting, not as the maker, so a maker test proves very little about other users.
- A user without read access, a missing search entry or an encrypted file all end in the same quiet result: no answer and no error.
- Test the same question as the affected user in Microsoft 365 Copilot Chat to separate an agent problem from a permission or index problem.
- Authentication, Restricted SharePoint Search and file size limits are quick checks that rule out whole groups of causes.
Three Microsoft Q&A and Microsoft Community Hub threads from March to September 2026 describe exactly this. In one, a tester with read permission on the folder only got fallback answers. In another, a user with read and write access, a Copilot license and a place on the agent's allowed list approved a SharePoint permission prompt and still got nothing. In the third, SharePoint lists added as knowledge showed an error without a message.
This article is a checklist built from those threads and from the current Microsoft Learn troubleshooting page for SharePoint knowledge. It is not an official Microsoft procedure. Where the threads and Learn differ, Learn wins, and I say so.
Symptoms
- The maker gets correct answers in the test pane. Other users get the fallback message.
- Files uploaded directly to the agent work for the affected user, but the SharePoint source does not.
- The knowledge source shows as ready, and there is no error anywhere.
- Nothing useful appears in the activity view for the affected user.
Why it fails quietly
Microsoft Learn states that SharePoint knowledge follows Microsoft 365 security trimming. A user needs at least read access, and without it the agent behaves as if the document does not exist. There is no error. The same quiet result appears when the document is not in the search index, when it is encrypted, or when the sign-in setup lacks scopes.
The agent also does not read your library file by file. Learn says it uses only the top three Microsoft Search results to write an answer. If search does not return the right file for that user, there is nothing to summarize.
Step 1: Reproduce as the affected user
- Ask the affected user to open the exact file by its SharePoint address. If that fails, you have a permission problem, not an agent problem.
- Ask the same question, with the same user, in Microsoft 365 Copilot Chat. Learn recommends this test. If Copilot Chat also finds nothing, the cause is permission or indexing. If Copilot Chat works and the agent does not, continue with step 2 and the steps after it.
- Ask the user to type a unique phrase from inside the file into the SharePoint search box. Use text from the document body, not just the file name.
Step 2: Check how the agent signs users in
Learn says agents created in Copilot Studio and Teams use Authenticate with Microsoft by default, and that SharePoint generative answers then run on behalf of the chatting user. With No authentication, the agent does not retrieve SharePoint information at all.
One community answer, marked as the solution in a SharePoint lists thread, reported that access to SharePoint and OneDrive was blocked while authentication was set to No authentication and worked after switching to Authenticate with Microsoft or manual authentication.
- In Copilot Studio, open the agent and go to its authentication settings.
- Pick Authenticate with Microsoft, unless you need a custom Microsoft Entra ID setup.
- If you use Authenticate manually, add the scopes
Sites.Read.AllandFiles.Read.Allnext to the existingprofileandopenid. In the app registration, add the delegated permissionsSites.Read.AllandFiles.Read.Alland grant consent. - Publish again. For Teams, Learn notes that changes can take a few hours, and users can type "start over" to restart with the latest version.
Learn also lists two limits: generative answers from SharePoint are not available to guest users in apps with single sign-on, and group chats or channel messages in Teams are not yet supported for the path without manual authentication.
Step 3: Check permissions on the exact content
Give users at least read access to the sites and files in the knowledge source. Learn adds a warning that you should not rely only on folder-level inheritance. In the tester thread, the answer from Microsoft staff said permissions on the specific folder or files matter, not just the site.
The agent searches the address you registered and everything below it. It does not look at parent folders, sibling folders or other sites unless you add them as separate sources.
Step 4: Check the search index
Learn says recently uploaded files may not be indexed yet, and some settings can keep a site out of search.
- Use the keyword test from step 1. If the file does not appear for the affected user, indexing or search settings are the cause.
- A SharePoint site administrator can ask for a reindex: open Site Information, then View all site settings, then Search and offline availability, and select Re-index site.
- A Microsoft external staff moderator in the March 2026 Microsoft Q&A thread suggested more checks. Confirm that the site setting for appearing in search results is set to yes, that the library is not set to stay out of the index, and that audience targeting on the library is off. The reply also suggested waiting up to 24 hours after access changes. These points come from a forum reply without a link to documentation, so treat them as reported in a community thread, not confirmed in Microsoft Learn.
Step 5: Look for protected and unsupported content
- Encryption: Learn says the agent respects sensitivity labels for access, but it cannot read content that is encrypted. This includes labels that apply encryption, Double Key Encryption and password-protected files. Such a file can show as ready and still return no answer. Test by asking about text that only appears in unprotected files from the same source.
- Page types: Modern pages work. Pages with SharePoint Framework components are not supported, and content from classic
.aspxpages is not used. - File size: Learn gives 7 MB for tenants without a Microsoft 365 Copilot license and 200 MB with one, together with a matching setting called tenant graph grounding with semantic search. Larger files can appear in search but are not processed.
- Renames: Learn warns that renaming a site or folder can break the source link. Generate a new link, update the source in the agent, and check permissions on the new location.
Step 6: Check tenant settings
Restricted SharePoint Search: if it is on for the tenant, Learn says SharePoint knowledge is blocked, no matter how the agent is set up. The SharePoint admin must turn it off or add the sites to the allowed list. See Restricted SharePoint Search.
Lists: for SharePoint lists, Learn requires Dataverse search to be on in the agent's environment. It also notes that lists with more than 35,000 rows reduce quality, and that you should use no more than 10 lists per agent. A reply from September 2026 in the lists thread mentions the same Dataverse search requirement. Another reply there suggested recreating the list as a Dataverse table as a workaround until a fix ships. The reply does not confirm that this worked, and it is not a fix.
Filters and topic settings: check the filters on the source (title, author, modified by, modified on) under Knowledge, then the source, then Edit, then Advanced settings. On a topic with a generative answers node, the option to search only selected sources means the agent will not fall back to other knowledge.
Step 7: Content moderation
Learn lists content moderation as a possible cause. When it blocks an answer, you see no response and no hint. You only see it in logs if the agent sends telemetry to Application Insights. If the questions are harmless and everything above checks out, set up telemetry and look for the filtered result, using the query on the Learn page.
Collect evidence before you open a case
If all of this passes, write down:
- the conversation ID from the affected user's chat,
- the exact question and the time in UTC,
- the client (Teams, Copilot app or web),
- the environment ID,
- the result of the Copilot Chat test from step 1.
What the threads did and did not show
- Two of the threads ended without a confirmed fix. In the tester thread, the first answer (from Microsoft external staff) was a list of likely causes, no answer was marked accepted, and the asker did not report back. In the March 2026 thread, the asker did not report back either.
- The lists thread has a solution mark on a reply that gives general setup advice. The asker did not confirm it.
- In August 2026, two other threads reported that agents which had worked suddenly stopped using SharePoint content. In one thread, about an Excel file in SharePoint, several people reported that it started around Wednesday 12 August, and a Microsoft external staff member opened an internal bug on 18 August as a possible service regression. The other thread was posted on 19 August and reported that existing and newly created agents ignored SharePoint documents. In that thread, the asker wrote on 20 August that Microsoft had fixed an internal problem. This is secondhand and not a statement from Microsoft, and another user reported the same issue on 26 August. If your case affects every user and every agent, check service health first. This pattern is different from the one in this checklist.
Related
Sources
- Microsoft Learn: SharePoint knowledge sources don't return results
- Microsoft Learn: Add SharePoint as a knowledge source
- Microsoft Q&A: Testers unable to get answers from Copilot agent in Stage environment (April 2026)
- Microsoft Q&A: Other users unable to chat with Copilot agent using SharePoint knowledge base (March 2026)
- Microsoft Community Hub: SharePoint lists with Copilot Studio error (April 2026)
- Microsoft Q&A: Copilot Studio cannot use SharePoint documents as knowledge sources (August 2026)
- Microsoft Q&A: SharePoint Excel knowledge source no longer returns results (August 2026)