On October 1, 2026, Microsoft told its resellers that new Microsoft 365 Copilot Business licenses sold through CSP carry usage-based billing by default from December 1. Each user arrives with a preset limit of 4,000 Copilot Credits a month.
We priced that default against the seat it sits on. The question concerns every CFO and CIO who buys Copilot through a reseller: who sets the agent budget, and on what basis?
What Microsoft changed
The Partner Center announcement states that "Pay-as-you-go will be the default billing configuration." It names Copilot Cowork, Work IQ APIs and GitHub Copilot Harness among the eligible experiences. New licenses "include the Azure subscription setup needed for usage-based billing."
The scope is narrow. It covers new purchases of Copilot Business through CSP, standalone or in bundles. Copilot Business is "available only to existing Microsoft 365 customers with an eligible Business plan," the plans Microsoft recommends for businesses with fewer than 300 users. The announcement does not name existing licenses or enterprise agreements.
The date moved. The change was "previously communicated as November 2, 2026." Partner Center sandboxes open on November 2, the original start date. Resellers get 29 days of testing before the default reaches buyers.
Eleven markets are excluded at launch: Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain. Microsoft does not say whether availability follows the customer's country or the tenant's. In our reading, a US group whose French or German subsidiaries buy through local resellers may run two billing regimes in December.
What the default cap is worth
Microsoft's Copilot Credits Guide, dated October 2026, prices the pay-as-you-go meter at "$0.01/Copilot Credit." At that rate, the default cap is $40 per user per month. The same guide states that reseller prices "are determined by the reseller," so a CSP invoice can differ.
Microsoft's pricing page lists Copilot Business at $21 per user per month on an annual plan, and $25.20 month to month. A promotion cuts the annual price to $18 for the first year, on offers taken by December 31, 2026. The default cap is 1.9 times the list seat, 2.2 times the discounted seat and 1.6 times the monthly seat.
Microsoft gives its own example: 100 users "could consume up to 400,000 Copilot Credits per month." At $0.01, that is a $4,000 monthly ceiling against $2,100 of seats at list. Over a year, $48,000 of metered ceiling sits beside $25,200 of licenses.
In units of work, the same cap is modest. The guide estimates a light Cowork task at 100 to 300 credits, a medium task at 300 to 700 and a heavy task above 700, as "rough planning estimates." 4,000 credits buy 5 to 13 medium tasks per user per month, or fewer than 6 heavy ones.
Both readings hold. In dollars, the default is high against the seat. In work, it is thin against an agent built for multi-step jobs. Microsoft set it without knowing which of your users runs which task.
The default cap is a budget Microsoft wrote for you, at 1.9 times the list seat price. It stops runaway spend. It does not decide what the spend is for. Hikari Blue · operator note
Which workflow changes
Seat spend is decided at purchase, in procurement. Metered spend is decided daily by users, inside a limit set in the Microsoft 365 admin center. Budget authority moves from the purchase order to a configuration screen.
The cap is a real control. When users hit a limited monthly budget, Microsoft's admin documentation states that "they lose access to agents and services for the rest of the month" until credits reset. Admins can adjust the limit, scope policies to groups and choose which services draw credits.
Two defaults pull the other way. The billing overview states that "Auto-apply new services" is "enabled by default for spending policies," and Microsoft "will add more agents and services over time." New spending policies also start with "All users" selected. Microsoft documents both as defaults of every spending policy, with no restriction to Copilot Business.
Today the metered list covers Cowork, advanced work in SharePoint and OneDrive, the Work IQ API, Copilot Managed Runtime and Teams Phone Agent. With the default on, each new service draws on an existing budget without a review.
Incentives are explicit. The reseller announcement says "Early usage can create a natural path to expanded consumption, upsell conversations, and the Copilot Cowork activation incentive." Microsoft's September notice describes that incentive as a reward for "driving customer adoption and usage of Copilot Cowork."
What management decides before December 1
CFOs: set the limit from a workflow budget, not from the default. Name the tasks agents will run, apply Microsoft's per-task ranges, and cap at that figure plus a stated margin. Leaders write the number. Laggards inherit it.
CIOs: turn off Auto-apply new services on every policy that funds production work. Add each new service by decision, with a named owner. Scope policies to groups. Grant finance a read-only reporting role, which Microsoft's setup guide provides.
Boards: the NIST AI Risk Management Framework asks that potential costs of AI errors or system functionality, "including non-monetary costs," be "examined and documented" (MAP 3.2). A vendor preset is not that record. Keeping it, across vendors, is the job of an AI operating layer.
What could prevent value capture
Estimates come first. The per-task ranges are Microsoft planning figures, not measurements of your work. Microsoft also writes that its spending "recommendations and policy requirements may evolve over time." A budget set in November needs a review date in January.
Price comes second. The $0.01 rate is Microsoft's published meter, and reseller pricing can differ. Ask the CSP for the credit rate in writing before December 1, alongside the seat price.
Which workflows will our agents run in December, what is each worth, and who approved the credits each may spend?
Carry one number into every monthly review: metered Copilot Credit spend divided by seat spend, by spending policy, beside tasks completed. At the default cap and list price, that ratio reaches 1.9. Whatever its level, the review should say what the spend bought.
- Microsoft Partner Center (October 1, 2026). Update: Usage-based billing is default on for new Microsoft 365 Copilot Business licenses starting December 1, 2026. October 2026 announcements, page updated October 5, 2026. Primary source for: the December 1, 2026 effective date, "previously communicated as November 2, 2026"; new Copilot Business licenses purchased in CSP, "including standalone offers and bundles"; "Pay-as-you-go will be the default billing configuration"; Copilot Cowork, Work IQ APIs and GitHub Copilot Harness; the default spending limit of "4,000 Copilot Credits per user per month, which can be adjusted by admins"; the 100-user example of up to 400,000 Copilot Credits per month; the eleven markets where the change is initially not available; sandbox availability on November 2; new licenses "include the Azure subscription setup"; "Early usage can create a natural path to expanded consumption, upsell conversations." learn.microsoft.com, Partner Center announcements, October 2026
- Microsoft Partner Center (September 10, 2026). New incentives for Microsoft Copilot Cowork adoption. September 2026 announcements. Primary source for: the Copilot Cowork CSP Activation Incentive, launched September 1, 2026, rewarding partners for "driving customer adoption and usage of Copilot Cowork." Same page, Office LTSC 2021 end of support (September 15, 2026): Microsoft 365 Business Premium and Business Standard as the upgrade paths for "Businesses with fewer than 300 users." learn.microsoft.com, Partner Center announcements, September 2026
- Microsoft Learn (updated October 2, 2026). Usage-Based Billing and Cost Management for Copilot Credits. Primary source for: the services managed by usage-based billing (Cowork, advanced work in SharePoint, advanced work in OneDrive, Work IQ API, Copilot Managed Runtime, Teams Phone Agent); "Microsoft will add more agents and services over time"; "The Auto-apply new services setting is enabled by default for spending policies"; read-only reporting roles for finance stakeholders. learn.microsoft.com, usage-based billing overview
- Microsoft Learn (updated October 2, 2026). Managing AI experiences enabled by usage-based billing. Primary source for: "By default, All users is selected"; "When users hit the limit, they lose access to agents and services for the rest of the month until credits reset on the first of the month"; limited and unlimited monthly budgets; optional per-user limits; "recommendations and policy requirements may evolve over time." learn.microsoft.com, managing usage-based billing
- Microsoft Learn (updated October 2, 2026). Set up usage-based billing for Copilot Credits. Primary source for: reader-based roles that "provide read-only access to consumption information"; the "Don't limit monthly spending" and "Limit monthly spending" options; the default setup that "targets your entire organization and all users." learn.microsoft.com, usage-based billing setup
- Microsoft (October 2026). Microsoft Copilot Credits Guide, PDF. Primary source for: the pay-as-you-go meter at "$0.01/Copilot Credit" (page 4); Cowork task estimates of 100 to 300 credits (light), 300 to 700 (medium) and more than 700 (heavy), "rough planning estimates" (page 7); "Prices for licenses acquired through Microsoft resellers are determined by the reseller" (page 26). microsoft.com, Copilot Credits Guide
- Microsoft (read October 6, 2026). Microsoft 365 Copilot Business pricing page. Primary source for: $21.00 per user per month originally, $18.00 per user per month paid yearly; "This discount offer is available between July 1, 2026, and December 31, 2026"; "promotional pricing applies to the first year only"; $25.20 per user per month on a monthly subscription; "The Microsoft 365 Copilot Business add-on is available only to existing Microsoft 365 customers with an eligible Business plan." microsoft.com, Copilot Business pricing
- National Institute of Standards and Technology (2023). Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, Table 2, page 27. Primary source for: MAP 3.2, potential costs, "including non-monetary costs," which result from expected or realized AI errors or system functionality, are "examined and documented." nist.gov, NIST AI 100-1
- Our arithmetic, at Microsoft's published $0.01 pay-as-you-go rate. Cap per user: 4,000 times $0.01 is $40 per month. Against the seat: 40 divided by 21 is 1.90; 40 divided by 18 is 2.22; 40 divided by 25.20 is 1.59. For 100 users: 400,000 times $0.01 is $4,000 per month; 100 times $21 is $2,100 per month; 12 times $4,000 is $48,000; 12 times $2,100 is $25,200. Cowork tasks per user per month at the cap: 4,000 divided by 700 is 5.7 and 4,000 divided by 300 is 13.3 (medium); 4,000 divided by 700 is under 6 (heavy, above 700 credits each). Slip: November 2 to December 1, 2026 is 29 days. These are ceilings and planning estimates, not forecasts of consumption: actual spend depends on usage, on the limit each tenant sets, and on the reseller's credit price.
The Hikari Blue team · Austin, October 2026