Copilot Cowork Is Now GA — Metered Billing, Admin Controls & IT Governance Guide

June 2026 · Microsoft 365 · Copilot · IT Admin

On June 16, 2026, Microsoft announced the General Availability of Copilot Cowork — the autonomous, cloud-hosted AI task execution engine built into Microsoft 365 Copilot. If you have been following the preview, you already know the headlines: tasks run in a secure cloud environment, billing moves to consumption-based, and the whole thing is off by default. If this is your first look, strap in — there is a lot to cover before you hand this to your users.

This post covers what Cowork actually is, how the billing model works, how to configure spending limits, what compliance surfaces are available, and — most importantly — what your IT admin checklist should look like before you flip the switch for anyone in your tenant.

Official announcement: microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/

1. What Is Copilot Cowork — And How Is It Different From Copilot Chat?

Regular Copilot Chat is conversational. You type a prompt, Copilot responds, you refine. Everything happens synchronously in your browser or Teams window, and the moment you close the tab the session ends. Copilot Cowork is a fundamentally different execution model.

Cowork is designed for autonomous, multi-step tasks that take minutes or hours to complete — research sweeps across SharePoint and the web, document drafting pipelines, data aggregation across Line-of-Business systems, or filling out forms across web apps. The agent runs in a secure, cloud-hosted environment: your laptop can be closed, your VPN can be off, and the task keeps running. No files are written to your local device during execution. The compliance boundary is maintained in Microsoft's cloud, not on endpoint storage.

Cowork also adds browser task execution — the agent can operate a sandboxed browser to interact with web applications — and image generation capabilities baked into the task pipeline.

Cowork vs. Copilot Chat — Feature Comparison

Capability	Copilot Chat	Copilot Cowork
Execution model	Synchronous / conversational	Autonomous, async, multi-step
Runs when laptop closed?	No	Yes — cloud-hosted
Files stored on device?	Yes (downloads, attachments)	No — cloud execution only
Browser automation	No	Yes — sandboxed browser
Image generation	Designer integration only	Native in task pipeline
Billing model	Included in M365 Copilot licence	Per-task metered billing (on top)
Enabled by default?	Yes (with Copilot licence)	No — admin must enable
Compliance surface (GA)	Audit log, eDiscovery	Audit log, DSPM, eDiscovery, IRM, DLM, Communication Compliance

Jan Ketil Skanke (MVP, Modern Work): "Cowork is the first Microsoft 365 Copilot feature that genuinely feels like an AI employee rather than an AI assistant. The async execution model changes the UX contract entirely — you delegate a task and come back to a result. That is a meaningful shift in how knowledge workers will think about AI."

2. The Billing Model — Per-Task Metered Charges

This is where most IT admins need to pay close attention. Copilot Cowork is not covered by your existing M365 Copilot per-seat licence. It uses a usage-based billing model layered on top of that licence — you pay per task executed.

Charles Lamanna, CVP of Business & Industry Copilot at Microsoft, has been direct about the reasoning: "Flat-rate pricing isn't sustainable for agentic workloads. The compute, orchestration, and tool-call costs of a 20-step autonomous task are orders of magnitude higher than a single Copilot Chat turn. Metered billing lets us price fairly for what is actually consumed."

Key billing facts for GA:

Billing is per task — a "task" is a single end-to-end Cowork job, not per step or per API call within it.
Requires an active Microsoft 365 Copilot licence per user — Cowork is not a standalone SKU.
Charges flow through Azure subscription billing — your Azure cost centre, not the M365 billing portal.
Frontier preview tenants get a grace period: billing starts July 1, 2026. If you were in the Frontier preview and haven't set spending limits yet, you have a short window.
Spending limits can be set at tenant, group, and user level — hard caps, not just alerts.

Frontier preview billing deadline: If your tenant was in the Copilot Cowork preview, billing begins July 1, 2026. You need spending limits configured before that date or users can run up unbounded charges. Do not wait until after July 1 to review this.

3. Admin Enablement — Off By Default

Unlike most Microsoft 365 Copilot features that light up automatically with the licence, Cowork requires explicit admin action. It ships in an off by default state across all tenants — including those that had it in preview. The preview flag does not carry over to GA enablement.

The admin control surface lives in the Microsoft 365 Admin Centre under Settings > Copilot > Cowork. From there you can:

Enable Cowork for the entire tenant, or scope it to specific security groups.
Set spending limits at tenant, group, and individual user level.
Review a real-time task execution log.
Suspend Cowork globally with a single toggle if an incident occurs.

