Copilot Studio SharePoint knowledge source returning old/stale file version instead of updated one

Question

Issue: I updated a file in the connected SharePoint library (replaced an older version of a PDF with a newer one — same filename, content changed). After the update:

• The agent continues to answer using content from the old version of the file.
• I have tried: manually clicking Refresh on the knowledge source, republishing the agent, forcing the newest version, and waiting

What I've checked so far:

• The updated file is confirmed correctly saved and visible directly in SharePoint (ruling out a versioning/sync issue on the SharePoint side itself).
• The knowledge source status in Copilot Studio currently shows: ["Ready"].
• I don't see an option to force re-indexing of a single file, only the entire knowledge source.

Questions:

1. Is this expected behavior due to asynchronous indexing/caching, or does it point to a bug in my specific setup?
2. What is the actual expected refresh/re-index interval for SharePoint knowledge sources? I've seen conflicting information in different places — some suggesting near real-time sync, others citing 4–6 hours, others up to 24–48 hours.
3. Is there a supported way to force re-indexing of a single changed file without removing and re-adding the whole knowledge source?
4. Does behavior differ depending on whether the source was added as a native SharePoint knowledge source vs. a Dataverse-backed SharePoint connector?

Answer 1

Hi @Manikandan V

According to Unstructured data as a knowledge source - Microsoft Copilot Studio | Microsoft Learn, SharePoint content isn't queried directly by the agent at runtime. Instead, Copilot Studio retrieves the content into Dataverse, where it's processed into semantic indexes and vector embeddings that the agent uses to answer questions.

Regarding your questions:

1. Is this expected behavior?

This can be expected behavior depending on how the SharePoint knowledge source was configured. Updates to SharePoint content might not be reflected immediately in agent responses because indexing and synchronization occur asynchronously. The knowledge source showing Ready indicates the source is available, but it doesn't necessarily mean a recently changed document has already been reprocessed and incorporated into the search index used by the agent.

2. What is the expected refresh interval?

For SharePoint content ingested through the Upload files > SharePoint option, Microsoft documentation states that content is synchronized and refreshed automatically, with content freshness typically occurring every four to six hours.

3. Can a single file be force re-indexed?

No supported method is documented to manually trigger a refresh or force reindexing of an individual SharePoint file. Refresh and reindex operations are handled automatically by the service.

4. Does behavior differ depending on which SharePoint option is used?

The documentation describes two different SharePoint knowledge source options:

• SharePoint connector: Content remains in SharePoint and the agent queries SharePoint search infrastructure directly. Documentation describes content freshness as "Real time, and reflects the latest available content."
• Upload files > SharePoint: Selected SharePoint files are copied into Dataverse, indexed using semantic indexes and vector embeddings, and kept synchronized with the source. Documentation states that content freshness is typically every four to six hours.

Could you confirm which SharePoint option was used when configuring the knowledge source? If you're using the Upload files > SharePoint option, some delay while synchronization and reindexing complete would be expected. If you're using the SharePoint connector option and the agent continues returning the old content after an extended period, it may be reasonable to open a Microsoft support case for further investigation.

I hope this helps.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".       

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.