By Matt Lawson, Senior Consultant, i3solutions

The Copilot seats were budgeted a year ago and approved as a clean per-user line item. Then somebody in finance opens Cowork, asks it to turn a folder of invoices into a reconciled spreadsheet, and the tenant starts drawing down credits against an Azure subscription that no one on the budget committee has seen. Two weeks later the IT director gets one question in the steering meeting: we already pay for Copilot, so why is there a second bill? The answer is unambiguous, it is published by Microsoft, and it sits in a different document from the one everyone read when they bought the seats.

Is Copilot Cowork included in the standard Microsoft 365 Copilot license, or an additional cost?

No. As of August 2026, Copilot Cowork is an additional cost. Microsoft’s Copilot Credits licensing guidance states that Cowork “requires the Microsoft 365 Copilot license as a prerequisite” and that “No Cowork entitlements are included with the Microsoft 365 Copilot subscription.” The seat unlocks Cowork; every task it runs is billed separately in Copilot Credits.

That is the whole answer, and the rest of this page is about what it costs you to act on it: how the credits are actually billed, the admin step without which Cowork does not run at all, the numbers Microsoft deliberately does not let you know in advance, and the one question about regulated tenants that Microsoft has not published an answer to yet.

1. The licensing facts on this page, and where each one came from

Licensing claims age badly, and a page about a product Microsoft is still shipping into ages worse than most. Every statement below was checked against Microsoft’s own published documentation on 22 August 2026. The dates in brackets are the last-updated dates Microsoft states on each page, not our reading of them.

Two of those sources give the same per-credit figure, which is why we are willing to print it. Read them yourself before you build a budget on this page: if Microsoft has changed the terms since our check date, Microsoft’s page is right and this one is stale.

2. Why “included” and “prerequisite” are not the same word, and the difference is the bill

The Microsoft 365 Copilot seat is an entry ticket. It grants the right to open Cowork. It does not carry any quantity of Cowork work with it, and Microsoft’s own framing is that “licenses act as an entry point enabling access to AI services billed on a pay-as-you-go basis.”

This is not a novelty in the Microsoft stack, which is the useful part for anyone building a forecast. The same service description that lists Copilot feature availability carries the footnote that “Power Platform licenses aren’t included with Microsoft 365 Copilot.” The pattern is consistent: a Microsoft 365 Copilot seat buys the assistant that answers, and any capability that goes off and does something on its own meter is licensed and metered separately. Cowork is the current, largest instance of that pattern, because the whole point of Cowork is that it acts.

The correct mental model for a budget is two lines, not one:

  1. A fixed, forecastable seat cost. Per user, per month, on a qualifying base plan. If you have not sized this part yet, our Microsoft 365 Copilot licensing guide walks the seat math and the base-plan prerequisites for a regulated enterprise.
  2. A variable, consumption-driven Cowork cost that scales with how much work your people hand to it, is pooled at tenant level, and has no natural ceiling until an administrator sets one.

Finance teams are used to the first line. The second line behaves like an Azure resource, not like a Microsoft 365 SKU, and it lands in the middle of a Microsoft 365 budget conversation where nobody is expecting it.

3. How the variable line is actually billed

Microsoft’s documentation is specific about the mechanics, and the details change what a sensible commitment looks like.

  • The currency is Copilot Credits, described by Microsoft as “a common currency for eligible Microsoft services with usage-based billing.” The same pool serves Cowork, Copilot Studio, Dynamics 365 agents, Power Platform workloads and the Work IQ API.
  • Prepaid and pay-as-you-go are not alternatives, they are layers. Microsoft states plainly that “Copilot Credit Pre-Purchase Plan (P3) and pay-as-you-go aren’t separate billing options. P3 is layered on top of pay-as-you-go”, and that when prepaid credits run out, “usage automatically continues on a pay-as-you-go basis.”
  • There is a defined drawdown order when you hold more than one form of prepayment: capacity packs first, then P3 prepaid credits, then pay-as-you-go.
  • Prepayment is a one-year, non-refundable commitment. Microsoft’s Copilot Credit pre-purchase plan documentation (updated 17 July 2026) states that “Each pre-purchase plan has a one-year term”, that plans renew automatically by default, and that “Cancel and exchange operations aren’t supported for Copilot Credit Pre-Purchase Plans. All purchases are final.” Read the savings figure on that page carefully, because it is an illustration rather than a price list: it assumes “the pay-as-you-go rate for Copilot Credit to be $0.01”, then says of a Tier 2 (15,000 CU) plan, “let’s say the cost of that tier is $14,100, it will give a 6% saving compared to the pay-as-you-go rate for the same usage.” The tier percentages that will actually apply to you are shown in the Azure portal purchase page, not in the article, and Microsoft warns that “Pre-purchase plan discounts don’t combine with other discounts you might have.” Price your own tier in the portal before committing.
  • Your Power Platform spending and your Cowork spending compete for the same prepaid capacity. Microsoft is explicit that capacity “assigned or used in Power Platform admin center (for example, allocated to specific environments or consumed by agents) reduces the prepaid capacity available for Cowork and Work IQ API services managed by Microsoft 365 admin center.”
  • If you hold an Azure Consumption Commitment, eligible Copilot consumption can draw on it, but only when the spending policy is bound to a subscription under the billing account carrying the commitment. Microsoft warns that with the wrong subscription “you still pay for consumption, but it might not count toward your MACC.”

