Build a market research assistant agent

Step 1: Connect internal and external sourcesSharePoint

In Copilot Studio's Knowledge settings, add the SharePoint libraries holding internal market research, purchased analyst reports, and win/loss notes, plus a web-search connector if your license supports grounding on external sources.

The whole value of this agent is synthesizing across both, so an agent scoped to only one side is just a search box with extra steps.

Step 2: Ask it a real planning questionCopilot Studio

Test it with the kind of question that actually comes up in planning cycles, not a generic "tell me about the market" prompt.

Prompt idea:

What's the current competitive landscape in mid-market ERP, and how has it shifted in the last two quarters? Pull from our internal win/loss notes and any analyst reports in the library.

Step 3: Check that internal and external findings actually reconcileCopilot Studio

When internal win/loss notes paint a different picture than an external analyst report, ask the agent directly which sources support each view — a response that quietly favors one source without flagging the disagreement is hiding a decision-relevant signal rather than resolving it.

Step 4: Use it as a standing resource, not a one-offSharePoint

The real value shows up when planning teams can query it repeatedly through a cycle instead of commissioning a fresh report each time.

Check the work

• Check that internal and external sources are both actually being drawn from, not just one.
• Flag and investigate any place internal and external data disagree, rather than letting the agent silently pick one.
• Confirm the sources feeding the agent are being refreshed, not going stale.

Source: Microsoft Copilot Scenario Library — Marketing (2026)