Introducing the plugin registry - one place to discover and govern plugins for Microsoft Copilot

Microsoft

Sep 30, 2026

On September 25, we introduced the new Microsoft Copilot to connect the tools people rely on with the next generation of capabilities they’ll need to build, customize and scale AI across work.

Agents in Copilot already help you work with your organization’s knowledge and automate business processes. Now, we’re giving you more ways to customize Copilot with plugins that contain skills, connectors, and agents, adding the data and actions you need to get work done.

To make these plugins easier to discover and manage, today we’re also announcing the Microsoft plugin registry, rolling out now. The plugin registry is a shared place to discover, publish, manage, and govern plugins across supported Microsoft Copilot experiences—Home (Chat and Cowork), Code, and Autopilot, Microsoft 365 apps (Word, Excel, and PowerPoint) and SharePoint. Your users can find organization-approved plugins through a consistent Plugins menu, while you manage access and oversight centrally. In the future, the plugin registry will support such experiences as Copilot Studio, GitHub Copilot, and Microsoft Foundry.

What is a plugin?

A plugin brings together the capabilities users need to get work done in Copilot in a package that is easy to discover, use, and manage. Users will discover enabled plugins through a consistent Plugins page across supported Copilot experiences. This Plugins page replaces and expands on the existing Agents page, providing continued access to all of your Agents, as well as Skills and Connectors, in one place. As an admin, you can approve, assign, and govern each plugin.

Plugins can include

Skills, which provide reusable instructions for specialized work
Connectors, which give Copilot approved access to services and data
Agents, which customize Copilot for specific uses

While the term “Plugins” is replacing “Agents” in the top-level UI of Copilot, Agents remain an important part of Copilot extensibility. With this change we are bringing them together with skills and connectors in a single package that users can discover and admins can manage. Developers and partners can also create plugins tailored to your organization’s systems and workflows. Learn more about the plugin registry.

Help your users complete more work

We’re introducing a more consistent way for your users to discover and use access approved plugins across supported Copilot experiences. As these updates roll out, users will be able to find the plugins you enabled through a Plugins menu in Home (Chat and Cowork), Code, Autopilot, and supported Microsoft 365 apps. Plugins can connect Copilot to approved business data and actions, helping users complete more workflows without leaving the experience where they’re working. These updates will make it easier to find and use enabled capabilities as users move across apps and Copilot experiences, reducing repeated discovery and setup and helping them stay in the flow of their work.

Control plugin access from one place

Give IT centralized control over which plugins users can access across supported Copilot experiences. Through the Agent 365 experience in the Microsoft 365 admin center, under Agents > Tools, admins can review Microsoft, custom-built, and partner plugins, enable or disable which plugins are available, block or assign them to users or groups. This makes it easier to expand what users can do with Copilot while keeping plugin access centrally managed. ¹

Managing plugins under Tools in Microsoft 365 admin center

Microsoft 365 admin center MCP management view

Help developers and partners scale

Central management gives you a consistent way to control access and updates over time. As your users, groups, and business requirements change, you can adjust assignments, review new versions, see where a plugin is in use, and decide when to expand, limit, or retire it. This helps you keep plugin access and versions aligned with your organization’s requirements without managing each underlying component separately.

Developers and partners can package related skills, connectors, and the metadata and configuration needed to connect to MCP servers and other enabled tools in one plugin. They can publish and update that package once for your review instead of maintaining separate deployment artifacts for each Copilot experience. You remain in control of approval and assignment, while developers and partners gain a clearer path to reach supported Copilot experiences as availability expands.

Find plugins for common business needs

More than 100 plugins are already available, with more being added. They support work across areas such as finance, sales, project management, creative work, IT service management, market research, and software development.

For example, plugins can connect Copilot to customer data in HubSpot; work-management systems such as Linear, Atlassian, and Asana; content platforms including Webflow, Canva, and Notion; databases such as MongoDB; and research services from IDC, NielsenIQ, and CAS. Browse the available plugins^2.

Build and publish custom plugins to the plugin registry using Work IQ Developer Tools (WIQD)

Use Work IQ Developer Tools (WIQD) to move through the end-to-end custom plugin lifecycle: build, preview, validate, package, and publish through the plugin registry. Import an existing agent plugin or start with the business outcome you want to achieve and create a new one. You can work through your preferred coding harness, including GitHub Copilot CLI, or use WIQD commands directly. Learn how to bring your plugin to Microsoft Copilot with WIQD here.

The plugin registry brings together the capabilities your users need and the controls your organization relies on. It makes enabled plugins easier to discover, access easier to manage, and solutions easier for developers and partners to publish across supported Copilot experiences. The result: more ways to get work done, with less complexity for users, admins, and builders.