That last point is the one worth reading twice. It is a configuration decision made once, in an admin panel, that determines whether a year of AI consumption counts against a commitment you have already made. Microsoft also notes that “After you set a billing method for a spending policy and create the policy, you can’t change it. To update it, you must delete the policy and create a new one.”

4. Until an administrator turns billing on, Cowork does not run at all

This is the operational fact most cost conversations miss, and it is a separate question from the money.

Cowork is not a feature that appears when the seat is assigned. Microsoft’s setup documentation describes the first-run flow as the step that “activates the AI experiences, like Cowork, that are gated by usage-based billing”, and the Cowork prerequisites list an active Microsoft 365 Copilot license and that “Usage-based and Cowork billing has been enabled.” Enabling it requires a Global administrator or Billing administrator, because those are the only roles that can “add, select, and change billing methods.” An AI administrator or License administrator can create spending policies and read the dashboards but, in Microsoft’s words, “can’t set or modify the billing method.”

Two consequences follow for a regulated enterprise, and both are governance questions rather than technical ones. First, the person who unlocks the spend is a highly privileged billing role, and the setup is a one-time act with a durable financial consequence. Second, the controls you set at that moment are the controls you get: a tenant-level spending limit, optional per-user limits, alert recipients and thresholds, and a policy scoped to groups. Microsoft’s guidance is to set the per-user limit deliberately “to prevent runaway spending of Copilot Credits by one individual user”, and describes what happens when the limit binds: “When users hit the limit, they lose access to agents and services for the rest of the month until credits reset on the first of the month.”

A spending cap that silently removes a tool from a department in the third week of every month is not a cost control. It is an adoption failure with a budget line attached. Set the limits with the business owners in the room, and instrument the alerts before the first business unit gets excited about Cowork rather than after.

5. What Microsoft deliberately does not let you know in advance

A cost model needs a unit cost and a unit volume. Microsoft publishes the unit cost. It does not publish the volume, and it says so in its own documentation rather than leaving you to discover it.

  • There is no published credit price per task. Microsoft’s position is that the credits consumed depend on the complexity of the work performed. A one-line answer and a deep research task that touches forty documents are not the same expense, and the same prompt does not cost the same twice.
  • You cannot check what a task will cost before running it. Microsoft’s FAQ answers “Can I check the cost before running a task?” with a flat “No. Currently, you can only use /cost to check how many credits a task has already used.”
  • The in-product number is an estimate, not a bill. Microsoft states that /cost “shows an approximation of your consumption based on activity logged to date. It is not an authoritative billing record”, and is explicitly “not intended for” official billing or invoice reconciliation.
  • Unused credits expire monthly. “No. Credits reset monthly and do not carry over. Any unused credits from the previous month are not added to your credit limit for the new month.” Prepaying against an over-optimistic adoption curve buys nothing back.

Microsoft does offer a Customer Cowork Estimator for modeling expected credit usage, and it is a reasonable place to start. Treat its output the way you would treat any vendor sizing tool at the beginning of an adoption curve: as an input to a pilot, not as a budget. The defensible way to size this line is to run a bounded, instrumented pilot with a named group, a per-user limit and alerting on, read the Consumption tab by user and by service, and extrapolate from your own tenant’s numbers rather than from anyone’s model.

