Extend Cowork with plugins and connectors
Some tasks need specialized instructions or access to systems such as a customer relationship management system, project tracker, or ticketing service. Plugins add those capabilities to Cowork.
What plugins add
A plugin is a package that adds capabilities to Copilot. In Cowork, a plugin can add skills, connectors, or both:
- Skills: new domain know-how, the same idea as the built-in and custom skills you've already seen, packaged as a plugin by a publisher or someone in your organization. A plugin might add specialized capabilities for financial analysis, legal research, or a particular line-of-business process.
- Connectors: links to an external data source or service, so Cowork can retrieve or act on information that lives outside Microsoft 365.
You browse what's available from Plugins (formerly Customize). You'll see plugins your organization has made available, and your admin might add some for you automatically.
Open any plugin to see what it provides. A plugin's detail page lists the skills and connectors it brings.
When you open a plugin's details, its connectors appear under a heading like MCP servers.
Note
MCP (Model Context Protocol) is an open standard many connectors use to link to an outside service.
How they fit into your work
When a plugin is enabled, its skills join Cowork's built-in ones. Cowork selects skills based on your request, and active skills appear in the side panel. Use the Sources & Skills panel to check connector status or turn a plugin on or off.
The first time you use a connector, you might need to sign in or grant consent to the service. This authorization can remain available across conversations until you or your admin revoke it. That's different from an Always allow action approval, which applies only to the current session.
Important
Review the service, requested permissions, and planned action before you authorize access. Some connector tools send a file you select to the connected service, and Cowork asks for approval before the tool runs. Check that the file is appropriate to share under your organization's policies.
For example, an approved connector can supply project-tracker information for your weekly report. Check that the connected account can access the intended project and review the retrieved information before you share the report.
When to involve IT
Because plugins can reach outside Microsoft 365, they sit within your organization's governance, so IT is often part of the picture:
- Some plugins need approval first. If a plugin you need is missing or marked as blocked, ask your admin to review it for your organization.
- Admins can deploy plugins for you. Plugins your admin deploys show up automatically, and you can't remove them, though you can still enable or disable them for your own sessions.
- You complete any required sign-in yourself. If an admin-deployed connector needs a service connection, an admin can't sign in on your behalf.
- If you need something that isn't there, ask. IT can review and approve a plugin your team needs, or work with a partner when a capability doesn't exist yet.
For steps to browse, enable, and connect plugins, see Use plugins with Copilot Cowork. To explore plugin capabilities and guidance on building, publishing, and managing plugins, see the Plugins hub.
Note
We recognize that different people like to learn in different ways. You can choose to complete this module in video-based format or you can read the content as text and images. The text contains greater detail than the videos, so in some cases you might want to refer to it as supplemental material to the video presentation.