From December 1, every Copilot Business license you sell comes with a consumption meter switched on, set by default to more than the license itself, and billed through you. This is the customer's new problem, the three sentences that explain it, the four-verb managed service that solves it, and what to charge.
Sections 1 through 4 explain what changed and why it is your customer's problem now. Read those with your leadership team. Sections 5 through 9 are the practice: the words, the service, the whiteboard, the price and how the money flows through distribution. Sections 10 through 14 are for the seller walking into the room: the talk track, the objections, the December 1 campaign and the lines that will cost you credibility. The research behind every number sits in the token economics research folder, and the pricing dials this page extends are in Model the Practice.
This playbook started with a question partners could not answer. They could explain the $30 to $40 a user they charge on top of a Microsoft 365 license: helpdesk, security, backup, patching. Asked what they did for the Copilot license, they went quiet. The three tiers in Model the Practice answered that. Now the question has changed shape, and Microsoft changed it on purpose.
The seat was the key. The credit is the meter. Microsoft built the meter, switched it on by default for your SMB customers, set the default higher than the license, and routed the bill through you. Nobody is reading it.
Everyday Copilot is still included in the seat. The new Copilot, the part that does work instead of answering questions, runs on Copilot Credits. A credit is a penny. The default lets every user spend up to $40 a month of them, and the customer did not choose that.
SET the budget and the limits. WATCH the meter. TUNE who buys what and how. PROVE it on one page. It maps onto the dials Microsoft already built into the admin center and onto the FinOps Foundation's own loop.
Credits pass through at Microsoft's price. You charge $3 to $5 a user to read the meter, with a tenant minimum, and keep the spread when you pool prepaid packs. Across 50 customers that is roughly $175,000 a year at about 85% gross margin, and it attaches to Tier 1, not Tier 3.
For twenty years the Microsoft business you sold was a seat. One price, one user, one month. In 2026 Microsoft said, in its own words, that the model is now the seat plus what the user consumes. The words below are Microsoft's, not ours. They are the corroboration a partner needs before building a practice on this.
“Evolving our business model beyond per-seat to per-seat-plus-consumption.”
Amy Hood, CFO
FY26 Q4 earnings call, July 29, 2026
“Observability of token spend and the manageability of token spend.”
Amy Hood, on what customers need next
Same call
“Advancing Copilot and agents from conversation to consumption.”
Nicole Dezen, Chief Partner Officer, to CSP partners
Microsoft blog, April 21, 2026
Partner Center said the rest on September 25, 2026, introducing the new Copilot. The partner opportunity is to “manage and optimize AI at scale”, and “FinOps for AI introduces new ways to govern costs.” The same post said partners can turn this into expanded services, differentiated software, increased consumption and deeper customer relationships. Microsoft also reports that 60% of CSP partner revenue is now tied to value-added services.
Sources: Microsoft FY26 Q4 earnings call transcript (July 29, 2026); Microsoft Official Blog, “Accelerating frontier transformation with Microsoft partners” (April 21, 2026); Partner Center announcements, September 2026. Every quote is verbatim and under fifteen words. The full source list is in section 15.
Copilot Cowork, the delegate-a-job product, starts drawing Copilot Credits. Nadella told investors in July that thousands of customers were already paying for it. The Cowork Guide covers the product; the Cowork simulator models the credits.
The FY26 Q4 call: usage-based credit consumption in customer-service agents up four times quarter over quarter. Autopilots, autonomous long-running agents, announced.
The Copilot Cowork CSP Activation Incentive recognizes partners “accelerating consumption growth.” The payout is gated on sustained monthly consumption, not on seats. See section 10.
Cowork, Code, Autopilot and frontier models all run on usage-based billing. Cost Management, spending policies, per-user limits, alerts and model routing live under Copilot in the Microsoft 365 admin center. Partner Center names FinOps for AI as the partner opportunity.
Partner Center confirms usage-based billing on by default for new Copilot Business in CSP from December 1, with the 4,000-credit default. The same day, CSP growth margin goes live on Copilot seat growth.
Partners can test the default-on experience before it reaches customers.
Pay-as-you-go by default. 4,000 credits per user per month by default. Billed through the partner's Azure plan. Eleven markets are excluded at launch, including Germany, France, India and Australia. The United States is in.
Your customer did not ask for a meter. They bought Copilot the way they buy everything from Microsoft: a price per person, per month, that finance can put in a budget. What arrives on December 1 is that price plus a ceiling they did not set, on a bill they will not see until it lands. The chart below is the first thing to draw for a business owner.
Chart A · The license you sold them versus the ceiling they got by default
Per month. Copilot Business at $21 a user, against the 4,000-credit default at $0.01 a credit. The ceiling is an exposure, not a forecast, and that is exactly the problem: nobody knows which it will be.
| Seats | License per month | Default ceiling per month | Ceiling as a multiple of the license |
|---|---|---|---|
| 50 | $1,050 | $2,000 | 1.9x |
| 100 | $2,100 | $4,000 | 1.9x |
| 300 | $6,300 | $12,000 | 1.9x |
Microsoft's own example in the October 1 announcement: 100 users can consume up to 400,000 credits a month. The $18 promotional seat price running through December 31 makes the multiple larger, not smaller.
The honest answer to “will they really spend $40?” is: some will, most will not, and nobody in the customer's building has the job of finding out which. Three things make that worse than it sounds.
Chart B · This is already happening to everyone else
The surveys partners can quote. Consumption pricing surprises are the norm, and the smallest businesses have nobody to catch them.
IDC's SMB survey, in its own words: unpredictable costs are a big red flag, and SMBs prefer transparent, credit-based pricing. That sentence is your opening.
Partners lose this conversation by making it complicated. There are three kinds of Copilot work, and three price tags. A credit is one cent. Microsoft publishes no conversion from credits to tokens, and you should never offer one.
A licensed user's own use of a standard agent is free with the seat. The bill comes from Cowork, Code, Autopilot, unlicensed and external users, autonomous runs, computer use and the GitHub harness. A partner who cannot draw that line for every agent before building it will over-quote the deal and lose it, or under-quote it and eat the difference. The rate card and the rule are verified in the Copilot Credit Planner.
We went looking for who is already selling this to small businesses. Across roughly sixty searches and thirty-five vendor pages, here is what the market looks like in October 2026.
A free 15 to 30 minute “set your spending policies” session. Several Microsoft partners are giving the first step of the service away as lead generation, with no ongoing fee behind it.
Governance and adoption by the hour. The best published example sells three monthly tiers of hours. Its scope covers telemetry reviews and says nothing about credit budgets, thresholds or re-billing.
No SMB MSP publicly re-bills Copilot Credits, prices an included-credit allowance with overage, or sells a per-agent retainer. The enterprise firms have essays and frameworks, not a priced Copilot consumption service.
Why is the market behind? Three reasons, and each one is a reason the partner wins by moving now.
When AI is billed separately, buyers prefer per-seat pricing (42.3%) over consumption (36.6%), because they want an AI cost they can budget. Microsoft bills the new Copilot by consumption anyway. The partner's product is turning the meter back into a budget. That is the service, in one sentence. Futurum, “The Pricing Split,” August 2026.
Partners asked for this drawn with big crayons. Here it is. If a seller can say these three sentences without notes, the rest of this page is detail.
The seat buys everyday Copilot. Cowork, Code, Autopilot, agents that serve people outside your license, and anything your agents do on their own run on the meter, in Copilot Credits. A credit is a penny.
Microsoft ships new Copilot Business tenants with a 4,000-credit default per user. That is up to $40 a month on top of a $21 seat. For 100 users, the license is $2,100 and the default exposure is $4,000.
Microsoft built the dials: budgets, per-user limits, alerts, model routing, reports by user, group and agent. It did not build anyone to turn them. The bill comes to us before it comes to you, so we are going to set the budget with you, watch it, tune it and hand you a receipt every month.
This is the whole managed service. Everything else in the playbook, Tier 1 to 3, AgentCare, the Agent 365 overlay, wraps around it. It maps directly onto the FinOps Foundation's Inform, Optimize, Operate loop, and onto the controls Microsoft already shipped in the Microsoft 365 admin center under Copilot, then Cost management.
SET
Onboarding, then quarterly
Agree a credit budget per tenant and per group. Lower the 4,000 default to the agreed limit. Alerts at 80% and 100%. Decide which services are allowed. Pick the funding source.
WATCH
Monthly, 1 to 2 hours a tenant
Read the meter. Top consumers, idle agents, spikes, users hitting limits, requests for more. Baseline for 30 to 60 days before you move a threshold.
TUNE
Monthly, re-plan quarterly
Steady users onto prepaid packs. Pre-purchase only at break-even. Retire idle agents. Route routine work to the cheaper model. Remove unused seats.
PROVE
One page, every month
Credits spent, by whom, on what, next to the outcome. Cost per user per month. Cost per resolved request for each agent. It feeds the QBR.
Microsoft 365 admin center: Copilot, then Cost management. Spending policies, user limits, policy alerts, credit-request routing, model profiles. Global or Billing Administrator creates; AI Administrator edits; AI Reader and Global Reader get the read-only dashboard, which is the role you give the customer's finance person.
A one-page credit budget the customer signed: per-user limit, tenant limit, allowed services, alert recipients, budget owner, review date.
Cost management reports in the admin center; the Power Platform admin center for per-agent Copilot Studio consumption; Microsoft's Analytics Hub templates for single-tenant chargeback reports. The consumption API has refused automated calls since September 2026, so this is an export and a person until Microsoft ships the supported alternative.
A meter reading: top consumers, idle agents, spikes, limit hits, requests. It becomes the first half of the PROVE page.
Capacity packs and pre-purchase plans through CSP; model profiles and request routing in Cost management; the Copilot Credit Planner for the cheapest-cover math across packs, pre-purchase and pay-as-you-go.
A funding mix the customer approved, and a list of what was retired or re-routed and what it saved.
The Insights consumption dashboards (preview as of September 2026) and the customer report the Credit Planner prints with your name on it.
The receipt. It is the artifact that makes the fourth line on the invoice feel earned, and it is the input to the QBR in Tier 1's Value Proof pillar.
If your team has ever lowered a credit limit for a customer, answered “why is our Azure bill up?” or turned off an agent nobody used, you have delivered part of this service for free. The opportunity is to name it, schedule it and put it on the invoice, the same way Model the Practice says of AgentOps.
Every MSP owner can draw the first bar from memory. The second bar is what this playbook taught. The third and fourth bars are what December 1 adds, and the difference between them is the service.
Chart C · Old math, Copilot math, and the new fourth line
Per user, per month. The top two bars you already sell. The third is Microsoft's, and it is on whether you like it or not. The fourth is what stops the third from surprising anyone.
| Line | Microsoft license | Your service | Credits (pass-through) | Credit Wrap | Per user per month |
|---|---|---|---|---|---|
| Microsoft 365 math | $22 | $35 | — | — | $57 |
| Copilot math | $21 | $12 | — | — | $33 |
| December 1, default | $21 | $12 | up to $40 | — | up to $73 |
| December 1, governed | $21 | $12 | $15 cap | $4 | $52 |
The $35 managed-services line is the midpoint of the $30 to $40 upcharge partners describe for Business Premium. The $15 credit cap and $4 Credit Wrap are the worked example in section 8, not Microsoft figures.
“The top two lines you already know. The third line is Microsoft's, and it is on whether you like it or not. The fourth line is what stops the third one from surprising you.”
Credit Wrap in Model the Practice is defined as an Azure consumption markup: buy pooled credits at CSP cost, bill at a 30% markup, earn roughly $75 to $150 a month per customer, “modest at Tier 2.” That definition was written when consumption was a side effect of a few Copilot Studio agents. Three things changed under it.
This is our synthesis, not a published norm, and it follows the shape the analysts and the MSP billing guidance converge on: a predictable fee, pass-through at Microsoft's price, a visible spread, and an optional savings share.
| Component | How it is priced | Why | Provenance |
|---|---|---|---|
| Credit Wrap floor | $3 to $5 per user per month, with a $150 to $250 per-tenant minimum | The buyer's predictable number. Covers SET, WATCH, TUNE and PROVE at one to two hours a month per tenant. The analyst finding that AI buyers want a budgetable number is the reason this is a flat fee. | Ours |
| Credits, passed through | Microsoft's price, as a separate invoice line | Never sell unlimited usage. Keep license, usage, service and labor as separate lines. The customer always sees the public rate. | MS rate; Reported billing guidance |
| Pack spread | Buy packs at $0.008 a credit, bill steady consumers at the $0.01 pay-as-you-go rate | A 20% spread that is visible and defensible: the customer pays the public rate, you carry the commitment and the pooling. Confirm pooling rules in the Azure portal before quoting it. | MS prices; Ours spread |
| Savings share, optional | 25 to 50% of verified savings from retired seats, retired agents or a pay-as-you-go to pre-purchase move, for one quarter | The telecom expense management precedent. “We only win if you save.” | Reported |
| Invoice line | Arithmetic | Per month | Who keeps it |
|---|---|---|---|
| Copilot Business licenses | 50 × $21 | $1,050 | Microsoft, less your CSP margin |
| Tier 1 AI Essentials | 50 × $12 | $600 | You (existing playbook figure) |
| Copilot Credits, budgeted | 1,500 credits a user, a $15 cap instead of the $40 default | up to $750 | Microsoft, passed through |
| Credit Wrap floor | 50 × $4 | $200 | You |
| Pack spread | 30 steady Cowork users on packs, roughly 45,000 credits a month at a $0.002 spread, about | $90 | You |
The new line is worth about $290 a month per customer at roughly 85% gross margin once the monthly read is routine, and almost all of it comes from the floor fee, not the markup. That is the opposite of how the current Credit Wrap page is written, and it is what the research supports.
Chart D · Where the fourth line's revenue comes from, across a 50-customer book
Annual, at the worked example above. The floor is predictable and attaches to every Copilot Business tenant. The spread only exists where consumption is steady enough to pool.
Compare the current Credit Wrap page's $75,000 to $90,000 a year across 50 Tier 3 customers. The floor-first structure roughly doubles it and does not wait for Tier 3.
Everything above tells you what to sell. This section is the plumbing: how a seat and a credit each get billed to an indirect partner buying through TD SYNNEX, where each dollar of margin actually comes from, what you have to set up before December 1, and a worked invoice for a 50-seat customer. It is the section to read with whoever runs your billing.
Microsoft has not published a channel margin on Copilot Credits. Every credit figure on this page is Microsoft's public price. Confirm the channel price, the invoice line and the pack pooling rules with your TD SYNNEX team before you quote credits to a customer.
A normal CSP license. TD SYNNEX bills you, you set your own price to the customer, and you earn your CSP margin on it. Since October 1, 2026 you also earn CSP growth margin on new-to-offer, seat expansion and adoption for Copilot and the other eligible workloads.
Copilot Credits are consumption, billed monthly in arrears through an Azure subscription in the CSP channel. Microsoft's partner setup guidance starts with one requirement: an Azure subscription linked to your partner billing account. For an indirect partner that subscription sits inside the TD SYNNEX relationship, so credit charges flow Microsoft → TD SYNNEX → you → the customer, the same path as the seat.
Microsoft invoices the distributor for the customer's Azure consumption and holds it responsible for payment. Microsoft's own partner guidance tells CSP partners you're responsible for your customers' Azure consumption, and the nonpayment policy makes direct-bill partners and distributors financially responsible for customer nonpayment. What you owe TD SYNNEX in turn is set by your reseller agreement with TD SYNNEX, and you should expect it to pass straight through. If a customer burns $3,000 in credits and disputes it, the invoice still arrives. That is the commercial reason to set the limits before Microsoft's default does, and it is why reading the meter is a service worth paying for rather than a favor.
| Revenue line | Who pays | How it works | Type |
|---|---|---|---|
| Seat margin | Customer, through your seat price | CSP margin plus growth margin on Copilot Business. | Recurring |
| Credits | Customer, passed through | Billed at Microsoft's price as its own invoice line. Expect little or no margin on pay-as-you-go. | Recurring, variable |
| Pack spread | Customer, at the public rate | Buy capacity packs below the pay-as-you-go rate and bill steady usage at pay-as-you-go. Only the used part of a pack is spread; an unused pack is your loss. | Recurring, conditional |
| Credit Wrap (reading the meter) | Customer | Flat $3 to $5 a user with a tenant minimum. SET, WATCH, TUNE, PROVE. | Recurring, the core of the offer |
| Sizing and agent build | Customer | Scoping Cowork and agents with the Copilot Credit Planner; building Copilot Studio agents. | One-time project |
| Agent operations | Customer | A retainer per production agent to monitor, tune and retire. AgentCare in Model the Practice. | Recurring |
| Microsoft incentives | Microsoft | Paid on sustained consumption and seat growth. Upside, not plan. | Periodic |
CSP partners set their own customer pricing, so marking up credits is technically possible. Bill at Microsoft's public rate so the customer can always check it. The revenue is the service, not the resale.
$200 for 25,000 credits a month is $0.008 a credit against $0.01. No rollover, and the licensing guide footnotes the pack as billed annually, so confirm the CSP billing frequency with TD SYNNEX. You keep the difference only on credits that actually get used, and only once pooling is confirmed in the Azure portal.
$3 to $5 a user, $150 to $250 tenant minimum. One to two hours a month per tenant. It is the line that turns a variable Microsoft meter into your MRR.
Set up the delegated admin relationship with the right roles. Global or Billing Administrator creates spending policies; AI Administrator edits them; AI Reader and Global Reader get the read-only dashboard, which is the role you give the customer's finance person.
Partner Center can hold an Azure spending budget per customer, with an email every seven days once usage reaches 80 to 100% of the figure. Two things to know: it alerts, it does not stop usage, and the tool sits in the Billing workspace of the partner Microsoft invoices, which for an indirect reseller is TD SYNNEX. Ask your TD SYNNEX team to set one for each of your Copilot Business customers. Your own hard stop is the tenant spending limit in the Microsoft 365 admin center, which can go to zero; in an emergency a partner with admin-agent rights can cancel the Azure subscription.
Microsoft publishes no multi-tenant cost view for partners, and since September 2026 the credit-consumption endpoint refuses automated calls. The monthly report is a manual export someone pulls and summarizes. Budget the hour. That is also why the service is worth paying for.
You run a scoping session with the Copilot Credit Planner. The figures are illustrative, built on Microsoft's published rates, and the arithmetic is ours.
Usage the customer agrees to:
| Invoice line | Customer pays | Your cost | You keep |
|---|---|---|---|
| 50 Copilot Business seats | $1,050 | Channel price | CSP and growth margin |
| Tier 1 AI Essentials (existing) | $600 | Labor | $600 less labor |
| Copilot Credits, about 71,000 at $0.01 | $710 | Two packs ($400 for 50,000) plus 21,000 on pay-as-you-go ($210): $610 | About $100 of spread, if both packs get used |
| Credit Wrap, 50 × $4 | $200 | One to two hours of labor | Most of the $200 |
| Agent operations retainer | — | Labor | The retainer, at the price you set |
| One-time: sizing and agent build | — | Labor | The project margin, at the fee you set |
The customer agreed to a cap, not a guaranteed spend. Start them on pay-as-you-go. Move steady usage onto packs after a 30 to 60 day baseline, because a pack you bought for usage that did not happen is your loss, not theirs. Consider a pre-purchase tier only when the baseline is 60 to 90 days old and the break-even math works: discounts run 5% to 20%, unused credits expire, and the plan is final with no cancellation or exchange. Microsoft's own documents disagree on whether it is paid up front or monthly, so ask TD SYNNEX how it invoices in CSP.
The seat pays you margin. Same as always, plus growth margin.
The credits pay you almost nothing. Pass them through at Microsoft's price. You carry the risk, so control it.
Reading the meter pays you every month. $3 to $5 a user, the line that turns credits into MRR.
Packs pay you a spread once usage is steady enough that nothing goes to waste.
Agents pay you twice: once to build, every month to operate.
Your job with TD SYNNEX is to wire the billing, size the line of credit and confirm credit pricing. Your job in the customer's tenant is to set the limits before Microsoft's default does.
There is a trap in this conversation, and partners who miss it will find themselves arguing with Microsoft's incentives. Microsoft's partner language about consumption is growth language: “accelerating consumption growth,” “a natural path to expanded consumption.” The money follows it.
| Mechanism | What it pays on | What it means for the pitch |
|---|---|---|
| Copilot Cowork CSP Activation Incentive Reported | From September 1, 2026. Reported as $50 per incremental Cowork monthly active user, capped at $12,500 per tenant, gated on 50 or more Cowork users and $2,500 or more of monthly Cowork consumption sustained through month three. The announcement is verified; the dollar mechanics come from channel press and sit behind partner sign-in. | You are paid when consumption is real and sustained. A pitch built on minimizing spend fights your own incentive. |
| CSP growth margin MS | Live October 1, 2026, on new-to-offer, seat expansion and adoption for Copilot and the other eligible workloads. | Seats still pay. Governance keeps the seats renewing. |
| Microsoft 365 Copilot specialization MS | Since July 2026, performance is measured on monthly active usage growth, not seats sold. | Usage is the badge metric now. See Designation to Specialization. |
| Partner margin on Copilot Credits | Not published anywhere we could find. | Do not quote one. The revenue is the service, not the resale. |
Spend the right credits, on purpose, with a receipt. The service is not a brake on the customer's AI. It is the thing that lets them push harder without the bill surprising anyone. Microsoft's CFO called it manageability of token spend, and the Cowork incentive only pays once a customer is consuming steadily. Governance is what makes the growth survivable, for the customer and for you.
One more reason to take it seriously: when organizations overrun on AI, 60.9% cut external contractors and consultants first. An ungoverned credit bill eats your own services line before it eats anything else.
Written for a seller or vCIO talking to an SMB owner or office manager, 30 to 300 seats, who already buys Microsoft 365 and either has Copilot or is about to. Plain words. No “FinOps,” no “tokens,” no “UBB” in the customer's hearing.
“You know how your Microsoft 365 bill has always been a flat number per person? Copilot changed that this year. The license is still flat, $21 a person. But the new stuff, the part where Copilot actually does work for you instead of answering questions, runs on a meter. Microsoft calls the units credits. A credit is a penny.
Here's the thing nobody is telling small businesses. Starting December 1, every new Copilot Business license comes with that meter switched on, and the default setting lets each person spend up to 4,000 credits a month. That's forty dollars. On top of a twenty-one dollar license. For your 50 people, that is a $2,000 a month ceiling you did not agree to.
The bill comes to us first, because we are your Microsoft partner. So we are not going to let the default run. We are going to set it with you.”
Draw the four bars from section 7. Say the three sentences from section 5. Stop talking. Let them ask what a credit buys.
“Three kinds of work, three price tags.
Asking Copilot a question in Word, Outlook, Teams: included in the license. No meter.
Telling Copilot to go do a job, like ‘build me the board pack from these six folders’ or ‘work through these forty invoices’: that runs on the meter, and a job is counted in dollars, not pennies. Microsoft's own range for a heavy user is somewhere between eighty and two hundred-odd dollars a month if nobody is watching.
An agent you build that answers your customers, or runs by itself overnight: every answer and every action is metered. A couple of pennies per answer, a nickel per action.
Our job is to make sure the second and third kinds happen on purpose.”
“Four things, every month, for $4 a person.
We SET the budget with you: a limit per person, a limit for the whole company, an alert at 80%. We WATCH the meter: who is using it, what is sitting idle, anything that spikes. We TUNE it: steady users go on the cheaper prepaid rate, unused seats and forgotten agents get turned off, routine work goes to the cheaper model. And we PROVE it: one page, once a month, that says what you spent and what you got for it.
The credits themselves are Microsoft's price, on their own line. We don't mark up the pennies. We charge for reading the meter.”
“Before December 1, let's set your limits. Thirty minutes, in your admin center, with you on the call. Then we run one month at the budget we agreed and I bring you the first page.”
| They say | You say | Backing |
|---|---|---|
| “We'll just leave the default. $40 is a ceiling, not a bill.” | “A ceiling nobody is watching becomes the bill. 78% of IT leaders got a surprise charge from this kind of pricing last year. And Microsoft turns on new metered features by default, so the ceiling grows on its own.” | Zylo 2026 SaaS Management Index; admin center auto-apply default |
| “We'll just turn the meter off.” | “You can, and for some people you should. But the meter is where the new Copilot lives: the jobs, the agents, the overnight work. Turning it off keeps you on the chatbot forever. The question is not on or off. It is who decides, and when.” | Spataro, September 25, 2026: Cowork, Code and Autopilot run on usage billing |
| “Isn't this your problem? You're the partner.” | “It is, which is why I'm here. The bill comes to us before it comes to you. We are going to govern it either way. I'd rather do it with you, with a budget you chose, than for you after the fact.” | Microsoft CSP guidance: Azure subscription linked to the partner billing account |
| “Why pay you to read a dashboard Microsoft gives us?” | “Microsoft gave you the dials. Nobody at your company has the job of turning them, and 40% of businesses your size have no full-time IT person at all. Four dollars a person buys you someone whose job it is.” | IDC SMB survey, June 2026 |
| “Can't you just put us on prepaid and save us money?” | “Not yet. Prepaid credits expire if you don't use them. We baseline you for two months first, then we move the steady users across when the math says it pays. That is part of what you're paying us to get right.” | FinOps Foundation break-even rule; pre-purchase expiry |
| “What's a credit in tokens?” | “Microsoft doesn't publish that, and anyone who gives you a number is guessing. The credit is the unit. A penny. That's the whole point: you budget in pennies, not tokens.” | Copilot Credits Guide, October 2026: no conversion published |
| “Our agents are for our own staff. Why would we pay anything?” | “If they're your licensed people using a normal agent in Teams, you don't. That's included. You pay when the agent serves customers, runs on its own, or does the heavy stuff. We'll draw that line for every agent before we build it.” | Zero-rating rule, Copilot Studio billing documentation |
Other partners are offering the setup session for free. Turn it into the on-ramp to the paid service. This is the first thing to ship, and it is sellable to every Copilot Business customer you have, this quarter.
Subject line: “Your Copilot bill changes December 1. Let's set your limit first.” Three sentences from section 5 and a link to book thirty minutes.
Become Customer Zero on the meter. Set your own limits, trip your own alert, pull your own export. The Customer Zero Starter Kit is the method.
Link the Azure billing, lower the default, set the alerts, review auto-apply, name the budget owner. The customer leaves with a signed one-page credit budget.
“That's SET. WATCH, TUNE and PROVE are $4 a person a month. Your first page arrives in thirty days.”
Everyone else's customers got the default.
Microsoft publishes no conversion, and per-task consumption varies by model, context and tools. An automated summary of the Credits Guide invented one; the actual document has none. The credit is the unit. Stop there.
One trade publication reported a $10 preset. Microsoft's own October 1 announcement says 4,000 credits, which is $40. Use Microsoft's figure, always.
Only the largest tier reaches 20%, the smallest is 5%, unused credits expire, and the FinOps rule is a 60 to 90 day baseline before any commitment. Say “we will tell you when prepaying pays,” and mean it.
That pitch fights Microsoft's incentives, which pay you on sustained consumption, and it fights the customer's reason for buying. Say “we'll make sure you spend it on purpose.” See section 10.
It did not, in so many words. It named FinOps for AI and managed services as partner opportunities, built the controls, set the default and routed the bill through you. Say that, exactly, and let the partner draw the conclusion.
The Credits Guide says Microsoft 365 Copilot became Microsoft Copilot in August 2026. Partner Center still writes “Microsoft 365 Copilot Business.” Both names are live. Use the one on the document in front of the customer.
Microsoft built the meter, switched it on, set the default above the seat, and sent you the bill. Every other partner is waiting for a dashboard. You have a process, three sentences and a price.