A Microsoft Copilot Seat Does Not Cover Every Copilot Credit Charge

A small company can assign Microsoft Copilot licenses, open Cowork, and assume the seat price covers the work. Microsoft’s current documentation says otherwise: in some scenarios the license is an entry point to an AI service that is billed by usage.

The Copilot Credits overview, checked 28 August 2026, says this Cost Management surface currently covers Copilot Cowork and the Work IQ API. It also warns that other pay-as-you-go Copilot services have separate billing pages. A license, a Copilot Credit meter, and another Copilot product should not be collapsed into one “Copilot bill.”

Separate the seat from the meter

The fixed license pays for licensed Microsoft Copilot experiences. The usage-based layer measures eligible work in Copilot Credits and bills it through the billing method connected to the spending policy.

Microsoft’s current Copilot Credits licensing guidance says Cowork requires a Microsoft Copilot license but includes no Cowork entitlement in that subscription. It also describes Work IQ API use as a separate Copilot Credit workload. Native experiences inside the licensed product are not automatically the same thing as a custom solution calling Work IQ APIs.

The safe procurement model is therefore:

Layer	What to verify
Microsoft Copilot license	Which users have access, and which native experiences the current license includes
Copilot Credit billing method	Which Azure subscription, prepaid capacity, or P3 plan pays for eligible usage
Spending policy	Which users or groups can consume credits and the monthly limits that apply

Do not describe the variable charge as necessarily arriving on a literal second invoice. It is a separate usage meter; Microsoft Learn says a P3 purchase itself appears as a separate invoice line item, while pay-as-you-go consumption is tied to the selected Azure subscription.

Pay-as-you-go and P3 are layered, not alternatives

Microsoft Learn’s P3 page uses $0.01 per Copilot Credit as the pay-as-you-go assumption in its sizing example. In that example, 1.5 million credits have a $15,000 pay-as-you-go value, while a Tier 2 pre-purchase plan is illustrated at $14,100, a 6% saving.

That is an official sizing example, not a quote for every tenant, currency, tax treatment, or negotiated agreement.

The Cost Management setup page is explicit that P3 and pay-as-you-go are not separate switches. A spending policy uses prepaid credits first; when they are exhausted, eligible usage continues on pay-as-you-go unless the policy limit stops further access.

P3 has three procurement constraints that Microsoft Learn states directly:

• it has a one-year term;
• automatic renewal is enabled by default;
• cancellation and exchange operations are not supported, and purchases are final.

The Microsoft Learn P3 page opened for this review does not state what happens to a remaining balance after the one-year term. Confirm that treatment in the current checkout and contract before prepaying; this article does not infer it from the term length.

Put a limit on the meter before discovery

In the Microsoft 365 admin center, go to Copilot → Cost Management → Configuration. The current setup page documents a default spending policy and additional policies scoped to security groups.

For each policy, choose a limited monthly budget rather than an unlimited one, then add an optional per-user monthly limit. When a user reaches the assigned limit, the documented behavior is loss of access to the covered agents and services until the policy limit resets on the first of the next month. That monthly reset applies to the policy limit; it is not a reset of a P3 annual balance.

Use alerts as an early warning, not as the cap itself. Keep tenant discovery off until the billing method, group scope, and enforceable limits are ready. Microsoft’s discovery documentation describes discovery as an organization-level visibility control; user eligibility belongs in security-group-scoped spending policies.

A conservative rollout for a team under ten is:

1. Create one security group for the initial Cowork users.
2. Attach the Azure subscription that finance already monitors.
3. Apply a limited monthly policy to that group and set per-user limits.
4. Add the people who should receive credit-usage alerts.
5. Let those users run real work for one billing month.
6. Review the Consumption tab by user, service, and agent before widening access or buying P3.

The Overview tab refreshes every four hours, according to the setup page. Cowork users can also enter /cost on an open task to see approximate consumption, but Microsoft says that readout is not the authoritative billing record.

A reproducible budget example

Suppose a team chooses a 20,000-credit monthly policy limit. At the documented $0.01 pay-as-you-go assumption, the modeled ceiling is:

20,000 credits × $0.01 = $200

That is planning arithmetic, not a recommendation or a promise that every action costs the same number of credits. Cowork consumption varies with the models, runtime, context, and tools used by the task. Set the actual limit from measured work and the tenant’s current rate.

Do not pre-purchase merely to make the meter feel predictable. P3 is a discounted one-year commitment layered over pay-as-you-go, not a replacement for a spending policy. First gather usage data; then compare the forecast with the current P3 checkout and its final-purchase terms.

GitHub Copilot is a different billing system

GitHub Copilot has its own seats, included allowance, and overage rules. Its license-change documentation governs additions and removals; those events do not change a Microsoft 365 Copilot spending policy or its Copilot Credit balance.

For GitHub and other coding-product overage switches, see the separate AI subscription overage guide. Keep the ledgers distinct:

• Microsoft Copilot license;
• Microsoft Copilot Credits for eligible usage-based experiences;
• GitHub Copilot license and overage.

The operating rule is simple: assigning a Microsoft Copilot seat is not the same as approving unlimited Cowork or Work IQ API spend. Configure the billing method, group scope, monthly cap, and per-user cap before the first production task.