Copilot now charges per task: FinOps for AI

At the end of September, Microsoft published two Message Center posts that change more than any new feature: MC1479276 on the pricing model and MC1470425 on cost management. In short: Copilot is no longer just a license per user. Copilot becomes a consumption product.

Two levels: license and credits

The logic is simple, the consequences are not.

Level	What belongs to it?	Billing
Everyday AI	Model choice and auto mode, which picks the model and reasoning effort per request	Included in the Copilot license (user subscription license, USL)
Advanced AI	New frontier models, agentic features like Cowork, Code and Autopilot, advanced capabilities of Copilot in SharePoint and OneDrive	Usage-based billing (UBB) with Copilot Credits
At the limit	Users keep working with credits instead of waiting	Copilot Credits

ℹ️ Important
In existing tenants, nothing happens as long as no admin creates a spending policy in the admin center. Only then do credits flow.

⚠️ Exception: Copilot Business
For new Microsoft 365 Copilot Business purchases, usage-based billing has been set up by default since 19 October 2026, including a spending policy with preset limits (MC1476200). This applies to direct purchases first, CSP follows later. Especially for mid-sized companies, this means: check the policy and limits right after purchase.

FinOps for AI: what is new

Microsoft ships the tooling to steer these costs right away:

• Cost management now covers Cowork, Work IQ APIs, Copilot Code, Copilot Managed Runtime and advanced SharePoint and OneDrive work.
• Spending policies per group: you define which models and which effort level a group may use, even which models auto mode in Cowork may choose.
• Consumption dashboard in Insights: it shows where and for what credits are consumed. That turns “What does it cost?” into “What does it deliver?”.

The September package in cost management

MC1470425 brings the details for operations:

• Auto-apply new services: new UBB services and agents automatically fall under existing policies. On by default.
• Threshold emails: admins get a warning before users reach their limit.
• More read access: AI Reader, Global Reader and License Administrator can now see the consumption dashboards.
• Better reports: expanded consumption views for reporting.
• Approval paths: credit requests can be routed to your own approval workflows.

⚠️ Watch out for auto-apply
It sounds convenient, and it is. But it also means: every new paid service Microsoft rolls out automatically lands in the budget of your existing policies. Decide consciously where you want that.

And the users?

Licensed users see the new features like Cowork, Code and Autopilot even when no policy applies to them yet. What they are shown in that case, you control via the discovery setting for UBB features in the admin center. In other words: demand is coming, whether you like it or not. Better to have a process in place first.

What stays

Microsoft is transparent here and ships the controls along with it. That is fair. The blind spot is on our side: many organizations introduced Copilot as a licensing project, not as an operating cost topic. That changes now.

☕ Espresso Moment: An espresso is paid per cup, not per machine. Now Copilot is too.

Your takeaways

• Clarify who in the company decides on Copilot budgets
• Create a spending policy for a pilot group, not for everyone right away
• Decide on “Auto-apply new services” consciously in every policy
• Set up threshold emails
• Set the discovery setting: what do users without a policy see?
• For Copilot Business: check the preset policy and limits right after purchase
• Review the consumption dashboard regularly with the business departments

Message Center posts: MC1479276, MC1470425, MC1479277, MC1476200

How are you tackling this in your tenant? Tell me on LinkedIn, I am curious about your experiences.