Agent Builder adds Copilot connector knowledge

Key insights

• The demo distinguishes website knowledge from synced Copilot connector data.
• Administrators deploy connectors through the Microsoft 365 admin center.
• Rollout audiences affect which users can access a connector.
• An agent can use connector content indexed in Microsoft Graph as a knowledge source.

Microsoft published a 13-minute demonstration of extending Agent Builder with Copilot connectors. The video, presented by David Warner, is identified as a demo from a Microsoft 365 and Power Platform community call held on August 20; the description does not specify the year. Its main point is that a connector can make indexed external knowledge available to an agent, but administrators first control deployment and audience access.

What's new

The demonstration focuses on adding Copilot connector data as a knowledge source in Agent Builder. Microsoft’s description says the agent can answer using indexed content in Microsoft Graph, which provides a route to information from external or third-party sources rather than relying only on website knowledge.

The video calls out a distinction between website knowledge and synced connectors. These are presented as different ways to provide an agent with information: website knowledge is the web-based option shown in the updated Agent Builder experience, while connector content is synchronized and indexed before the agent uses it. The description does not provide technical details about synchronization timing, supported data types, or how often content refreshes.

This is a knowledge-source capability, not evidence that an agent can take actions in the external system. The material describes answering from indexed content; it does not demonstrate writing records, changing tickets, or executing transactions. That distinction matters when deciding whether Agent Builder covers a use case or whether a separate action or workflow design is needed.

Why it matters

For makers, connectors offer a way to ground an agent in business information that is not presented as website knowledge. The demonstrated pattern is relevant when users need an agent to draw on an external source, such as a connected business system, while asking questions in an agent experience.

For administrators, connector deployment is part of the setup rather than a step an individual agent maker can assume is already complete. The video specifically shows deployment in the Microsoft 365 admin center and explains that rollout audiences affect connector availability. In practice, that means an agent maker may not see a connector if it has not been deployed or made available to that audience.

For end users, the intended change is access to responses grounded in indexed external content. The description does not claim that every user, tenant, or license has access, and it gives no licensing details. Organizations should therefore confirm their own connector configuration and access requirements instead of treating the demo as a universal availability statement.

How it works

The sequence shown in the description can be summarized as an administrative setup followed by agent configuration. Connector content is indexed into Microsoft Graph, then selected for use by an agent as a knowledge source. The video’s description highlights these steps:

1. An administrator deploys the Copilot connector in the Microsoft 365 admin center.
2. The administrator’s rollout audience settings determine which users can access it.
3. An agent maker adds the available connector as a knowledge source in Agent Builder.
4. The agent can then answer using relevant content indexed in Microsoft Graph.

That flow separates organization-wide connector availability from the configuration of an individual agent. Deployment makes a connector available to the relevant audience; selecting it for an agent associates its indexed knowledge with that agent’s answers. Microsoft’s documentation provides further context on Copilot connectors, connectors and Copilot Search, and deployment in the Microsoft 365 admin center.

Limitations and open questions

The video description is a summary, not a full transcript, so it does not establish every configuration step or explain connector behavior in detail. It does not name the specific connector demonstrated, state how long indexing takes, or describe how source permissions are enforced. Those details should not be inferred from the fact that content is indexed in Microsoft Graph.

Licensing, rollout status, and broad availability are also not specified in the supplied video material. The description says rollout audiences affect availability, but it does not say which audiences, regions, or license plans are supported. Administrators should check the relevant tenant documentation and their own configuration before planning a deployment.

Finally, the demonstration is about using connector content as knowledge. It does not show whether an agent can update the connected source or perform actions against it. Treat the capability shown as information retrieval for answers, and verify separately what additional tools or workflows are required for transactional scenarios.

Sources

• Microsoft’s Agent Builder and Copilot connectors demonstration
• Microsoft 365 Copilot connectors overview
• Microsoft documentation on connectors and Copilot Search
• Microsoft documentation on connector deployment

Frequently asked questions

What do Copilot connectors add to Agent Builder?

They let an agent use external or third-party knowledge that has been indexed in Microsoft Graph. The video describes the data as a knowledge source for answering questions.

Who makes a connector available to agent makers?

An administrator deploys connectors through the Microsoft 365 admin center. The rollout audience affects who can access a connector.

Can an agent update the external system through a connector?

The material shows an agent answering from indexed content, not changing records or carrying out transactions. It does not establish that connector access enables actions.

Does the video specify licensing or general availability?

No. It mentions audience-based rollout but provides no licensing details or claim of availability for all tenants.