Rudy Ooms (MVP, Microsoft Endpoint Manager): "The off-by-default posture is the right call. I have seen too many features roll out enabled and admins scrambling to turn them off. Starting with a hard gate, requiring an admin opt-in per tenant, and requiring spending limits to be configured before users get access — that is a mature governance model. Microsoft clearly learned from the Copilot pilot rollouts."

4. Compliance and Governance Surface (GA)

The compliance surface that shipped at GA is comprehensive. Microsoft Purview integration covers the full standard suite, with Data Lifecycle Management reaching GA on June 22, 2026 — six days after the main GA announcement. Here is the full picture:

Control	Status	What It Covers
Unified Audit Log	GA June 16	All task execution events, file access, tool calls logged to Microsoft Purview Audit
DSPM (Data Security Posture Mgmt)	GA June 16	Alerts when Cowork tasks access sensitive labelled content; policy-based blocking
eDiscovery	GA June 16	Task inputs, outputs, and intermediate artefacts are discoverable via Purview eDiscovery
Insider Risk Management	GA June 16	IRM policy signals fire on anomalous Cowork task patterns (e.g., bulk data exfiltration via agent)
Data Lifecycle Management	GA June 22	Retention and deletion policies apply to Cowork task artefacts and interaction history
Communication Compliance	GA June 16	Scans Cowork outputs for regulatory keywords, policy violations, inappropriate content

Reference: learn.microsoft.com/en-us/purview/insider-risk-management-overview

5. How to Set Spending Limits — Step by Step

Spending limits are configured in the Microsoft 365 Admin Centre. You can set limits at three levels: the full tenant, a specific security group (department, pilot group, etc.), or an individual user. Limits are hard caps — once reached, Cowork tasks are blocked for that scope until the limit is raised or reset.

Sign in to admin.microsoft.com with a Global Admin or Billing Admin role.
Navigate to Settings > Microsoft 365 Copilot > Cowork.
Under Billing & Limits, select Manage spending limits.
To set a tenant-wide limit: enter a monthly cap in USD under Tenant limit and click Save.
To set a group-level limit: click Add group limit, search for a security group, enter the monthly cap, and save. Group limits are additive — a user in two capped groups consumes from both pools.
To set a user-level limit: click Add user limit, search for the user's UPN, enter the monthly cap, and save. User limits are the most granular control and override group limits where stricter.
Optionally configure alert thresholds (e.g., notify billing admin at 80% of limit) under Spending alerts.
Confirm the Azure subscription linked to Copilot billing under Billing account — charges flow through this subscription.

Important: There is no default spending limit — until you set one, costs are unbounded per user. Microsoft does not impose a default cap. Set at minimum a tenant-level limit before enabling Cowork for any user.

6. How to Monitor Cowork Usage

Microsoft provides three monitoring surfaces: the Copilot Usage Report in the Admin Centre, the Unified Audit Log via Purview, and the Microsoft Graph API for programmatic access. Here is how to use each.

6.1 Admin Centre Usage Report

Navigate to Reports > Usage > Microsoft 365 Copilot. The report surfaces active user counts, task volume, and spending per user. Reference: learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/microsoft365-copilot-usage

6.2 Purview Audit Log

In Microsoft Purview > Audit, filter by Workload: CopilotCowork. Every task execution, file access event, and tool invocation is logged with user UPN, timestamp, task ID, and outcome.

6.3 Graph API — Check Enablement Status and Pull Usage Data

PowerShell — Check Cowork Tenant Enablement Status

# Requires Microsoft.Graph PowerShell SDK
# Scope: Policy.Read.All, Reports.Read.All

Connect-MgGraph -Scopes "Policy.Read.All", "Reports.Read.All"

# Check if Cowork is enabled at tenant level
$coworkPolicy = Invoke-MgGraphRequest -Method GET `
    -Uri "https://graph.microsoft.com/beta/admin/microsoft365Copilot/settings"

Write-Host "Cowork enabled: $($coworkPolicy.coworkEnabled)"
Write-Host "Billing start date: $($coworkPolicy.billingStartDate)"
Write-Host "Tenant spending limit: $($coworkPolicy.tenantSpendingLimit) USD/month"

PowerShell — Pull Cowork Usage Report via Graph API

# Get per-user Cowork task usage for the last 30 days
# Scope: Reports.Read.All

$usageReport = Invoke-MgGraphRequest -Method GET `
    -Uri "https://graph.microsoft.com/beta/reports/getMicrosoft365CopilotCoworkUserCounts(period='D30')"

# Export to CSV for review
$usageReport | ConvertFrom-Json | Export-Csv `
    -Path "C:\Reports\CoworkUsage-$(Get-Date -Format 'yyyyMMdd').csv" `
    -NoTypeInformation

Write-Host "Report exported. Review before billing date."

PowerShell — Query Purview Audit Log for Cowork Events

