Add a knowledge source
After you choose a knowledge source, you make it available to your agent so the agent can use it in its answers. In this unit, you learn how to add a source, using a Copilot connector as the example, and how to name and describe it so the agent knows when to use it.
Confirm that the connector is available
A Copilot connector brings data from another service into Microsoft 365. Copilot connectors come in two types. A synced connector indexes the content into Microsoft Graph, and an admin usually sets up and manages its connection in the Microsoft 365 admin center. A federated connector fetches data in real time instead of indexing it. For both types, the connector setup happens outside your agent.
In your agent's Add knowledge dialog, connector-based suggestions appear only when the required connectors are installed and consented to in your environment. If a connector you expect doesn't appear, ask your admin to confirm that it's available. Don't substitute a tool or a similar entry, such as Custom Connector on the Advanced tab, unless you confirm that it provides the same content.
Azure DevOps Work Items is a Copilot connector on the Advanced tab. It lets the agent reference work items, bugs, and backlog content. For example, if your support team tracks issues in Azure DevOps, this connector is the source you add for questions about known-issue fixes.
In agents powered by the GitHub Copilot harness, Copilot connector knowledge uses data indexed for Microsoft 365 Copilot. Before you plan around a connector, confirm with your admin which type it is.
Learn more in Copilot connectors overview.
Add a source from the Build tab
The following steps show the common path, which is the same for every source type until you pick one:
- Open your agent in Copilot Studio.
- In the agent navigation bar, select the Build tab.
- In the components panel on the right, select the Knowledge button.
- In the Add knowledge dialog, choose a source. You can drag and drop files or select the upload area, search for a source in the search box, or select a source type on the Featured tab. For more types, such as Azure DevOps Work Items or Custom Connector, switch to the Advanced tab.
- Follow the configuration steps for the source type you selected.
- Select Save or Add to confirm the knowledge source.
For the Azure DevOps example, in step 4 you search by name or switch to the Advanced tab, and then select Azure DevOps Work Items. Step 5 is where source types differ. Follow the prompts in the dialog, and ask your admin about any setting you're unsure of.
The dialog can also suggest sources. Treat a suggestion as a candidate. Before you add it, confirm that it contains the content your agent should reference.
Learn more in Add knowledge sources to an agent.
Name and describe the source
After you add a source, update its name and description. The runtime decides for each question which sources to search, and the description helps it choose. State what the source holds and which questions it answers.
For example, the name and description for the Azure DevOps connector might look like this:
- Name: Known issue resolution history
- Description: Factual records of known issues from the work-tracking service, including bugs, work items, and the steps that resolved each issue. Use this source for questions about how a known issue was resolved or whether a workaround exists.
Compare that description with a vague one, such as Azure DevOps data, which names the system but not the questions it answers. A descriptive name also helps you find the source quickly.
Your agent's sources appear as chips in the Knowledge section of the Build tab, each showing the source name. To review or change a source, select its chip, change the configuration in the details pane, and select Save. To remove a source, select × on its chip and confirm. Removing a source from the agent doesn't delete the original content in Azure DevOps.
Reflect: Pick one source your agent uses or plans to use. Which questions should send the agent to that source, and which similar questions belong to a different source?
Learn more in Manage knowledge sources in an agent.
An added source is a starting point. Testing in Preview shows whether the agent uses it the way you expect.