web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Slow Performance using...
Copilot Studio
Suggested Answer

Slow Performance using SharePoint as Knowledge source

(0) ShareShare
ReportReport
Posted on by 42
Hi everyone, 
we're having an issue where the Copilot Studio agents are extremely slow when connecting to large SharePoint site collections. The new GitHub Harness agents are even worse than the standard agents. 😫
In some cases, we're seeing response times of 40–60 seconds for the first response—and that's with just instructions and one connected SharePoint knowledge source. 
 
We've already tried different models and also tried splitting the site collection into sources containing the individual libraries (Site Pages, Shared Documents, etc.), but that didn't help either.

Any ideas?
Categories:
I have the same question (0)
  • Suggested answer
    Ulrich_Zogo Profile Picture
    81 on at
    Hi @Louisa#
     

    This does not look like something that changing the model or simply splitting the SharePoint site into more knowledge sources will necessarily solve.

    There are actually two different SharePoint retrieval paths in Copilot Studio. The full SharePoint knowledge source queries SharePoint search at runtime, whereas Upload files > SharePoint stores and vector-indexes selected files/folders in Dataverse. For a curated document set, I would test the latter and compare the response time. Microsoft documents the runtime differences here:

    https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-unstructured-data

    If you need to keep the full SharePoint integration, Microsoft also specifically recommends using the SharePoint knowledge-source Advanced settings filters (Title, Author, Modified by/date) to reduce the search scope and improve performance:

    https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-add-sharepoint#filter-your-sharepoint-source

    I would also avoid the GitHub Copilot harness for this particular test. Microsoft positions that harness for reasoning-heavy, multi-step work, while the Standard harness is intended for predictable Q&A/help-desk scenarios using enterprise knowledge:

    https://learn.microsoft.com/en-us/microsoft-copilot-studio/harnesses-overview

    So I would benchmark the same question with:
    Standard harness + one tightly scoped SharePoint source, then Standard harness + SharePoint files/folder indexed in Dataverse.

    If the minimal configuration still consistently takes 40–60 seconds, I would raise a Microsoft support case rather than continue restructuring the SharePoint site. At that point the latency is likely in the Copilot Studio/SharePoint retrieval pipeline rather than in the agent instructions or model selection.

  • Mohsin Ali Profile Picture
    467 on at
    Hello @Louisa# - In addition to detailed response from @Ulrich_Zogo, can you please tell me following two things.
     
    • Which orchestration you are using? Is it Generative or classic?
    • Have you tried disabling the Allow ungrounded responses and Use information from the web settings?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Mohsin Ali Profile Picture

Mohsin Ali 151

#2
Dua Sadiq Profile Picture

Dua Sadiq 125

#3
sannavajjala87 Profile Picture

sannavajjala87 93 Super User 2026 Season 2

Last 30 days Overall leaderboard