# Requires ExchangeOnlineManagement module (Purview audit)
Connect-IPPSSession

$startDate = (Get-Date).AddDays(-7)
$endDate   = Get-Date

$auditResults = Search-UnifiedAuditLog `
    -StartDate $startDate `
    -EndDate   $endDate `
    -RecordType "CopilotInteraction" `
    -Operations "CoworkTaskExecuted", "CoworkTaskFailed", "CoworkTaskBlocked" `
    -ResultSize 5000

$auditResults | Select-Object CreationDate, UserIds, Operations, AuditData `
    | Export-Csv "C:\Reports\CoworkAudit-7d.csv" -NoTypeInformation

Note: The Graph API endpoints for Cowork usage reports are currently in beta. Endpoint paths and field names may change before they reach v1.0. Do not build production monitoring pipelines against beta endpoints without a change-management plan.

7. What "Secure Cloud-Hosted Environment" Actually Means

Microsoft's marketing language around "secure cloud-hosted environment" is worth unpacking for IT and security teams. Here is what is documented at GA:

No endpoint file storage: Cowork tasks execute in isolated compute in Microsoft's cloud. Intermediate files, downloaded web content, and generated artefacts are not written to the user's local device. This removes a significant endpoint data leakage vector.
Compliance boundary: The execution environment is subject to your tenant's data residency configuration. If your M365 tenant is geo-pinned to the EU, Cowork compute runs within that boundary.
Identity context: The agent acts with the user's delegated permissions, not elevated service-account permissions. It can only access what the user can access via their M365 identity — it does not escalate privilege.
Browser sandbox: When Cowork uses browser task execution to interact with web apps, the browser runs in an isolated container. It cannot access the user's local browser state, saved passwords, or cookies from the user's physical machine.
Task isolation: Each task runs in an ephemeral compute container. There is no persistent state carried between separate task executions — a task started on Monday cannot access artefacts from a task run on Friday unless they were explicitly written to SharePoint or OneDrive.

Security caveat: "Acting with delegated user permissions" means Cowork's blast radius is bounded by the user's access rights. A user with broad SharePoint permissions who runs a Cowork task can expose significant data through that task. Principle of least privilege for your M365 users has always mattered — it matters more now that an autonomous agent can act on their behalf at machine speed.

8. IT Admin Checklist Before Enabling Cowork

Do not enable Cowork tenant-wide on day one. Work through this checklist first. It is a short list — none of these items should take more than a few hours — but skipping them means billing surprises, compliance gaps, or support tickets you cannot diagnose.

Pre-Enablement Checklist

☐Set a tenant-level spending limit before enabling any users. Even a high cap ($500/month) is better than no cap.
☐Confirm your Azure subscription is linked to M365 billing and your finance team is aware of the new consumption-based line item.
☐Enable Unified Audit Log if not already active. Cowork events will not be captured if audit logging is off for your tenant.
☐Review IRM policies in Microsoft Purview to ensure Cowork-specific signals (bulk file access via agent) are covered by existing or new policies.
☐Validate DSPM sensitivity labels are applied to high-value SharePoint sites and OneDrive locations before agents can access them.
☐Scope the pilot group — start with a small security group (10–20 users), not the entire organisation. Use group-level spending limits for the pilot.
☐Communicate to users that Cowork tasks incur per-task charges and that they will be blocked when their limit is reached — set that expectation before they hit a wall.
☐Define a DLM retention policy for Cowork artefacts before June 22 (DLM GA) — decide how long task interaction history and outputs should be retained.
☐Review conditional access policies — confirm that Cowork cloud execution is covered by your existing Entra ID conditional access rules for M365 Copilot.
☐Brief your security operations team on the new CopilotInteraction audit record type and what "CoworkTaskBlocked" events look like in Purview Audit.

Rudy Ooms (MVP): "My standard advice: treat Cowork like you treated Intune when it first landed. Start with a pilot ring, instrument everything, and only broad-deploy once you have a week of usage data. The feature is GA but your operational processes for managing it are not — build those first."

Summary

Copilot Cowork represents a genuine step change in what Microsoft 365 Copilot can do. Autonomous multi-step tasks, cloud-hosted execution with no endpoint file storage, and a full Microsoft Purview compliance surface are all real and available today. But the shift to per-task metered billing means IT admins cannot treat this as another feature that passively rolls out — you need spending limits set, audit logging verified, IRM policies reviewed, and a pilot scope defined before you enable a single user.

Frontier preview tenants have until July 1, 2026 before billing starts. Everything else should treat June 16 as the starting gun for getting governance in place before end-user demand arrives. That window is short.

Copilot Cowork Is Now GA — Metered Billing, Spending Limits & IT Governance