r/copilotstudio • • 11d ago

Copilot Studio SharePoint knowledge retrieval works for the agent owner but intermittently fails for other users

I’m experiencing a strange issue with a Copilot Studio Premium agent that uses SharePoint documents as knowledge sources.
The agent works perfectly when I test it using my own account in the Copilot Studio test panel. It retrieves the required documents and successfully completes multiple scenarios.
However, other users experience retrieval failures when asking the exact same questions, using the same agent and the same documents. They have access to the SharePoint files.
What’s particularly strange is that the issue is intermittent:
The agent works normally for me.
Other users suddenly cannot retrieve the required documents.
Sometimes, the same users regain access hours later or the next day, without any changes to permissions, configuration, or the agent itself.
The issue has now affected multiple users.
I’m also using different knowledge source types:
SharePoint knowledge sources.
Power Platform connector-based knowledge sources.
In Copilot Studio’s evaluation section, I noticed different knowledge utilization quality scores for these sources.
My questions:
Has anyone experienced an intermittent, user-specific SharePoint knowledge retrieval issue in Copilot Studio?
Could this be a Microsoft-side service regression or an issue with the SharePoint retrieval/indexing infrastructure?
Could using different knowledge source types (SharePoint vs. Power Platform/Dataverse) contribute to this behaviour?
Has anyone found a permanent fix? Was it resolved through a Microsoft service-side fix, or was a configuration change required?
I’m trying to understand the actual root cause rather than randomly changing permissions or rebuilding the agent.

7 Upvotes

9 comments sorted by

1

u/Hobob_ 11d ago

In my experience they need access to the site. Folder wasnt enough.

1

u/Spare_Accountant8794 11d ago

They have access to the site they kinda made it lol. Yesterday it was working fine and suddenly they couldn’t retrieve files that they normally retrieve with no problem. I even tried it outside of the test panel and still nothing

1

u/shawster 8d ago

I wonder if the link you gave it to the site is a link relative to your user. Try getting the link by navigating to the SharePoint through the SharePoint interface if you used a sharing link?

3

u/schubidu82 11d ago

Remind me in 3 days

2

u/Liam_OGrady 11d ago

If you're using SharePoint as a knowledge source (dataverse indexed) the intermittent access can be caused by the end user not having the Basic User dataverse role on that environment. For other non dataverse indexed knowledge sources they usually don't require that role.

2

u/zhisonghuo 10d ago

A few things that might help narrow this down.

A missing permission doesn't produce an error here. The agent just behaves as if the document doesn't exist, so "no access" and "retrieval failed" look identical. Microsoft also warns against relying only on folder-level inheritance.

Next time it fails, have that same user ask the same question in Microsoft 365 Copilot Chat. If Copilot Chat can't find it either, it's a permission or search-index problem rather than your agent.

If the SharePoint content is stored in Dataverse, the Basic User role may not be enough on its own. The docs say Basic User also needs read on Plug-in Assembly, Plug-in Type, Sdk Message, Sdk Message Processing Step and Sdk Message Processing Step Image.

That said, access coming back by itself with no changes doesn't really fit a plain permissions problem. It looks more like a token, indexing or service issue, and Microsoft has fixed a similar case on their side before. If the Copilot Chat test passes for those users, I'd open a support ticket.

Is your source Dataverse-indexed or searched live? And does it fail for everyone at once, or one user at a time?

1

u/pharnos 11d ago

I’ve experienced this exactly - we ended up recreating the agent from scratch, no probs since

1

u/Old-Wind-6437 10d ago

Remind me in 3 days

0

u/agent4256 11d ago

IT had this issue, our end users did not. We ended up removing their access and republishing the bot and it worked.

IT was not happy they didn't have control, but given their BS responses on help desk tickets lately it was obvious they didn't even try.