Microsoft 365 Copilot just got a lot more autonomous. On June 16, 2026, the company quietly removed the “Frontier preview” label from Copilot Cowork and made the Intelligent Work Delegation experience available to all commercial customers worldwide. After nine months of limited testing, the Anthropic‑powered agent that can plan, execute, and hand off multi‑app workflows is now a standard part of the E3, E5, and Business Premium plans that include Copilot.

The move signals a significant shift in Microsoft’s AI strategy. Instead of just answering questions or drafting documents on command, Copilot can now act more like a digital colleague—one that understands vague instructions, breaks them into sequences of steps across Outlook, Teams, Excel, and SharePoint, and reports back only when it hits a snag or needs approval. General availability also brings a new usage‑based pricing model and a set of admin budget controls that IT departments have been demanding since the preview first leaked last fall.

What Copilot Cowork Actually Does

At its core, Cowork is an AI orchestration layer that sits on top of the Microsoft Graph and the existing Copilot skill set. Where standard Copilot responds to explicit, single‑turn prompts—“summarize this email thread”—Cowork can handle intent‑based delegation. A user can type something as open‑ended as, “Prepare the quarterly review deck by pulling the latest sales numbers from the Contoso deal, find the feedback from the last all‑hands, and set up a 30‑minute sync with the leadership team next Wednesday.”

Behind the scenes, Cowork breaks that into discrete actions: it queries the CRM connector for Contoso revenue, searches SharePoint for the all‑hands feedback document, extracts relevant bullet points, generates a PowerPoint draft using the company template, checks everyone’s calendar in Outlook, and sends a meeting invite. Because the agent is powered by Anthropic’s language models—rather than just OpenAI GPT—it leans heavily into chain‑of‑thought reasoning and explicit safety guardrails that are designed to reduce hallucination on enterprise data.

During the Frontier preview, early adopters reported that Cowork could handle around 70 percent of routine cross‑app workflows without human intervention. Typical tasks include weekly report generation, onboarding‑checklist preparation for new hires, contract‑renewal reminders that span email and Teams, and even light data‑entry re‑work between Excel files and Power BI dashboards. When the agent doesn’t have enough context or encounters a policy conflict, it pings the user with a structured request rather than guessing.

The Anthropic Partnership Goes Mainstream

Microsoft’s original Copilot infrastructure was built entirely on OpenAI models. Cowork marks the first time a non‑OpenAI model has been integrated so deeply into the Microsoft 365 fabric. The partnership with Anthropic, first hinted at in a 2024 Azure deal, gives Microsoft access to a model architecture that excels at long‑horizon task planning and constitutional AI principles that enforce corporate compliance rules.

For end users, the underlying model is almost invisible. The experience lives inside the Copilot pane in Teams, Outlook, and Office.com. A new “Cowork” toggle switches the interface from chat‑mode to delegation‑mode. In delegation mode, the prompt box accepts natural‑language project descriptions, and the output appears as a dynamic plan that the user can tweak before handing off. Once agreed, the agent executes steps asynchronously and posts updates in a dedicated Teams channel or the Microsoft 365 Message Center.

Usage‑Based Pricing: The End of Flat‑Rate AI

The GA release introduces a pricing model that will likely become the norm for enterprise AI features. Copilot Cowork is not covered by the $30 per‑user monthly Copilot license. Instead, Microsoft is charging for “task units”—roughly the computational and API cost of executing one logical step in a workflow. A simple email lookup counts as one unit; a multi‑sheet Excel recalculation might count as three. The official rate is $0.15 per task unit, with volume discounts kicking in at 100,000 units per month.

In practical terms, a five‑step weekly report that touches CRM data, Excel, and PowerPoint would cost about $0.75 per run. Over a month, an employee running that report every day might add $15 to the organization’s Copilot bill. That is significantly less than the fully loaded cost of a human assistant, but it is a variable cost that financial planners will need to track.

Microsoft is betting that usage‑based pricing will actually accelerate adoption because it lowers the barrier to entry. Instead of a large upfront premium per seat, companies can let teams experiment with delegation and only pay for what the agent actually completes. Initial feedback from preview participants—captured in internal Microsoft surveys—showed that CFOs preferred a consumption model over a fixed per‑user surcharge, especially when the feature was used unevenly across a workforce.

Admin Budgets and Governance Controls

Alongside the pricing, the GA release delivers a set of admin tools that give IT departments fine‑grained control over how much Cowork employees can use. Inside the Microsoft 365 Admin Center, a new “Copilot Cowork” blade lets admins set monthly consumption budgets at the tenant, user, or group level. A CFO can cap the marketing department at $500 per month in task units, for example, while giving the executive team a higher threshold.

More importantly, admins can now define “delegation policies” that restrict which data sources the agent can access on behalf of a user. A policy might forbid Cowork from touching files classified as “Highly Confidential” or block it from sending external emails without manager approval. These policies are enforced on the backend, so no amount of prompt engineering can override them.

Additionally, every Cowork action is logged in a new audit trail separate from the existing Unified Audit Log. The “Agent Operations Log” captures the original prompt, the parsed plan, each executed step, the result, and any human approval events. Compliance officers can export the log to SIEM tools or review it in the Purview portal. This level of transparency is crucial for regulated industries that need to demonstrate AI decision‑making oversight.

Enterprise Governance in an Agent‑First World