6. The regulated-tenant question Microsoft has not answered yet, stated as unknown

Most of our clients run under CMMC, ITAR, DFARS, HIPAA or SOC 2 obligations, and for them the first question is not what Cowork costs but whether it exists in their environment at all. Here we have to report a gap rather than an answer, and the gap is more useful than a guess.

As of 22 August 2026, Microsoft has not published Cowork availability for GCC, GCC High or DoD in either of the two places it publishes that kind of statement. We checked both. Microsoft’s overview of U.S. government cloud environments for Microsoft 365 and Copilot [16 March 2026, refreshed 18 August 2026] does not mention Cowork. Neither does the feature-availability table in the Microsoft Copilot service description [5 August 2026, refreshed 21 August 2026], which is the table Microsoft itself points to for this question and which does carry rows for Chat, Researcher, Analyst, SharePoint agents, declarative agents and more, each marked per environment.

Unknown is not unavailable, and it is not availability either. Three things the same published sources do support:

  • Microsoft’s stated general rule is that in government clouds “Feature availability may differ” and “Release timing typically lags behind commercial environments.” Copilot capabilities “may be introduced on a different timeline than in commercial environments due to sovereign cloud requirements.”
  • Scheduled Prompts, which the Cowork overview lists as a Cowork capability, is marked in that same feature table as “Not currently available” in GCC, GCC High and DoD while being available commercially. Adjacent capability, already gated.
  • The usage-based billing documentation describes setup exclusively in terms of Azure subscriptions, Azure Consumption Commitments and the commercial Microsoft 365 admin center. It says nothing either way about the government billing surfaces.

The practical instruction for a regulated tenant: do not put Cowork in a fiscal-year plan on the strength of a commercial announcement, and do not tell a compliance officer it is unavailable either. Ask Microsoft or your licensing partner for a written statement on your specific environment, get it dated, and re-ask on the roadmap cadence. If you are still choosing an environment, the trade-offs are laid out in our comparison of GCC High and GCC Moderate, and feature timeline lag is one of the costs that belongs in that decision.

7. The cost that is not on anyone’s price list

Cowork acts. It sends mail, posts in Teams, creates and reorganizes files in SharePoint and OneDrive, and searches across the organization. That changes the risk profile of your existing permission model, because an agent operating with a user’s access will find and act on everything that user can reach, at machine speed, whether or not anyone intended them to reach it.

This is where the real money usually is, and it is the pattern we see most consistently. i3solutions AI readiness assessments scope from a shallow tenant readiness scan at the low end to deep unstructured data discovery at the high end. The order-of-magnitude difference between AI readiness assessment quotes is data governance cleanup: when Dataverse and SharePoint access-control alignment has to precede a Copilot or OpenAI API integration, that remediation dominates the engagement.

The underlying condition is usually older than the AI project, and the figure below is i3solutions delivery data rather than a vendor statistic or an industry survey. Across our Microsoft 365 migration and modernization work: Lift-and-shift migrations typically carry over 60 to 80% of existing permission inconsistencies, creating immediate audit exposure in Microsoft 365 environments rather than resolving the underlying governance debt. An oversharing problem that was survivable when it took a person a determined afternoon to stumble into it is a different problem when an agent can traverse it in a single task, on a schedule, on behalf of anyone with a seat.

So the honest total for a Cowork rollout in a regulated enterprise has more than the two lines above. It has:

  • Tenant and data readiness, sized by how much permission remediation and access-control alignment your estate actually needs. An i3solutions Microsoft 365 Copilot readiness engagement typically runs $18,000 to $35,000. Where it lands in that band is driven by the state of the estate, not by seat count.
  • Governance of the spend itself: spending policies mapped to real cost centers, per-user limits set with business owners, alerting that reaches someone who can act, and a monthly read of the Consumption tab. i3solutions governs client Power Platform tenants with the Center of Excellence Starter Kit, tenant-level and environment-level DLP policies, and managed environment controls. The same discipline applies to a credit pool that Power Platform and Cowork now share.
  • Ongoing review as consumption patterns settle. Governance Subscription engagements run from $18,000 to $42,000 per quarter, refreshing the recommendation matrix as the estate evolves. For a consumption-billed service in its first year, that refresh cadence is doing real work rather than ceremonial work.

