Microsoft Copilot Studio

Native integrations

Copilot Studio uses Power Platform connectors as tools. Standard connectors such as SharePoint are included in every plan, premium connectors need select plans, and custom connectors reach any public API. You can call connectors as tools in an agent or inside a topic, and use them as knowledge sources. An idea: connect SharePoint as knowledge and a ticketing connector as a tool, so an agent answers policy questions and opens a ticket when it cannot.

API and webhooks

Microsoft documents several ways to bring agents into your own apps, including the Microsoft 365 Agents SDK, Direct Line and the Power Platform API. Use them when you want the agent inside your own web or native app instead of Teams. An idea: embed an agent in a customer portal and pass the signed-in user so it can answer from their data.

MCP server

Copilot Studio is an MCP client, not an MCP server. Microsoft documents no MCP server of its own for it, but it supports the other direction: your agents can connect to existing MCP servers as tools, through an onboarding wizard with no authentication, an API key or OAuth 2.0. It supports the Streamable transport, and SSE is no longer supported. An idea: connect an agent to your own internal MCP server so it can read from a system that has no connector.