Copilot Studio Friction
New or updated files don't show up in answers
Last verified
Details & related
Assessment
- Confidence
- CorroboratedMultiple independent sources describe the same behaviour.
- Severity
- Degrading
- Typical time lost
- Hours
Identification
Verification & changes
Verified
Doc check by human: Bounded web check (3 sources) during seed migration: docs claim real-time connections for SharePoint lists only; files rely on scheduled sync; community still reports stale answers until manual refresh.
Change
Provisionally approved by the Product Owner; external LLM quality review pending.
Change
Initial record created from the seed dossier (migration wave 1).
Are you in the right place?
- You uploaded or updated files in a connected SharePoint library or other knowledge source.
- Questions about the new content return nothing or an outdated answer.
- Older files from the same source are answered normally.
- The agent itself was not changed since the files arrived.
- Hours or days later, the new content may appear on its own.
If instead a specific PDF is never used, old or new → see Your PDF files are ignored. If instead every question against knowledge returns nothing → see Knowledge returns nothing — and no error is shown. If instead your agent changes are missing in Teams → see Teams answers with an old version of your agent.
What's happening
Copilot Studio answers from an index, not from your live files. An index is a prepared, searchable copy of your documents' content. New and changed files reach that copy late, and mostly not on their own. Think of a library catalog: a donated book stays unfindable until a librarian catalogs it. The documentation adds confusion. As of 2026-07-08, the docs promise a "real-time connection" — but for SharePoint lists. For files and libraries, the same docs describe a scheduled background synchronization job. Makers consistently observe static behavior: new files stay invisible until someone refreshes the source. Trust the observed behavior and refresh deliberately.
For technicians
- The dossier flagged a docs-versus-behavior conflict; our doc check on 2026-07-08 confirms it persists.
- The official SharePoint knowledge doc claims a "real-time connection" for lists; connected files get a scheduled synchronization job.
- Microsoft also ships a Copilot Studio Kit feature for SharePoint synchronization — a signal that built-in freshness is limited.
- Indexing exposes no status; makers cannot see progress or completion.
How to fix it
Solution 1
Official workaroundRefresh the knowledge source manually
- Open your agent in Copilot Studio.
- Select "Knowledge".
- Select the affected source.
- Start a refresh from the source's menu.
- Allow generous time; indexing shows no progress indicator.
✅ You should now see: questions about the new content answered in the test pane.
Solution 2
Community workaroundAutomate the refresh with Power Automate
- Create a Power Automate flow that triggers when a file is created or modified in the library.
- Have the flow trigger a refresh of the agent's knowledge source.
- Test with a real file change.
✅ You should now see: new files appearing in answers without manual work, after the indexing delay.
Solution 3
Official workaroundUse the Copilot Studio Kit SharePoint synchronization
- Read Microsoft's guidance page for the Copilot Studio Kit "SharePoint synchronization" feature.
- Install the Copilot Studio Kit in your environment with your admin's help.
- Configure synchronization for the affected agent and library.
✅ You should now see: file changes flowing into answers on the configured schedule.
Check that it worked
Add a small file with a made-up fact to the source. Refresh the source and wait. Ask for that fact in the test pane. Expected: the answer cites the new file. Remove the test file afterwards.
If it didn't work
- Indexing is still running. There is no status display; wait an hour before you change anything.
- The file itself is blocked. Size caps and protected formats stop files permanently. See Your PDF files are ignored or not answered.
- You tested in a channel, not the test pane. Channel copies lag behind after publishing. See Teams answers with an old version of your agent.
- Your refresh flow failed. Check the flow's run history in Power Automate.
Prevent it next time
- Build a refresh trigger as a standard building block for every file-based knowledge source.
- Plan content updates ahead of deadlines; assume the index lags by hours.
Evidence
Official documentationlearn.microsoft.com
States that a SharePoint list creates a real-time connection, while connected files are refreshed by a scheduled background synchronization job.
Community threadlearn.microsoft.com
Makers report new and updated SharePoint files staying absent from answers until a manual refresh, with no live-sync option offered.
Official documentationlearn.microsoft.com
Official guidance offers a Copilot Studio Kit SharePoint synchronization feature to improve answer freshness for file-based knowledge.