The offset is real too, and it usually shows up in the same review. ROI analysis consistently shows potential savings of $50K-200K annually from optimized licensing and governance improvements alone. Behind that number is who does the work and under what accountability: i3solutions plans and runs governed Azure and Microsoft 365 migrations with senior, U.S.-based engineers. i3solutions delivers under a partner-led engagement model with named accountability and governance that holds up under a client audit, as distinct from contractor-only staff augmentation. For a spend line with no natural ceiling, the concrete step is narrower than any of that: name one accountable owner for the credit pool before the first spending policy is created, and put the monthly Consumption read on that person’s calendar.

What to bring to a scoping conversation

Four answers and thirty minutes are enough to size this honestly: how many Microsoft 365 Copilot seats you hold today and on which base plan, which cloud environment your tenant runs in, whether anyone has already enabled usage-based billing and under which Azure subscription, and whether you have ever run a permission audit across the SharePoint and OneDrive content a Cowork user could reach. If the last answer is no, that is the finding, and it is usually where the work starts.

You do not need a proposal to leave that conversation with something useful. What you should get out of thirty minutes is a written separation between the seat cost, the consumption cost, and the readiness cost, so your finance and security people can each argue with the line that belongs to them. A single blended number is the version that does not survive the steering meeting. If you are building the internal case rather than buying this quarter, that separation is the part that outlasts the meeting, because it is the artifact your committee will actually review.

Bring the four answers above and we will work the numbers with you against your own tenant rather than against a model.

Schedule a 30-minute scoping call

If the harder question on your side is architectural rather than financial, which cloud environment you belong in, how the permission model has to change before an agent operates inside it, or how a shared Power Platform and Cowork credit pool should be governed, that is a different conversation and it should be with someone who has built it. Ask for the architecture track when you book.

Talk to a senior architect

Frequently Asked Questions

Is Copilot Cowork included in the Microsoft 365 Copilot license?

No. Microsoft’s Copilot Credits licensing guidance states that Cowork “requires the Microsoft 365 Copilot license as a prerequisite” and that “No Cowork entitlements are included with the Microsoft 365 Copilot subscription.” The seat unlocks Cowork; it does not include Cowork usage. Budget the two lines separately: a fixed, forecastable seat cost, and a variable, consumption-driven Cowork cost billed in Copilot Credits.

What does a Copilot Cowork task actually cost?

Microsoft publishes the unit price and not the volume. The stated rate is “$0.01/Copilot Credit,” and the number of credits a task consumes depends on the complexity of the work performed. Microsoft’s own FAQ answers “Can I check the cost before running a task?” with “No. Currently, you can only use /cost to check how many credits a task has already used.” The defensible approach is a bounded pilot with per-user limits and alerting on, then extrapolation from your own tenant’s Consumption data.

Do we have to do anything before Copilot Cowork works for our users?

Yes. Until usage-based billing is enabled, Cowork does not run at all. Only a Global administrator or Billing administrator can “add, select, and change billing methods”; an AI administrator or License administrator can create spending policies but, in Microsoft’s words, “can’t set or modify the billing method.” Set the tenant limit, the per-user limit, and the alert thresholds with business owners in the room, because Microsoft states plainly that “When users hit the limit, they lose access to agents and services for the rest of the month until credits reset on the first of the month.”

Is Copilot Cowork available in GCC, GCC High or DoD?

As of 22 August 2026, Microsoft has not published an answer, and we report that as unknown rather than guessing. Cowork does not appear in Microsoft’s overview of U.S. government cloud environments, and it is absent from the feature-availability table in the Microsoft Copilot service description, the table Microsoft itself points to for this question. Microsoft’s general guidance for government clouds is that “Feature availability may differ” and “Release timing typically lags behind commercial environments.” Scheduled Prompts, a capability the Cowork overview lists alongside Cowork, is already marked “Not currently available” in GCC, GCC High and DoD.

Do unused Copilot Credits carry over from month to month?

No. Microsoft states: “Credits reset monthly and do not carry over. Any unused credits from the previous month are not added to your credit limit for the new month.” Prepayment is a separate commitment: a Copilot Credit Pre-Purchase Plan runs a one-year term that renews automatically by default, and “Cancel and exchange operations aren’t supported for Copilot Credit Pre-Purchase Plans. All purchases are final.” Prepay against measured consumption from a pilot, not against a forecast adoption curve.

Related