Microsoft is quietly rethinking how it charges for Copilot

Microsoft built Copilot around a familiar, predictable pricing model: a flat monthly fee per seat. That model is now under real strain, according to comments from Charles Lamanna, Microsoft's EVP for Copilot, in a June interview with Axios — the users getting the most value from Copilot are also the most expensive to serve, and flat-rate pricing wasn't built to absorb that.

The shift underway is toward usage-based pricing, particularly for agentic features like Copilot Cowork, which already bills on consumed credits rather than a flat seat price. The reasoning tracks with a broader shift GitHub has described publicly: “agentic usage is becoming the default,” and agentic workflows consume meaningfully more compute per task than the drafting-and-summarizing use cases Copilot launched with.

For IT and finance teams, this changes the budgeting conversation from “how many Copilot seats do we need” to something closer to how cloud spend already gets managed — watching consumption, setting budget alerts, and understanding which teams or workflows are actually driving cost. Microsoft has already added a Cost Management Dashboard to the admin center specifically for this, alongside Cowork's usage-based billing.

The near-term action worth taking: if your organization has power users running Copilot Cowork or other agentic features heavily, get visibility into per-user or per-team consumption now, before a broader pricing shift turns an assumption about “flat cost per seat” into a budget surprise.