Notitie
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen u aan te melden of de directory te wijzigen.
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen de mappen te wijzigen.
Start by deciding where people will use the experience:
- Inside Microsoft 365 Copilot experiences. Build or configure supported agents, connectors, skills, and tools, and then follow the package, distribution, and governance guidance for the selected route.
- In your apps and custom agents. Use APIs and SDKs to add Microsoft 365 work context and Copilot capabilities to experiences that you own and operate.
You can use both approaches in one solution. Choose the primary path based on the user experience, runtime, distribution model, and operating responsibilities.
Choose where the experience lives
| Where people use the experience | Start with | Use it when |
|---|---|---|
| Inside Microsoft 365 Copilot experiences | Plugins for Microsoft 365 Copilot | You want to build or configure a plugin with supported agents, skills, connectors, or MCP-based tools |
| In your apps and custom agents | Build Copilot-powered apps and agents | You want to use Microsoft 365 work context or Copilot capabilities in an experience that you host and operate |
Choose by what you want to create
| If you want to | Start with |
|---|---|
| Build a declarative agent that uses Copilot's orchestrator and models | Declarative agents |
| Add reusable instructions or workflows to a declarative agent | Skills as plugin capabilities |
| Ground Microsoft 365 Copilot in approved external organizational data | Microsoft 365 Copilot connectors |
| Make remote MCP tools available through a supported route | MCP servers and plugins |
| Maintain or evaluate a Teams message extension integration | Message extensions |
| Build and distribute a plugin that brings supported capabilities together | Plugins for Microsoft 365 Copilot |
| Build an application that uses Microsoft 365 work context | Work IQ APIs |
| Add Copilot search, retrieval, chat, export, meeting, reporting, or administration capabilities to an application | Microsoft 365 Copilot APIs |
| Build an agent with your own orchestration, models, hosting, or runtime | Custom engine agents |
For help comparing declarative and custom engine agents, see Compare declarative and custom engine agents.
Combine both paths
A solution can combine multiple paths. For example:
- A declarative agent can call an external API or remote MCP server through a supported action.
- An application can use a Copilot API while a separately packaged agent gives users a related experience inside Microsoft 365 Copilot.
- A custom engine agent can use Work IQ APIs and also follow the package or distribution requirements of its target channel.
Using an API doesn't by itself select a package or distribution route. Each part of a combined solution retains its own identity, authentication, deployment, distribution, and governance requirements.
Plan and continue
- Plan your plugin across data, identity, security, distribution, compatibility, cost, and ownership.
- For builders, choose a development experience and implementation guidance.
- For administrators, prepare the organization and identify applicable controls.
- For ISVs and software publishers, determine the supported customer distribution route.