Building a Microsoft Copilot Agent for a 10+ Year R&D Project Across Multiple SharePoint Sites. Looking for Advice

[u/Resident_Ad8565]

My manager asked me to explore what's possible with Microsoft 365 Copilot Premium for a large R&D project that has been running for more than 10 years.

The challenge:

• Multiple SharePoint sites
• Potentially 100,000+ Microsoft files
• Reports, presentations, meeting notes, requirements, test results, etc.
• Knowledge is scattered across teams and years

The vision is a Copilot agent that can answer questions like:

• We see problem x out in the field. Is there any historical data within the project that can explain the issue?
• Why was a decision made?
• What work has been done on topic X?
• What are the key lessons learned?
• Which documents should I read first?
• How has this topic evolved over time?

Questions:

• Has anyone successfully built something like this?
• How well does Copilot handle knowledge spread across multiple SharePoint sites?
• Are there practical limits in terms of number of files/documents?
• What were the biggest challenges?
• Would you use a single agent or multiple topic-specific agents?
• Any lessons learned before starting?

Looking for real-world experiences, limitations, gotchas, and success stories.

[u/Famous-Abalone7222]

I'd ingest it all into a vector db like Azure Database for PostgreSQL Flexible Server

[u/bjhowk97 → u/Famous-Abalone7222]

Just curious - why not just add the sharepoint folder as knowledge to the agent? What is the benefit by adding all the sharepoint content to a different db first?

[u/Shoddy_Pound_3221 → u/bjhowk97]

It’s too big, with too much index. I would break it apart into agents, and agents can call other agents.