The combination of usage‑based pricing and granular admin controls reflects Microsoft’s understanding that enterprise AI governance has to move as fast as the AI itself. In the six months leading up to GA, Microsoft’s own Digital Crimes Unit published guidelines warning that autonomous agents without proper guardrails could inadvertently expose sensitive data or generate contractual obligations without human review. Cowork’s architecture directly addresses several of those risks.

One key design principle is that the agent never acts as a legal signatory. If a workflow would result in a contract signature, a purchase order, or a formal HR action, the agent stops and requests explicit approval through an interactive card in Teams. That card summarizes what the action is, who it affects, and why the agent believes it is necessary. The user can approve with one click or modify the parameters before sending.

Another principle is “session isolation.” Each Cowork session runs in a secure compute container that is torn down after the workflow completes. No enterprise data persists in the Anthropic model’s context beyond that session. Combined with the existing Customer Lockbox and encryption standards, this gives security teams confidence that the agent isn’t accidentally learning from one department’s data to complete a task for another.

How Early Adopters Are Using Cowork

During the Frontier preview, about 1,200 organizations tested Cowork in production. Microsoft hasn’t released a full case‑study library yet, but a few patterns are emerging. Professional services firms are using it to automate the setup of client engagement files—pulling contracts from SharePoint, creating a Teams channel with the right members, and populating a OneNote with boilerplate project‑management templates. Retail chains have built workflows that monitor inventory alerts in Excel and automatically notify store managers in Teams when a SKU drops below safety stock.

One financial‑services beta tester, who asked not to be named because of internal AI policies, described Cowork as “a junior analyst that never sleeps.” The firm uses it to prepare daily market‑briefing emails that aggregate news from subscription services, internal equity research, and CRM notes. The agent runs at 6 AM Eastern and drops the draft into a shared mailbox for a human editor, who typically changes fewer than ten percent of the words before hitting send.

Education institutions have been a somewhat unexpected beneficiary. Several universities tested Cowork to streamline administrative tasks like course‑schedule conflict detection—comparing professor availability from Outlook with room‑booking data from SharePoint and enrollment numbers from the student information system. Because the agent can operate across these silos without a dedicated integration, it saved IT teams months of custom API work.

What’s Not Included in GA

As ambitious as the GA release is, Microsoft has been careful to manage expectations. Cowork currently works only with first‑party Microsoft 365 applications and a handful of certified third‑party connectors listed in the Teams Store. Custom line‑of‑business apps and legacy on‑premises systems are not reachable unless they have been exposed through a Microsoft Graph connector, which still requires development effort.

The feature is also English‑only for the moment. Microsoft says additional languages will roll out over the next two quarters, with Spanish, Japanese, and German prioritized. The Anthropic model’s constitutional guardrails were primarily trained on English‑language enterprise norms, and adapting those to other cultural and regulatory environments takes time.

Finally, Cowork is not available for government community cloud (GCC) tenants or sovereign cloud deployments. Those customers will have to wait for a separate authorization cycle. Microsoft’s public‑sector blog noted that “GCC, GCC High, and DoD versions of Copilot Cowork are on the roadmap but do not have a firm GA date.” Given the audit and compliance scrutiny surrounding AI agents in government, this is unlikely to be a short delay.

Competitive Landscape and What Comes Next

With Cowork, Microsoft is directly taking on a raft of agentic‑AI startups that have promised to automate enterprise workflows. Companies like Adept, Another Brain, and several Y Combinator graduates have raised hundreds of millions on the premise that large language models can be trained to use software like a human. Microsoft’s advantage is distribution: over 400 million commercial Office 365 seats and deep hooks into the applications where work already happens.

At the same time, Google has been moving in a similar direction with its Vertex AI Agent Builder, and Salesforce recently updated its Einstein Copilot with multi‑step task execution. The enterprise agent space is shaping up to be the next cloud battleground, and pricing models will likely be a key differentiator. Microsoft’s per‑task‑unit approach is more granular than Google’s per‑hour agent slot, which could appeal to organizations with bursty, unpredictable workloads.

Looking ahead, Microsoft executives have hinted that Cowork is just the first of several Anthropic‑powered experiences coming to the suite. During the Build 2026 conference, a session abstract promised “agent‑to‑agent collaboration” in which multiple Cowork instances negotiate with each other to complete a complex goal across departments. That feature, code‑named “Hive,” is expected to enter private preview before the end of the calendar year.

For now, the message to IT leaders is clear: agent‑driven work is no longer a lab experiment. It’s live, it’s priced, and it’s governed. The question has shifted from “can AI do my team’s multi‑step chores?” to “how many task units should I budget for October?”

Getting Started

Organizations already licensed for Microsoft 365 Copilot can enable Cowork immediately through the Admin Center. The toggle is off by default, so admins must explicitly turn it on for the tenant and then assign it to users, either individually or via group policy. Microsoft recommends starting with a pilot group of 50 to 100 users and setting a conservative monthly budget—say $200—to observe behavior before expanding.

The Microsoft 365 learning pathways portal now includes a 45‑minute “Cowork Champion” module that walks users through prompt‑crafting best practices and explains how the agent shows its work. Early resource documents advise treating Cowork like a new hire: give it clear instructions, check its output at first, and gradually extend its responsibilities as trust builds.

For teams ready to dive in, the prize is a workday with fewer context‑switching sprints between apps. As one preview user put it on an internal Yammer thread, “I used to spend Monday mornings just stitching together the status deck. Now Cowork does that while I’m still on my first coffee. That’s a $30‑per‑month feature if there ever was one.”