On June 16, 2026, Microsoft flipped the switch on Copilot Cowork worldwide, moving its “agentic teammate” out of a three-month preview and into general availability for every Microsoft 365 Copilot customer — with a new twist: usage-based billing charged per AI task, on top of the existing per-seat license. For CRM and ERP buyers already juggling license sprawl across Dynamics 365, Salesforce, and HubSpot, this is worth understanding closely, because Cowork isn’t a chatbot feature. It’s designed to take a multi-step, cross-application job — the kind that used to eat an analyst’s Tuesday afternoon — and simply hand back the finished result.

Key Takeaways

• Copilot Cowork reached global general availability on June 16, 2026, after three months in Microsoft’s Frontier preview program, where it became the fastest-growing feature in Frontier’s history.
• Cowork now bills usage separately from the Microsoft 365 Copilot license — roughly $0.01 per Copilot Credit, consumed based on model choice, tool calls, and runtime — on top of a required Copilot seat license.
• Full Cowork access requires the Microsoft 365 E7 bundle, priced around $99/user/month, a roughly $40 premium over E5 that IT buyers are already pushing back on publicly.
• Under the hood, Cowork runs on a mix of models including Anthropic’s Claude (Opus 4.8 and Sonnet 4.6) and OpenAI’s GPT-5.5 for Frontier customers, with Microsoft’s own lower-cost model reportedly coming later.
• Real customer use cases already include sales leaders using Cowork to surface at-risk pipeline opportunities and draft follow-ups in a morning instead of a week.
• More than half of the Fortune 500, plus named customers like Accenture, Avanade, Capital Group, Koch, and Zurich Insurance, used Cowork during preview.
• Cowork is off by default for admins, who must explicitly enable it, set spending limits, and assign access before employees can use it.

What Copilot Cowork Actually Is

Most “AI assistant” features in Microsoft 365 still work the way Copilot always has: you ask a question or request a draft, and a human reviews and finishes the work. Copilot Cowork is built for a different category of task — the long-running, multi-tool job that spans Outlook, Excel, Teams, SharePoint, and OneDrive, where a person defines the outcome they want and Cowork works through the full lifecycle: gathering information, invoking the tools it needs, reasoning through obstacles, and returning a completed deliverable rather than a draft to be finished by hand.

That distinction matters. Microsoft’s own materials describe Cowork as grounded in organizational context through “Work IQ” — meaning it isn’t just summarizing a document, it’s pulling in a user’s actual mail, files, and calendar history to inform the task — and it operates inside Microsoft 365’s existing security and compliance boundaries rather than as a bolt-on tool that needs separate governance.

The reported customer examples from the preview period give a concrete sense of scale: one engineering team used Cowork to automate batch-job spreadsheet editing across dependency flow charts; another team compared roughly 4,000 files across product versions in hours instead of weeks; and, notably for CRM-focused teams, a sales leader used Cowork to identify at-risk pipeline opportunities and compile follow-up details in a single morning — work that had previously taken about a week of manual review.

Why This Matters for CRM and ERP Buyers

CRM Experts Online works with clients running Dynamics 365, Salesforce, HubSpot, Zoho, and NetSuite, and the common thread in 2026 has been the same question from every one of them: which of these AI agent layers is actually going to touch our data, and what will it cost us to find out? Copilot Cowork’s arrival answers part of that question for any organization already on Microsoft 365 — it’s not an isolated AI feature anymore, it’s becoming a metered utility that sits across your inbox, your files, and increasingly your line-of-business systems.

The billing model is the part that should get the most attention from finance and operations leaders, not just IT. Cowork now consumes Copilot Credits based on which model handles the task, how much context it retrieves, how many tools it calls, and how long it runs — which means a single “compare these product files” request and a single “draft this one email” request can cost wildly different amounts, and that cost is invisible until an admin turns on usage reporting. For organizations that have historically treated Copilot as a flat per-seat cost, this is a real budgeting shift.

There’s also a licensing wrinkle worth flagging early: full Cowork functionality is tied to the Microsoft 365 E7 bundle, priced at roughly $99 per user per month — about a $40/user premium over E5. That has already drawn public criticism from IT professionals, with one widely quoted comment calling the pricing “crazy” for the jump required. If your organization is on E3 or E5 today, budgeting for Cowork means budgeting for a tier upgrade, not just a feature toggle.

