Why Did Our Copilot Credits Suddenly Drop? (The July 1 Cowork Billing Switch )

OfficeHours — Thu, 16 Jul 2026 07:44:18 +0000

The pattern I keep seeing
Lately I've heard the same story from a few different orgs: "our Copilot credits are burning way faster than before, and nobody knows why." Nine times out of ten, the answer is the same thing — Copilot Cowork billing kicked in.
If you already knew this, great. But a surprising number of admins and users missed the exact moment it happened — so here's the timeline, the billing structure, and what to check right now.

What actually happened
Copilot Cowork is the agentic layer inside Microsoft 365 Copilot — instead of just answering questions, it plans and executes multi-step, multi-tool work end to end. Here's the timeline that matters:

March 30, 2026 — Limited preview launch through the Frontier program
June 16, 2026 — General availability worldwide; billing begins for new users from this date
July 1, 2026 — The grace period for Frontier preview tenants ended. Any tenant that had at least one user run Cowork during the preview window (March 30–June 16) got billing waived until this date. After July 1, they're billed like everyone else.

So if your org tried Cowork during the preview, July 1 is the day the free ride ended. Teams that got comfortable using it without thinking about cost during preview often kept the same usage habits — and then watched credits disappear faster than expected.

The billing structure, one more time
Here's the part that trips people up: having a Microsoft 365 Copilot license does not mean Cowork is free.

The Microsoft 365 Copilot user subscription license (USL) is a flat per-user fee. It covers Copilot Chat, in-app Copilot features, Work IQ, and pre-built agents.
Copilot Cowork sits on top of that as a separate, usage-based charge. It's billed in Copilot Credits, and the cost of each task depends on four things: the model used, context retrieval, tool calls, and runtime.

In short: it's license fee plus consumption-based Cowork usage — two separate meters. The preview just delayed the second one.
What to check right now
If your org used Cowork during the Frontier preview, walk through this list:

Check the Cost Management Dashboard in the Microsoft 365 admin center — see what's been consumed against budget so far.
Verify spending limits are actually set. Tenant, group, and user-level limits are all available — if nobody configured them during preview, do it now.
Identify your heaviest Cowork users. Anyone who kept preview-era habits without adjusting is worth a quick heads-up.
Use the model picker deliberately. Lighter models for lighter tasks meaningfully cuts credit burn.

Why the timing matters more than the tech
Technically, this was a scheduled transition — nothing surprising about it from Microsoft's side. But in practice, billing switches like this always show up as a communication problem, not a technical one. If people got used to a free tool during preview and nobody told them it would start costing money, the reaction is rarely "oh, that makes sense" — it's "wait, why is this suddenly different?"

What actually prevents that friction isn't a deep technical explainer. It's one clear line: "starting [date], this changes." If your org tested Cowork during preview, a short heads-up to users now will save a lot of confused Slack threads later.

The bigger pattern
Every new AI tool goes through the same arc in an org: it starts as "wow, this is genuinely useful," and eventually someone asks "wait, this costs how much?" Copilot Cowork's July billing switch is just the latest example.
I'll keep tracking these transition points as they come up — follow along if you're navigating the same thing.

Hi, I'm starting a new chapter here 👋

OfficeHours — Thu, 16 Jul 2026 06:59:46 +0000

I work on Microsoft 365 and Copilot rollout projects — specifically on the change management and user training side. My job isn't configuring tenants or writing PowerShell scripts (though I touch that too); it's making sure that once M365 or Copilot is deployed, people actually use it, and use it well.
That gap — between "the tool is live" and "the org has actually adopted it" — is where I spend most of my time. And it's the gap I want to write about here.
What I keep running into
A few patterns show up in almost every project:

Rolling out a new feature is easy. Getting it embedded into daily workflows is the hard part.
Everyone agrees "we should use AI," but far fewer people know how, or why it matters for their specific job.
Training that works for one team completely misses the mark for another — there's no universal playbook.

None of this is really a technology problem. It's a people problem that happens to involve technology.
Why I'm writing this blog
I've kept most of this knowledge locked in internal reports and project decks. Starting now, I want to share it publicly — partly to build credibility in this space, and partly because I think change management and training don't get nearly enough attention in the M365/Copilot conversation compared to the technical setup side.
Here's what I'll be writing about:

Real change management challenges from Copilot rollouts (and what actually worked)
Lessons from designing and running user adoption training
Practical takeaways from M365 updates, seen through an adoption lens
Honest write-ups of things that didn't work, and what I'd do differently

Let's talk
If you're working on M365 or Copilot adoption in your org — or fighting the same "great tool, nobody's using it" battle — I'd love to hear how you're tackling it. Drop a comment or follow along; I'll be posting regularly.

DEV Community: OfficeHours

Why Did Our Copilot Credits Suddenly Drop? (The July 1 Cowork Billing Switch )

Hi, I'm starting a new chapter here 👋