Microsoft Copilot Cowork licensing in 2026. No SKU of its own, a seat and a meter underneath.

Copilot Cowork has no SKU of its own. It needs a Microsoft 365 Copilot seat, and since June 16, 2026 every task bills in Copilot Credits, so the negotiation covers two things: the seat commitment and the meter.

How is Microsoft Copilot Cowork licensed?

Cowork has no standalone SKU. Every user needs an active Microsoft 365 Copilot license, which lists at $30 per user per month on an annual subscription, and every task Cowork runs is billed in Copilot Credits on top of that seat.

The meter is the newer part. Cowork became generally available on June 16, 2026, and billing started the same day. Microsoft's announcement states that Cowork requires the Copilot user license and that users are then billed on a usage basis, set by the tasks they run. The seat buys access, and the meter pays for the work.

What changed at general availability?

Before June 16, Cowork ran as a Frontier preview, and the first version of this page described it as free once you held a Copilot seat. Tenants with a Frontier user who ran Cowork between March 30 and June 16 got a grace period, and their billing began on July 1, 2026.

The seat question has not gone away. An expansion justified by an agentic demonstration is still an expansion of seat count, term, or both. General availability added a second bill that grows with use and needs its own budget, owner and limits.

Where does the Frontier program fit now?

Frontier is an admin setting that you turn on for Copilot in the Microsoft 365 admin center. Microsoft lists no fee for joining, but it says access and any usage based costs vary by feature, role and subscription.

For Cowork, Frontier now matters mainly for the built in App skill, which is available only to Frontier users. Everything else in Cowork runs on the general availability release once billing is set up.

What does Cowork do, and what does that mean for cost and risk?

Cowork runs long, multi step tasks for a user instead of answering one prompt. Each capability below raises the value on offer and, at the same time, widens what you have to govern and pay for.

• Delegated tasks. It drafts documents, sends mail, schedules meetings and posts in Teams on your behalf, so its actions land in systems of record.
• Reusable skills. Skills capture how you want a workflow done, which raises the value ceiling and concentrates dependence inside daily work.
• Cross application reach. It extends into analytics and business application scenarios, which widens the governance surface at the same time.
• Model choice. At general availability Microsoft named Anthropic's Opus 4.8 and Sonnet 4.6, with its own Cowork 1 model promised at a substantially lower task cost. Anthropic acts as a subprocessor. Admins can turn the Anthropic family off, and users then keep working on the GPT models you allow.
• Switching cost that rises with adoption. Skills embedded in daily work are harder to unwind than a chat assistant, as the Copilot licensing brief explains for the seat itself.

How much does a Cowork task cost in Copilot Credits?

Microsoft prices each task on four inputs: the model, runtime, context retrieval and tool calls. Its illustrative ranges put a light task at 70 to 200 credits, a medium task at 400 to 600 credits, and a heavy task above 1,500 credits.

At $0.01 per credit on pay as you go, that is up to $2, about $4 to $6, and $15 or more per task.

• Light. Compiling a weekly team status note from calendar items and priorities, saved as a draft for review.
• Medium. Preparing for a customer meeting by pulling emails, calendar data, CRM records and files into a briefing.
• Heavy. Analyzing six months of product usage data and writing an executive summary of the patterns.

A worked budget for 1,000 Copilot seats

Say you hold 1,000 Microsoft 365 Copilot seats at list, which is $30,000 a month or $360,000 a year. You enable Cowork for 250 of those users. You budget light and medium tasks at the top of Microsoft's ranges and heavy tasks at the 1,500 credit floor, which leaves some room for error on the common work.

Over a year that is 21,600,000 credits, or $216,000, on top of a $360,000 seat bill. A medium user here costs $120 a month in credits, four times the seat price. For a per task view, see our Copilot Credits cost per task analysis.

Should you prepay credits through P3?

P3, the Copilot Credit Pre-Purchase Plan, buys credits in advance for a one year term at a tiered discount. It renews automatically by default, purchases cannot be cancelled or exchanged, and unused credits expire at the end of the term. Our pay as you go versus prepurchase guide covers the break even.

