Introduction
Knowledge sources ground a Microsoft Copilot Studio agent's answers in your organization's content, such as policy documents, business records, and the history kept in other systems. Adding a source is only the start. A useful answer comes from the right source, and that source has to be current.
Suppose you work on the IT team at a manufacturing company. Employees send the help desk the same kinds of questions every day: what a policy says, which laptop models they can order, and whether a known issue already has a fix. The answers exist, but they're spread across policy documents, purchasing records, and the support team's work-tracking history, and a different team keeps each one up to date. Your team asks you to build a help agent that employees can ask directly. For employees to trust it, each answer has to come from the current, approved version of that information, and you need a way to check that it does.
In this module, you explore:
- What each type of knowledge source provides and when it's a good fit.
- How to add a knowledge source, using an available Copilot connector as the example.
- How to test answers in Preview and diagnose the ones that miss.
- How to plan evaluations that recheck answers as your agent changes.
By the end of this module, you'll be able to choose the right knowledge source for each kind of question, add it to your agent, use Preview to confirm where each answer comes from, and plan evaluations to keep checking over time.