Copilot Cowork plugins are the missing piece between Microsoft 365 Copilot and the rest of your business stack, and Microsoft just turned them on for Frontier tenants. If you are running the Frontier program, this is the rollout that decides whether Cowork becomes a real orchestration layer or just another chat surface.
In this post I walk you through what Copilot Cowork plugins are, what is shipping in Public Preview, who is affected, how to manage them, and where I think most admins will trip up. According to Microsoft, this should be rolling out in early May 2026.
What Are Copilot Cowork Plugins?
Copilot Cowork plugins are extensibility components that let Cowork securely access additional Microsoft and third-party services using a user’s existing permissions. A ‘plugin’ in this context can be a connector, a skill, or both. Microsoft is using the same model that already powers their wider Copilot extensibility story, so if you have looked at MCP-based agents before, the mental model carries over.
There are three flavours to know:
- Native Microsoft connectors, including Dynamics 365 and Microsoft Fabric (with Power BI). These can read, and where supported, write data.
- Partner plugins, with LSEG (London Stock Exchange Group), Miro, monday.com, and S&P Global Energy in the first wave, and more partners landing over the coming weeks.
- Custom plugins, which your developers can build to connect internal systems or workflows directly into Cowork.
The thing to understand is that Copilot Cowork plugins do not change your tenant security boundary. Existing Microsoft 365 permissions, Purview policies, and audit controls still apply. The plugin layer is an extension surface, not a bypass.
For a related governance pattern, my earlier walkthrough of federated Copilot connectors and the Microsoft 365 admin center experience(opens in new window) is the best primer if you have not seen the connector admin flow before, the management story for Cowork plugins is converging on the same shape.
Why Copilot Cowork Plugins Matter Right Now
Until now, Cowork was useful but bounded. You could chat, run skills, and lean on the M365 graph. Anything outside that meant a separate tool, a separate agent, or a custom Copilot Studio build. Copilot Cowork plugins close that gap inside the same experience users already have on web, desktop, iOS, and Android.
For organisations on Frontier, the practical impact is:
- One Copilot surface that can pull live data from Dynamics 365, Fabric, and Power BI without copy-paste.
- A predictable extensibility model for partners, instead of one-off integrations.
- A governed path for internal developers to surface line-of-business systems, without a separate agent platform.
What Is Shipping in Public Preview
Microsoft has announced the following for the May 2026 Public Preview of Copilot Cowork plugins:
- Native connectors for Dynamics 365 and Microsoft Fabric (including Power BI).
- Partner integrations with LSEG, Miro, monday.com, and S&P Global Energy, with more rolling out in the weeks following Preview.
- The ability for organisations to create custom plugins to connect Cowork to internal systems and workflows.
- Availability through the Microsoft 365 Copilot app on web, desktop, iOS, and Android for Frontier participants.
This is Frontier-only. If your tenant is not enrolled in the Microsoft 365 Copilot Frontier program, no action is required and the feature is not enabled by default.
Rollout Timeline
According to Microsoft, this should be rolling out in early May 2026.
| Phase | Audience | Start | Expected Complete |
|---|---|---|---|
| Public Preview | Frontier participants | Early May 2026 | Early May 2026 |
| General Availability | Not announced | TBD | TBD |
Microsoft has not announced a General Availability date. Treat this as a Frontier-only signal, not a ‘when will my regular tenant get it’ question.
Who Is Affected
- Tenants enrolled in the Microsoft 365 Copilot Frontier program.
- Users with access to Microsoft 365 Copilot Cowork inside those tenants.
- Admins responsible for plugin governance, security review, and licensing decisions.
If you are not in Frontier, you can stop here. If you are, keep reading, because the governance work happens before users start clicking.
How to Prepare for Copilot Cowork Plugins
This is the part most admins will skip and regret later. Here is the order I would work through.
Step 1: Decide who can build custom Copilot Cowork plugins
Custom plugins are the highest-trust object in this rollout, they execute against your tenant data with the user’s permissions. Decide upfront whether plugin development is open to all developers in the tenant, scoped to a specific Entra ID group, or restricted to IT only. Document it before the first plugin lands.
Step 2: Decide which partner plugins you are willing to enable
LSEG, Miro, monday.com, and S&P Global Energy are the first wave, with more coming. Treat each one as a third-party data agreement question, not a tick-box, the partner will receive query-time data via the user’s session.
Step 3: Align native connectors with existing data classification
The Dynamics 365 and Microsoft Fabric connectors can surface a lot of data fast. Pre-existing sensitivity labels, Purview DLP policies, and Power BI workspace permissions still apply, but the surface area changes. Walk through a few realistic prompts in a pilot group before opening it broadly.
Step 4: Brief the helpdesk
Cowork is about to start surfacing data from Dynamics, Fabric, and partner services based on the user’s existing access. The first ‘why does Copilot suddenly know about my CRM accounts’ ticket will arrive within a week of enablement. A two-paragraph internal note prevents that.
For the broader extensibility pattern Cowork is built on, the Microsoft 365 Copilot interactive UI widgets admin guide(opens in new window) is worth reading alongside this post, the MCP and admin governance story is the same skeleton.
Admin Tips for Copilot Cowork Plugins
A few practical tips from the Frontier work I am doing right now:
- Do not enable everything on day one. Stage by Entra ID group. Pilot, observe, expand. The temptation in Preview is to flip every switch, this is the rollout where that backfires loudest.
- Review partner data flows before enabling. A partner plugin executing on behalf of a user is, in effect, a query-time data flow to that partner. Get your privacy and procurement teams aligned, especially in the EU where data boundary expectations apply.
- Treat custom plugins like apps, not scripts. Versioning, owner, review, sunset policy. If a plugin has no owner in 6 months, it should not be running.
- Watch for plugin sprawl. The same way SharePoint sites multiplied without governance ten years ago, plugins will. Set the policy now.
License Considerations for Copilot Cowork Plugins
Copilot Cowork plugins require participation in the Microsoft 365 Copilot Frontier program. This is not part of the standard Microsoft 365 Copilot SKU, and the feature is not enabled by default for non-Frontier tenants. If you do not know whether your organisation is enrolled, check with your account team before assuming you have access.
The underlying Cowork experience requires a Microsoft 365 Copilot license on a qualifying Microsoft 365 base plan. The plugin layer does not change those licensing prerequisites.
The Paul-Take
This is the rollout that turns Cowork from ‘a chat experience’ into ‘an orchestration layer’. That is a much bigger deal than the partner names in the press blog.
Three things matter, in this order.
First, the plugin model is the strategic move, not the partner list. Microsoft is signalling that MCP-style extensibility is how Copilot will reach your business systems, full stop. If you are still building one-off Copilot Studio agents for internal data, expect that strategy to feel dated within a few quarters.
Second, the governance work is the real project here. The list of partners and connectors will keep growing. The plugin allowlist, custom plugin policy, and review process are what determine whether this gets out of hand. Frontier tenants that put governance in place during Preview will glide into General Availability. Tenants that do not will spend Q3 doing cleanup.
Third, the EU question is real. Partner plugins execute query-time data flows to third parties. If you are an EU-regulated organisation, the discussion to have right now is which partner plugins are acceptable under your existing agreements, not after the first audit finding.
Community Question
Are you opening Copilot Cowork plugins to your full Frontier user base on day one, or staging by Entra ID group and use case? I am seeing both approaches with KbWorks customers and I am genuinely curious which way the majority is leaning.
MVP Reference List
- Microsoft Tech Community blog: (Co)work in Progress(opens in new window)
- Microsoft Learn: Build plugins for Copilot Cowork (Frontier)(opens in new window)
- Microsoft Learn: Manage plugins for Copilot Cowork (Frontier)(opens in new window)
- Microsoft Learn: Use plugins with Copilot Cowork (Frontier)(opens in new window)
- Microsoft Adoption: Frontier program