Copilot Cowork + Plugins: Where the Real Value Hides

If you’ve only watched the launch demo of Copilot Cowork, you’ve seen maybe a third of the story. The flashy part — Copilot taking action instead of just chatting, running tasks in the background, asking for approvals — that’s the headline. But the actual game-changer is the plugin layer. And almost no one is talking about it yet.

Let me walk you through why I think this is the most important Microsoft 365 release of the year, and what it actually means once you turn on plugins.

What Cowork Is (the short version)

Microsoft announced Copilot Cowork on March 9, 2026, and it became broadly available through the Frontier program at the end of March. The pitch is simple: instead of asking Copilot a question and getting a single artifact back, you describe an outcome. Cowork builds a plan, executes it across Microsoft 365, and checks in for your approval at each step.

It’s powered by a combination of Anthropic’s Claude models (the same agentic technology behind Claude Cowork) and Microsoft’s Work IQ — the intelligence layer that grounds responses in your emails, meetings, files, and chats. Available in the browser, on the desktop apps for Windows and Mac, and on iOS and Android.

Out of the box, Cowork ships with thirteen built-in skills: Word, Excel, PowerPoint, PDF, Email, Scheduling, Calendar Management, Meetings, Daily Briefing, Enterprise Search, Communications, Deep Research, and Adaptive Cards. That’s already enough to delegate a meaningful chunk of typical knowledge work.

But here’s where most coverage stops. And here’s where the actual story starts.

The Plugin Layer

A Cowork plugin is a packaged extension distributed through the Microsoft 365 App Store. It can contain skills (prompt-based workflows that teach Cowork new domain expertise) and connectors (links to external data sources and APIs). A single plugin can carry up to twenty skills and ten connectors.

That sounds like classic Microsoft extensibility plumbing. It isn’t. The reason this matters is that plugins solve the one problem agentic AI has had since day one: it can only act on what it can reach.

A built-in Cowork can draft you an email. A plugin-equipped Cowork can pull live order data from your ERP, cross-reference it with the pipeline state in your CRM, build a dashboard from Fabric, and then draft you an email. Same prompt. Different category of output.

Native Plugins You Get From Microsoft

Microsoft ships four native plugins out of the gate, and three of them should make every Dynamics consultant pay attention:

Dynamics 365 ERP — Cowork can interact with your ERP environment for scenarios like order approvals, inspection of open invoices, and operational data lookups. For anyone in the Business Central world: yes, this is the door we’ve been waiting for.

Dynamics 365 Sales — Pipeline reviews, opportunity inspection, account-level summaries. Cowork can pull pipeline data and combine it with email and meeting context for a complete account view.

Dynamics 365 Customer Service — Case resolution support, including pulling case history, related cases, and KB articles into a single working context.

Fabric IQ — Live Power BI data flows directly into Cowork workflows. Generate reports, run data-driven reviews, and ground your output in actual numbers rather than approximations.

Partner plugins are rolling in week by week — LSEG, Miro, monday.com, S&P Global Energy, Adobe, Atlassian, Box, Enosix, Harvey.AI, Money Forward, Morningstar, Swoop by Prezi. Most of them targeting specific industry verticals.

Custom Plugins: Your Domain Knowledge as Code

This is the part that makes me genuinely excited. Organizations can build their own plugins using the standard M365 app package format — the same one used for Teams apps, Copilot agents, and Office add-ins. Skills are written in Markdown using the Agent Skills open standard, which is the same format Claude Code, VS Code Copilot, Gemini CLI, Cursor, and JetBrains Junie support.

That means a skill you write for one tool can — with minor adaptation — work in others. Microsoft even ships a conversion script that takes a Claude Code plugin and produces a valid Cowork package.

Here’s what this looks like in practice. You write a SKILL.md file describing how your organization handles, say, monthly project reporting: what data to pull, what tone to use, what format the output should follow. You package it with a connector to your project management system. You publish it to your tenant. From that moment on, every employee with Cowork access can run the skill, and the output is consistent with how your organization wants the work done.

That’s not a chatbot anymore. That’s institutional knowledge becoming executable.

The Scenario Where It All Clicks

Let me make this concrete. Last week I mapped out a scenario most BC consultants will recognize: prepping for a quarterly business review with a strategic customer.

The traditional flow: someone on the account team spends half a day pulling data. They check Outlook for relevant correspondence. Open Teams for the running account discussion. Dig through SharePoint for the latest contract and MSA. Pull order volume from BC. Check the open pipeline in Sales. Build a deck. Write a briefing doc. Coordinate with the technical lead.

Now picture this with Cowork plus the Dynamics 365 ERP plugin, the Dynamics 365 Sales plugin, and the Fabric IQ plugin enabled:

“Prepare a QBR briefing for the [customer] meeting on Thursday. Pull the last six months of customer correspondence, summarize the key themes from our internal Teams discussion, check open orders and invoice status in ERP, get the current pipeline state, include the revenue trend from Fabric, and build a briefing doc plus a 10-slide deck.”

One prompt. Six sources. The plan runs in the background. Cowork checks in when it needs clarification. You approve the actions you want approved. Forty minutes later, the doc and the deck are sitting in your OneDrive.

That’s not “AI saved me 20 minutes.” That’s a structurally different way of doing business reviews.

The Catch

Cowork is currently Frontier-only, which means you need a Microsoft 365 E5 license plus Frontier program enrollment. The E7 Frontier Suite goes generally available in May 2026. Plugins are governed at the tenant level — your IT admin controls what’s installed, blocked, or available to specific groups. And custom plugins still need someone who builds them, which means the real value lands fastest at organizations willing to invest in the plugin layer rather than just consume the built-in features.

Also worth saying: this is a v1 enterprise product. Documentation is still catching up. Edge cases exist. Real adoption requires real change management, not just a license assignment.

Why This Is Bigger Than a Feature Release

I’ve been through enough Microsoft launches to be allergic to “this changes everything” rhetoric. So I won’t say that. What I will say is this: the plugin architecture in Cowork is the first time I’ve seen agentic AI in the enterprise stack with a credible answer to the silo problem.

Most AI tools either live inside a single app or operate as a generic assistant that can’t reach into your business systems. Cowork plus plugins crosses both barriers. It’s embedded in M365, governed by your tenant, and able to reach into Dynamics, Power BI, and any third-party system someone builds a plugin for.

For Microsoft partners — and especially those of us in the Business Central and Dynamics ecosystem — this is the moment to start thinking about which custom plugins your customers actually need. Because the demos are nice, but the value lives in the plugin layer.

If you wait until everyone else has figured this out, you’re late.

Give it a try. Build a plugin. See what your team can delegate that they couldn’t last quarter.

---