Run the worked example through it. Tier 4 covers 15,000,000 of the forecast 21,600,000 credits for $138,000, and the remaining 6,600,000 credits bill at pay as you go for $66,000. The total is $204,000, a saving of $12,000 against paying as you go.

Now assume real use lands at half the forecast, 10,800,000 credits. Pay as you go would have cost $108,000, while the P3 buyer pays $138,000 and forfeits 4,200,000 credits worth $42,000 at list. An 8 percent discount cannot absorb a 50 percent forecast error, so we size P3 from measured use.

Why should base Copilot adoption gate any Cowork expansion?

Because the seats you already own are the larger cost, and their adoption lags. In roughly 6 of 10 Copilot rollouts we benchmarked, base seat adoption was still under half at six months. Adding agentic capability to that gap widened the distance between license spend and realized value.

The effective price of a Copilot seat is what you pay divided by the people who use it. Using the same hypothetical 1,000 seats at $30 a month:

The account team will argue that Cowork raises the productivity ceiling and so justifies more seats now. That says nothing about how many of your current seats are in use.

The test is the one that applied before Cowork existed: what share of assigned seats show measured active use, and is that share rising. Keep new Copilot commitments short until it clears roughly 60 percent. The full seat cost model sits in our true cost analysis, and adoption benchmarks are in Copilot adoption in 2026.

Why we would not switch Cowork on for every Copilot user

A common recommendation from partners is to enable Cowork for every Copilot user and let the agentic features pull base adoption up. We advise against it. Cowork bills per task with no included allowance, so tenant wide enablement opens a meter for thousands of people whose use of the base seat you have not yet measured.

The better course is a named pilot group with a written use case for each user, a user level spending limit, and a review after one quarter. That gives you real credits per task from your own tenant, which is the only input worth putting into a P3 or seat decision.

A demo shows what Cowork can do. Your usage report shows what your people do with it, and only one of those belongs in a business case.

How should agent governance be set up before you enable Cowork?

Settle governance before the first user runs a task. Agent governance was an afterthought in about half the rollouts we saw, which created audit and data exposure risk because agents act inside the same applications your staff use.

General availability gives you a natural checkpoint. Someone has to connect an Azure subscription and turn on usage based billing before Cowork works, so make governance sign off a condition of that step.

• Spending policies. In the Microsoft 365 admin center under Copilot, then Cost management, set limits at tenant, group and user level and configure alerts. User limits reset at 00:00 UTC on the first of the month, and unused allowance does not carry over.
• Policy scope as access. Microsoft treats a spending policy as an access control. Anyone in its scope can open Cowork however small the limit, and a user who hits the limit loses access to agents and services until the monthly reset, so scope the policy to the pilot group only.
• App building. Enabling Cowork also enables the app building capability by default, and apps built with Cowork draw on the same credits. Decide whether you want both.
• Agent 365. Put controls, audit logging and data boundaries in place through Agent 365 first. The Agent 365 licensing guide covers who needs the $15 license.
• Model and data terms. Record which model processes your data and the Anthropic subprocessor terms with your compliance team before enablement.

What have we seen in recent Copilot and Cowork negotiations?

Across roughly 30 to 40 Microsoft 365 Copilot engagements in 2025 and 2026, agentic features became the upsell hook well before base value was proven. Measured active use of base Copilot sat between 25 and 45 percent of assigned seats at the six month mark, and agentic capability was being offered as a reason to add more seats.

• Demonstrations treated as evidence. The business case cited the demo and no data from the tenant.
• Expansion before measurement. Seat growth was agreed before anyone measured adoption.
• Governance after enablement. An included capability triggered no procurement review.

Price the commitment and the meter separately, since those are the two things with a price. The wider library sits in the Microsoft practice hub, and the seat and credit numbers for the two layers are broken down in Copilot Cowork pricing.

What will the Microsoft account team say, and how should you answer?

"Cowork is included with Copilot."

The seat gives a user access, and each task is billed on top of it. Ask the team to state in writing whether any Cowork credits come with your Copilot seats, then ask for a credit estimate for your pilot group at Microsoft's own illustrative ranges.

"The agentic ceiling justifies more seats now."

Reply with your measured active use by assigned seat. Offer to revisit expansion when that number clears your adoption gate, and ask what term and price hold Microsoft will offer if you wait.

