Microsoft Copilot Credits: who owns the meter on the advanced workflow?

The Copilot activation checklist is nearly complete. Subscription: named. Seat owner: named. Rollout group: named.

Three rows are still blank. Which workflow may consume credits? Who owns the spending cap for it? What result earns the agent another run?

Under Microsoft’s new Copilot model, those blank rows are the part of the cost that moves. The fixed seat covers everyday work; advanced, long-running work is metered separately, so each credit-consuming workflow needs its own owner, spending policy and task-level result before it is switched on.

What changed in Microsoft’s Copilot licensing?

Microsoft now separates a fixed per-user subscription from usage-based billing for advanced agentic work.

In its 25 September 2026 announcement, Microsoft describes the user subscription as covering Copilot in Chat and across Word, Excel, PowerPoint, Outlook and Teams, with model selection. It then states that Cowork, Code and Autopilot — the new long-running agentic capabilities — and frontier models run on usage-based billing.

Microsoft says the capabilities are rolling out through its Frontier programme, with broader availability to follow over the coming weeks and months. The boundaries are new and may move, so read the current Copilot Credits licensing guidance before any budget or activation decision rather than relying on this page or any other secondary summary.

Which Copilot work consumes Copilot Credits?

The advanced, multi-step and agent work consumes credits; everyday Copilot in the Microsoft 365 apps does not.

Microsoft’s licensing guidance lists Copilot Chat and the experiences in Word, Excel, PowerPoint, OneNote, Outlook and Teams — including the built-in Researcher, Analyst and Facilitator agents — as included in the subscription, with no credits consumed in those authenticated employee scenarios. Credits are consumed by Copilot Cowork’s multi-step work and by other agent workloads, such as Copilot Studio agents, Dynamics 365 agents and Power Platform AI features beyond their included entitlements.

The same guidance prices pay-as-you-go credits at $0.01 per Copilot Credit, with an annual pre-purchase plan whose unused credits expire at the end of the term. The price of one credit tells you little on its own. What matters is how many credits one run of a workflow consumes, how often it runs, and what that run replaces.

So not every Copilot action is metered. The practical risk is narrower and easier to miss: an organisation assigns seats, considers the licence question closed, and the variable part of the cost arrives through a few advanced workflows nobody named.

What does a Copilot activation checklist need beyond seat assignment?

For every workflow that may consume credits, six fields:

1. The workflow and its owner. Name the task — for example, a long-running research-and-draft job for tender responses — and the role accountable for its result. “Agents for the finance team” is not a workflow.
2. Who may run it, and with which models. Microsoft lets administrators set which model families are available to which groups. Decide this per workflow.
3. The spending cap and its owner. Microsoft describes spending policies that administrators manage at scale. Someone has to choose the number and own it.
4. The approval route for more. Microsoft allows end-user credit requests to be routed into existing approval workflows. Decide who approves, on what evidence, and how quickly.
5. The result that earns another run. Record the starting point before activation — how long the task takes today, what quality it reaches, how much rework follows — and the result a run must reach to justify the next one.
6. The review and the stop rule. Who checks the output before it is used, and what happens if runs keep consuming credits without meeting the result.

Microsoft also says end users can see their own credit usage, remaining balance and history in Copilot. That visibility helps, but it does not replace the six fields. A person watching their balance can control their own spend; they cannot decide whether the workflow deserves a budget.

Is Microsoft Copilot worth it for enterprise?

It depends on the workflows, and the new model makes that question more specific rather than easier to avoid.

The fixed seat is worth it where people use Copilot in their daily documents, email and meetings in a way that changes how the work gets done. The credit-consuming layer is worth it where a named, recurring workflow produces a result — against its starting point — that justifies the consumption and the review work around it. Those are two different questions, and a single “Copilot ROI” number hides the difference.

This also connects to a wider gap. Cost monitoring is common; comparing cost with the value the work produced is much rarer. Usage-based billing makes the cost visible per run. It does not produce the value comparison unless someone designs it into the workflow.

How should the cost of a long-running agent be compared with its result?

Per workflow, per run, against the starting point.

Take one run of the workflow. Record the credits consumed, the human review time it still needs, and the rework that follows. Compare that with how the same piece of work was done before: the hours, the handoffs, the error rate. Saved hours are released capacity, not automatically cash, so record what the team does with that capacity rather than converting it into a euro figure it has not yet earned.

That comparison is the architecture work behind the licence. The seat is a procurement decision. The credit-consuming workflow is a design decision about ownership, permissions, review and a measurable result — and it is worth making before the first long-running run, not after the first invoice.