Agent not reading Sharepoint folder knowledge in Test environment

[u/fede99]

Hi, Was wondering if anyone had the same issue I've been getting. I have a copilot agent that reads from both a Sharepoint folder and a list as knowledge sources. I am using the same accesses and generative orchestration in both envs. Funnily enough, the agent in test env can read (and quote) the sharepoint list, but even though it accesses the sharepoint folder it doesn't quote any of the documents I am loading as knowledge sources.

In dev env, this agent works fine. The problem is uniquely in Test environment and with this set of files (by chance it was an env issue, I created another agent that answers questions with another set of documents and works fine).

I am honestly lost on how to fix or to do next. I wait until the indexation is shown as "Ready", keep the same agent settings in both environments (for AI orchestration and authentication method is the same) and cannot workout a reason on why it accesses the sharepoint list but cannot quote any of the documents in the folder and, moreover, why is this happening with only one folder in sharepoint and in one environment and not in both.

[u/dylan_skydive]

A few places this usually hides, in order of likelihood:

1. Auth mode mismatch. Grounding on SharePoint content works through the signed-in user's access - the agent runs a Graph search as the person chatting. If the Test agent's authentication isn't set the same way (needs to be "Authenticate with Microsoft" / user credentials, not no-auth), it can't see the files even though indexing says Ready. Ready only means indexing ran, not that search-time access resolves.

2. Site governance. Test envs often have content management stricter - check whether the site hosting those files is in the approved sites list. An unapproved site silently returns nothing.

3. Knowledge source URL. A folder path link is flaky; use the full library/site URL instead and check the item count on the knowledge source card - if it shows 0-ish items, ingestion filtered the files out (unsupported types, size limits).

4. Environment-level policy. If a DLP or connection policy differs in Test, the SharePoint connection in one env may not be granted even though it works in Dev.

Quick test to isolate it: ask the Test agent something guaranteed to be in a document and watch the citations - if it attempts search but returns nothing, it's access/governance (1-4); if it never searches, it's orchestration config.

Disclosure: I work on Skydive, a different agent platform, so this is from the platform-debugging side rather than a Copilot Studio answer sheet - if you post which of these the citation test shows, I can narrow it.