"Commit to a P3 tier now to lock in the discount."

The lower tiers save 5 to 8 percent, purchases are final and unused credits expire. Say you will size a commitment after three months of cost data from your own tenant.

"Move to E7 and you get Agent 365 with it."

E7 lists at $99 per user per month and includes Agent 365. Price it against the components you would deploy, and ask whether any Cowork credits come with it. Our E7 guide sets out that comparison.

What contract terms should you ask for before committing?

Cowork has no contract of its own, so the terms sit in your Copilot order and any credit purchase. Ask for these in writing:

1. A price hold on Copilot seats for the full term. Expansion priced at today's rate protects you if adoption justifies growth later.
2. A short initial Copilot term or an anniversary reduction right. Either keeps you from carrying unused seats for three years.
3. Written confirmation of which workloads draw on prepaid credits. Cowork, apps built with Cowork, Work IQ API and Copilot Studio agents can share capacity, and capacity assigned in the Power Platform admin center reduces what is left for Cowork. Agree the split before you size the purchase.
4. P3 automatic renewal switched off. It is on by default, and a renewal sized on last year's forecast repeats last year's error.
5. Model and subprocessor terms attached to the order. Data handling terms are easier to agree before enablement than after an incident.
6. Pilot credits funded or capped. Ask whether Microsoft will fund the pilot's consumption, and cap it with a group spending limit either way.

The EA renewal brief covers where Copilot and credit terms fit into a renewal cycle.

How do you check your own Copilot and Cowork usage?

Use Microsoft's own reporting, before any commercial conversation. Agent audit logs, not demonstrations, answer the value question, and Cowork leaves that evidence inside the applications your staff use.

• Microsoft 365 Copilot usage report. In the admin center under Reports, then Usage, it shows active users against assigned licenses.
• Cowork usage report. Under Copilot, then Cowork, it lists active users, total tasks and, per user, scheduled tasks, active days and last activity. Divide a group's credits by its tasks here to get your own cost per task.
• Copilot Dashboard in Viva Insights. It breaks adoption down by group and app, which helps pick a pilot group.
• Cost management under Copilot. The admin center view shows daily consumption by user, policy and service, expressed in credits. Azure Cost Management on the linked subscription shows the billed cost, with Cowork, Copilot Studio and Work IQ API grouped under one Copilot Studio service.
• The /cost command. Users type it inside a Cowork task to see the approximate credits that task has used so far and how much of their monthly limit remains. It uses no credits. Microsoft describes it as an estimate that is not a billing record.
• Microsoft Purview audit. Cowork activity, including each browser task it starts for a user, is recorded in the unified audit log, which shows what ran, how often and for whom.

Which mistakes cost buyers the most?

• Budgeting Cowork at zero. A budget written during the Frontier preview, when Cowork carried no usage charge, has no credit line. Add one before usage based billing is switched on.
• Leaving limits unset. Without user or group limits, a few analysts running heavy analysis every day can consume most of a month's budget with nothing to stop or flag them.
• Using a tiny limit as a block. A low limit does not keep users out of Cowork. Users can start work and are then cut off partway through the month, which frustrates the users you most want to measure.
• Committing P3 on a vendor forecast. The credits expire and the purchase cannot be exchanged.

What to do next

1. This month. Pull measured active use of base Copilot by assigned seat, and treat that number as the gate for any expansion conversation.
2. Before enablement. Settle agent governance through Agent 365, including audit logging and data boundaries, and make it a condition of switching on usage based billing.
3. Before enablement. Confirm which model processes your data inside Cowork, and record the answer and the subprocessor terms with your compliance team.
4. At pilot start. Enable Cowork for a named group only, with user and group spending limits and alerts in Cost management.
5. After one quarter. Take credits per user and per task from your own tenant, and size any P3 purchase from that, with automatic renewal off.
6. At the commitment. Refuse any premium for Frontier access. It is an admin setting, and Microsoft lists no price for it.
7. At renewal. Keep new Copilot commitments short until measured use clears the adoption gate from step 1. Our Microsoft advisory team builds the adoption case and the credit forecast with you.

Frequently asked questions