Ever wished your ERP system could just… handle things? Like, actually understand what you need and go do it, instead of you clicking through fifteen screens in Dynamics 365? That’s basically the promise behind Copilot Cowork paired with the D365 ERP Apps plugin, and honestly, it’s one of the more interesting shifts happening in the Microsoft ecosystem right now. Let’s break down what this thing actually is, how it works, and why it matters if you’re anywhere near Dynamics 365 or Business Central.
What Exactly Is Copilot Cowork?
Think of Copilot Cowork as your personal digital coworker — one that doesn’t need coffee breaks or a standing desk. It’s a productivity-focused agentic system built right inside Microsoft 365 Copilot that plans, executes, and actually delivers finished work rather than just answering questions. You can access it at aka.ms/Cowork, assuming your admin has flipped the switch on.
What separates Cowork from your average chatbot is its multi-model architecture. It’s not locked into one AI brain — it pulls from several frontier models across different AI labs, picking whichever one fits the task best. That’s a pretty big deal because different models excel at different things, and Cowork essentially gets to pick its best player for each job.
How Does Copilot Cowork Actually Work?
Here’s where it gets interesting. Cowork operates on a four-stage loop: Intent, Plan, Execute, and Checkpoint.
You describe the outcome you want — say, “create this quotation, mark prices up 10%, generate a PDF, and email it to the client with a note about their overdue balance.” Cowork then breaks that down into visible steps you can actually watch unfold, like fetching customer data or pulling transaction history. From there, it executes across Microsoft 365 apps, checking emails, pulling records, doing the legwork.
But — and this is the part I really appreciate — it doesn’t just barrel ahead and start emailing your clients or writing data without asking. For anything consequential, it stops and asks for your approval first. So if it’s about to apply a price to a purchase order line, it’ll show you the options and let you decide rather than guessing.
Why Pair Cowork With Dynamics 365 ERP?
On its own, Cowork is great at organizing your inbox or prepping for a meeting. But ERP work is a different beast — it involves multi-step processes, cross-referenced data, and real business consequences if something goes wrong. That’s exactly the gap the D365 ERP Apps plugin fills.
Think of Agentic ERP AI along a spectrum: interactive tasks (answering questions, assisting with analysis), outcome-delegated tasks (longer-running work handed to AI with a human checking in), and fully autonomous processes (running at organizational scale on a regular cadence). The plugin lets Cowork tap directly into Dynamics 365’s business logic, data, and actions, riding on top of MCP (Model Context Protocol) and Work IQ.
The Architecture Behind the Scenes
If you’re the type who likes to understand what’s under the hood, the architecture is worth a look. At the center sits the Cowork Agent Runtime, handling orchestration, planning, context management, and multi-step workflows. This runs inside a Secure Execution Sandbox — isolated task containers with zero-trust execution, supporting built-in, personal, team, and organizational skills.
Wrapped around that is enterprise-grade security: Entra ID, Purview, DLP, and compliance controls, because nobody wants an AI agent running loose with sensitive financial data.
On the connectivity side, Cowork taps into Work IQ (which understands people, org charts, expertise, and context), plus a whole suite of Microsoft services — Outlook, Teams, SharePoint, OneDrive, Fabric IQ, and of course Dynamics 365 for CRM and ERP intelligence. It’s all powered by foundation models pulling from multiple AI labs, giving it flexibility depending on task complexity.
When Should You Actually Use Cowork for ERP Tasks?
Not every task deserves an AI agent. Honestly, using Cowork for something simple is like calling a moving truck to bring home a single grocery bag. There’s a decent framework worth following here:
First, ask who’s running the task and whether they already have Dynamics 365 access to complete it themselves. Cowork operates in the user’s context, so permissions still matter.
Second, check whether the task is already covered by an existing M365 or D365 feature. Need variance analysis? The Finance Solution inside M365 Copilot might already do that. Need a report from public sources? Researcher in M365 Copilot has you covered.
Third — and this is the real sweet spot — look for multi-step processes that go beyond simple data retrieval. Anything that pulls from multiple sources (D365, Work IQ, third-party plugins) and produces a real artifact, like a presentation, email, or system record, is exactly where Cowork earns its keep.
Setting Up Copilot Cowork: The Tenant Admin Steps
Getting this running isn’t a five-second toggle — it involves a few different roles working through separate steps. Let’s walk through it.
Step 1: Allow Dataverse Data
A tenant admin heads into the Microsoft 365 Admin Center, goes to Copilot, then Settings, and toggles on “Dataverse data available in Microsoft 365 Copilot.” This lets Copilot ground its answers in your actual business data rather than guessing.
Step 2: Deploy Cowork Tenant-Wide
Still in the admin center, under Agents > All Agents, the admin searches for “Copilot Cowork” and clicks Install. It shows as available and deploys across the whole tenant — a one-time action that benefits the entire organization.
Setting Up the ERP Connection: The F&O Admin Step
Step 3: Allow the MCP Server
This one falls to the Finance and Operations admin. In Dynamics 365 F&O, under Feature Management > Allowed MCP Clients, the admin needs to explicitly allow the client ID for Copilot Cowork to connect to the D365 ERP Model Context Protocol server. Good news: this is enabled by default for easier setup, though admins retain the option to disable it if they want tighter control.
Business User Setup: Getting Cowork Ready to Work
Step 4: Add Cowork Through the Agent Store
Now it’s the business user’s turn. They search “Cowork” inside Microsoft 365 Copilot’s Agent Store, or just go straight to aka.ms/Cowork, and click Add. Note that it currently shows up under the “Frontier” program — Microsoft’s early-access track for experimental Copilot innovations, meaning features and availability can still shift around.
Step 5: Enable and Connect the ERP Plugin
Inside Cowork’s settings, the user enables the “Dynamics 365 ERP apps” plugin and picks which environment they want it to work against. This is the moment where Cowork actually gets tied to your specific Dynamics 365 instance rather than operating in a vacuum.
Step 6: Give It Time to Provision
Here’s a small but important detail — connections don’t happen instantly. Give it five to ten minutes for the plugin to fully provision. After that, you can start prompting Cowork with real ERP questions, like asking who the vendor is for a specific purchase order, and it’ll pull that straight from F&O.
Real-World Impact: The Customer Pilot Numbers
Numbers talk, right? In one real operational scenario, Cowork was tested combining supplier bids, ERP data, and work context, then applying an approved scorecard to recommend a supplier award — following a Gather, Score, Recommend, Approve pattern.
The result: roughly 16 hours of potential capacity released per RFQ. That’s not a small thing if you’re running procurement at any scale. Worth noting though, this is described as a defined value target from a real customer pilot rather than a fully customer-attested result — the evaluation and recommendation pieces are promising, but measured savings are still being validated. Fair enough; that’s how good pilots should be reported.
Skills vs. Prompts: Knowing the Difference
This distinction trips a lot of people up, so let’s clear it up. A prompt delegates one task. A skill standardizes how an entire class of tasks gets performed, every single time.
If you’re doing one-off or exploratory work where the workflow can vary and governance doesn’t matter much, a prompt is fine. Something like “Evaluate RFQ 000012 using these bids and summarize the best vendor” works perfectly as a single prompt.
But if multiple users need the same method, the same controls, and the same output shape repeatedly, that’s a skill’s job. A reusable RFQ skill would apply standard scoring, evidence checks, an approval gate, and a consistent recommendation format every time it runs — no matter who triggers it.
The decision test is simple: will multiple users need the same method, controls, and output again? If yes, build a skill.
What Makes Up a Good Skill?
A skill isn’t just a fancy prompt saved somewhere. It’s a small, versioned operating contract covering six things: the Trigger (what request pattern activates it), the Job (one business outcome owned by a role or team), the Manifest (name, description, inputs, steps, outputs, stop rules), the Tools it can use (ERP MCP tools, Work IQ for mail/files/calendar), the Contract (a stable output shape — tables, exceptions, approvals, citations), and Controls (human approval before F&O gets written to, and a fail-closed approach when things are ambiguous).
Designing Skills That Don’t Burn Through Resources
Here’s something people overlook — good skills are engineered to spend less reasoning power on every run. It’s like the difference between someone who methodically checks a to-do list versus someone who re-thinks their entire day from scratch every hour.
The framework here has five parts: Scope (retrieve only the required F&O entities, fields, companies, and records — don’t go fishing), Reduce (avoid broad searches, reuse context already gathered in that turn), Route (use deterministic code or ERP business logic for calculations rather than making the model reason through math), Stop (clearly define conditions like missing customer/item/company/currency or ambiguous matches so the skill knows when to halt), and Measure (track tool calls, latency, retries, user corrections, and credit consumption).
That last point brings us neatly to costs.
Understanding Microsoft 365 Copilot Pricing for Cowork
Microsoft splits Copilot usage into two buckets: per-seat and usage-based. Chat, Copilot in Office apps and Teams, pre-built agents like Researcher, Work IQ, and multi-model access all fall under the per-seat model — you pay for the seat, you get the usage. Cowork sits differently, though; while access comes through the per-seat license, actually running Cowork consumes Copilot Credits, which is a usage-based billing mechanism.
What Drives Copilot Credit Consumption?
Four inputs calculate the price of each task: Models (which AI model handles the task, varying by needed quality, speed, or cost), Context (understanding people, roles, and collaboration insights pulled from emails, files, meetings, past interactions), Tools (actions taken to get work done — sending emails, scheduling meetings, updating documents, and yes, Dynamics 365 ERP actions), and Runtime (the managed cloud orchestration keeping agents working across tasks, including long-running work).
You can actually check the cost for any given session by typing /cost, which shows credits used for the current session, total credits used that month, percentage of your limit remaining, and the reset date. If you hit your monthly limit, Cowork pauses until you either wait for the reset or request additional usage.
Managing Costs Through the Centralized Dashboard
For anyone responsible for budgets, there’s a Cost Management dashboard inside the Microsoft 365 Admin Center under Copilot. It lets you monitor Copilot Credit usage and runway with reporting and spend trends, configure services with spending limits and policies at the tenant, group, or user level, and optimize by informing policy adjustments and smarter budget allocation. It’s genuinely useful for catching runaway usage before it becomes a budget surprise.
Controlling User Access: The Full Governance Table
Putting it all together, there are five clear steps spanning different admin roles: enabling usage-based billing (Global/Billing admin, via M365 Admin Center > Copilot > Cost Management), making Cowork discoverable to end users (Global/AI admin, via Copilot > Settings > AI experiences enabled by usage-based billing), registering the Cowork client ID for MCP access (D365 System admin, via Allowed MCP Clients), adding the Dynamics 365 ERP apps plugin (the Cowork user themselves, searching plugins), and connecting the ERP environment (again the Cowork user, toggling on and selecting their environment).
Where the Roadmap Is Heading
Microsoft frames the roadmap around three phases: Start, Run, and Act — and it’s explicitly noted that sequencing, scope, and timing may shift based on customer feedback and engineering readiness.
In the Start phase, the focus is guiding users to value with persona-aware prompts and enabling work inside real artifacts — co-editing Word, Excel, PowerPoint, and other governed deliverables directly inside Cowork. The Run phase is about reliability: improving citations, long-context handling, task recovery, speed, and lowering the cost of outcomes without sacrificing quality — plus introducing granular Role-Based Access Control for Cowork via MCP. The Act phase looks toward responding to ERP events directly, enabling scheduled and automated triggers for approved exceptions and thresholds, and expanding plugins, connectors, and skills alongside secure browsing and memory capabilities.
Final Thoughts
So where does that leave us? Copilot Cowork combined with the D365 ERP Apps plugin isn’t some flashy gimmick bolted onto Dynamics 365 — it’s a genuinely structured attempt to bridge conversational AI with real ERP workflows, complete with checkpoints, governance, and cost visibility baked in from day one. It won’t replace your ERP consultant or your finance team’s judgment anytime soon, and Microsoft itself is upfront that this is still evolving through its Frontier program. But for repetitive, multi-step ERP tasks that eat up hours every week — RFQ evaluations, purchase order lookups, vendor reconciliation — this combination is worth testing on a real pilot before it becomes standard practice across your organization.
Download full presentation here: Click here
FAQs
1. Do I need a special license to use Copilot Cowork with Dynamics 365?
You need Microsoft 365 Copilot access along with usage-based billing enabled for Copilot Credits, since Cowork consumes credits separately from standard per-seat Copilot features.
2. Is Copilot Cowork available to everyone right now?
Not exactly — it currently sits under Microsoft’s “Frontier” program, meaning it’s an early-access preview built for evaluation and feedback, so capabilities and availability may still change.
3. Can Cowork make changes to my ERP data without my approval?
No. Cowork is designed to pause and request approval before taking consequential actions, like writing data into Dynamics 365 F&O or sending emails on your behalf.
4. What’s the real difference between a prompt and a skill in Cowork?
A prompt handles a single, one-off task with a workflow that can vary each time. A skill standardizes a repeatable business process with consistent controls, tools, and output format across multiple users.
5. How do I keep Copilot Credit usage under control?
Use the /cost command to check session-level usage, and rely on the Cost Management dashboard in the Microsoft 365 Admin Center to set spending limits and policies at the tenant, group, or user level.