What is a Microsoft 365 Copilot plugin?

A plugin is an installable package that adds new capabilities to Microsoft 365 Copilot and other Microsoft AI experiences. It brings together the skills, tools, and optional agents needed for a job in one unit that people can find, install, share, and manage.

For example, a support plugin might use an agent to answer questions, a skill to guide troubleshooting, a connector to find support content, and an MCP server to provide tools.

A plugin can contain one capability or several; a single packaged skill is also a plugin. External services, such as remote MCP servers, can run separately from the package.

Before building a new plugin, browse the Copilot Plugin Catalog, a public registry of available plugins.

What can a plugin include?

Choose what your plugin needs based on the task it should help users complete.

Capability What it does Learn more
Skills Provide reusable instructions for a task, packaged in a directory that contains SKILL.md. Skills in declarative agents
Tools Connect to apps and data, including supported Copilot connectors and remote MCP integrations. Copilot connectors and MCP servers
Agents Provide specialized assistants for a role or workflow; today, these are declarative agents. Declarative agents overview

A plugin doesn't need all three capability types. You can create new capabilities or reuse existing ones.

Support varies by product. Check the guidance for Agent Builder, Copilot Studio, and Copilot Cowork for the experience you're targeting before you build or package your plugin.

Plugins and declarative agent actions

A Microsoft 365 Copilot plugin is an installable package. An API plugin or MCP plugin is an integration that provides actions to a declarative agent. When a plugin package includes that agent, its API and MCP actions remain available through the agent; they don't become independently available capabilities of the package. The API or MCP server runs separately.

The manifests describe different levels of the solution:

Manifest What it describes
Microsoft 365 app manifest, manifest.json The installable package's identity, metadata, and supported capabilities.
Declarative agent manifest The agent's instructions, knowledge, and actions. Its actions entries reference or inline API or MCP plugin manifests.
API or MCP plugin manifest, such as ai-plugin.json An agent action integration, including the API or MCP server connection and applicable function, tool, and authentication configuration. It isn't the app manifest.

Use MCP and API plugins for declarative agents to add actions to an agent. To connect a remote MCP server at the package level instead, use remote MCP configuration in the app manifest. That route uses agentConnectors, not an agent's API or MCP plugin manifest. Choose the route supported by your target experience.

Plugin journey

  1. Prepare: Define the outcome, intended users, target products, and requirements for your plugin.
  2. Build or reuse: Choose and integrate the capabilities you need, then test how they work together.
  3. Package & test: Package your plugin, then test and validate it for your intended publishing route.
  4. Publish & distribute: Share or publish the tested plugin through a supported route for your audience.
  5. Make available & govern: Complete any required admin review, installation, user availability, and access configuration.
  6. Monitor, update & retire: Review performance, support users, release updates, and retire your plugin when it's no longer needed.
  7. Discover & use: Browse available plugins in the Copilot Plugin Catalog. Help users find and use your plugin in their target product; for Cowork, see Use plugins with Copilot Cowork.

After you publish or share your plugin, users might still need approval, installation, or connection setup before they can use it. The steps depend on how you shared it and your organization's settings.

Key terms

Term Meaning
Copilot Plugin Catalog A public registry for discovering available plugins.
Plugin registry A destination for plugins published or shared with a selected audience.
Tools Registry The view under Agents > Tools > Registry in the Microsoft 365 admin center for plugins, skills, MCP servers, and connector visibility.
Agent Registry The view under Agents > All agents > Registry for agent-specific controls; a packaged agent can also have an Agent Registry record.
Microsoft Marketplace A publishing route for reaching customers across organizations.

Public discovery, publishing, and tenant administration are separate. A listing in the Copilot Plugin Catalog doesn't establish organizational approval or availability. Tools Registry, Agent Registry, and Microsoft Marketplace aren't interchangeable names for one catalog.

Next step