Practical Use Cases Beyond the Preview Highlights

Microsoft’s headline preview examples (file comparisons, spreadsheet automation, pipeline review) are a useful starting point, but the pattern generalizes well to the kind of cross-system busywork that CRM and ERP teams deal with constantly:

• Sales operations: Compiling a weekly pipeline risk report by cross-referencing CRM export data, email threads, and calendar activity — then drafting the follow-up outreach for each flagged account.
• Finance and ERP teams: Reconciling a batch of vendor invoices against purchase orders stored across Excel and SharePoint before they’re keyed into an ERP system, flagging exceptions for human review.
• Customer success: Pulling renewal-risk signals out of scattered email threads and support tickets and turning them into a structured briefing ahead of a quarterly business review.
• Manufacturing and distribution back office: Automating the kind of multi-file, dependency-heavy spreadsheet work (BOM comparisons, batch job tracking) that currently ties up an analyst for a day at a time.

Because Cowork today is scoped to Microsoft 365 applications rather than third-party connectors, the practical entry point for most of our clients is still document- and mailbox-centric work that feeds into a CRM or ERP system, rather than Cowork acting directly inside Salesforce or NetSuite. That’s an important scoping detail to get right before you promise stakeholders more than the tool currently delivers.

Benefits and Challenges

Benefits

• Genuine time compression on tasks that are tedious specifically because they span multiple files and applications — not just single-document drafting.
• Runs inside Microsoft 365’s existing compliance and security boundary, which simplifies governance conversations compared to adopting a separate third-party agent platform.
• Granular admin controls (off by default, spending limits at tenant/group/user level, usage alerts) give IT a real chance to pilot safely before wide rollout.
• Multi-model routing (Claude and GPT-class models at launch) means Microsoft isn’t locked to a single vendor’s capability ceiling.

Challenges

• Usage-based billing introduces cost unpredictability that per-seat licensing never had — a single ambitious Cowork task can quietly consume a meaningful number of credits.
• The E7 requirement for full functionality creates a real budget conversation, not a simple feature-flag decision.
• Like other agentic tools on the market right now, Cowork still requires plan approval before execution and lacks persistent cross-session memory, so it isn’t yet a “set and forget” automation layer.
• Scope is currently Microsoft 365-native; organizations wanting an agent that reaches directly into Salesforce, HubSpot, or NetSuite today still need a different tool or a custom MCP-based integration.

Implementation Best Practices (and Common Mistakes)

The organizations that got real value out of Cowork during the Frontier preview treated it as a governed pilot, not an all-hands rollout. A few practices worth carrying into your own deployment:

• Set spending limits before you enable access. Cowork ships off by default for a reason — use the admin controls to cap spend at the group level before opening it to a whole department.
• Pilot with a narrow, high-value workflow first. Pick one recurring, multi-file task (a weekly pipeline report, a monthly reconciliation) rather than announcing Cowork as a general-purpose tool on day one.
• Get usage reporting turned on immediately. Because credit consumption varies enormously by task complexity, you need visibility from week one, not after the first surprising invoice.
• Don’t assume it reaches your CRM/ERP directly. Confirm what data sources a given Cowork task can actually touch before promising a business unit an automation that spans systems Cowork doesn’t yet connect to.
• Budget for the license tier honestly. If full Cowork requires E7, model the $40/user/month delta against the actual time savings before committing, rather than discovering the tier requirement mid-rollout.

The most common mistake we’re already seeing is treating this as a like-for-like swap for existing Copilot licensing costs. It isn’t — it’s a new pricing model layered on top of an existing one, and it deserves the same procurement scrutiny you’d give a new SaaS line item, not the assumption that “it’s just Copilot.”

CRM Experts Online’s Perspective

We implement and support CRM and ERP systems for a living, which means we spend most of our time in the seams between tools — the exact place Copilot Cowork is designed to operate. Our honest read: this is a meaningful capability for clients who are already deep in the Microsoft 365 ecosystem and are willing to treat AI spend as its own budget line, not a rounding error on an existing license. The sales pipeline use case Microsoft highlighted is exactly the kind of work we see clients doing manually today — stitching together CRM exports, email threads, and calendar context into something a rep can act on — and automating that reliably is worth real money.

What we’d caution against is assuming Cowork replaces the CRM/ERP integration work itself. It’s a productivity layer on top of Microsoft 365 data, not a substitute for properly connecting your CRM, your ERP, and your automation tooling so that data doesn’t need manual stitching in the first place. The clients who get the most value from tools like this are the ones who’ve already done the unglamorous work of clean data flows between systems — Cowork then becomes a force multiplier on top of that foundation rather than a patch over a messier one. If you’re evaluating whether Cowork, a comparable agent tool, or a deeper CRM/ERP integration project is the better next dollar spent, that’s precisely the kind of scoping conversation we help clients work through before they commit budget.

FAQ

Is Copilot Cowork included in my existing Microsoft 365 Copilot license? Basic access requires a Microsoft 365 Copilot User Subscription License, but full functionality is tied to the Microsoft 365 E7 tier, and all usage is billed separately through Copilot Credits regardless of tier.

How much does Copilot Cowork actually cost per task? Microsoft prices credits at roughly $0.01 each, but total cost per task varies based on the model used, how much context is retrieved, and how many tool calls and how much runtime the task requires — there’s no fixed per-task price.

Can Copilot Cowork connect directly to Salesforce, HubSpot, or NetSuite? Not natively today — Cowork’s connectors are currently scoped to Microsoft 365 applications (Outlook, Excel, Teams, SharePoint, OneDrive). Reaching CRM/ERP data typically means the data has already landed in a Microsoft 365 file or mailbox, or requires separate integration work.

Is Cowork on by default for our organization? No. Cowork is off by default; a tenant admin must explicitly enable it and can set spending limits and access at the tenant, group, or user level before employees can use it.

What models actually power Copilot Cowork? Reporting indicates Cowork uses a mix of models at launch, including Anthropic’s Claude (Opus 4.8 and Sonnet 4.6) and, for Frontier customers, OpenAI’s GPT-5.5, with a Microsoft-built lower-cost model reportedly planned.

How is this different from asking regular Copilot to help with a task? Standard Copilot typically produces a draft or suggestion you then finish yourself. Cowork is designed to execute the entire multi-step task across tools and return a completed deliverable, working through the steps without requiring manual intervention between them.

Is Copilot Cowork worth the E7 upgrade for a mid-sized business? It depends entirely on whether you have recurring, tedious, multi-file/multi-app workflows worth automating at that price point. For a business without heavy cross-application busywork, the E7 premium plus metered usage may not pencil out yet.

Was there a grace period before billing started? Yes — organizations that had at least one Cowork user during the Frontier preview received a grace period through July 1, 2026, before usage billing began; new adopters were billed from general availability onward.

Conclusion

Copilot Cowork’s move to general availability is a real signal about where Microsoft thinks enterprise AI spend is headed: away from flat per-seat pricing and toward metered, task-based consumption layered on top of your existing licenses. For CRM and ERP-centric organizations, the opportunity is genuine — especially for the messy, cross-application reporting and reconciliation work that eats analyst time every week — but the pricing model, the E7 tier requirement, and the current Microsoft 365-only connector scope all deserve a clear-eyed evaluation before you roll it out broadly.

If you’re trying to figure out whether Copilot Cowork, a different agentic tool, or a deeper investment in your CRM/ERP data integration is the right next step for your business, CRM Experts Online can help you scope that decision against your actual workflows and budget — not just the vendor pitch. Schedule a consultation with our team to talk through where AI agents genuinely fit your CRM and ERP stack today.

Further Reading

• Copilot Cowork is now generally available — Microsoft 365 Blog
• Microsoft’s Copilot Cowork now generally available with usage-based billing — Neowin
• Microsoft Makes Copilot Cowork Generally Available Worldwide — Redmondmag
• Copilot Cowork vs Claude Cowork: Same AI, Different Worlds — FindSkill.ai
• The free ride is over: What Copilot Cowork’s new billing model means — Data#3

John M Perez

CRM & ERP Enterprise Technology Expert and Entrepreneurial Executive with 20+ years of leading CRM, ERP, Customer Experience, and Block-chain initiatives and projects across internal and customer facing technologies.  Proven success in closing large deals in Pre Sales customer facing engagements and deploying enterprise wide CRM & Customer Experience solutions internationally and domestically.