The short answer
Copilot Studio pay as you go costs $0.01 per Copilot Credit with no commitment. A capacity pack costs $200 a month for 25,000 credits, billed annually, and unused credits are lost at month end. The pack is cheaper only when the tenant uses more than 20,000 credits every month; below that the meter wins. A third option, the one-year Copilot Credit Pre-Purchase Plan, discounts the meter 5 to 20 percent by volume and keeps credits alive for the whole year, which makes it the cheapest choice for uneven usage from 300,000 credits a year. Every figure was read from microsoft.com, the Azure retail price list and the September 2026 Copilot Studio Licensing Guide on September 21, 2026.
The pay as you go versus capacity pack question comes up at exactly one moment: an agent has passed its pilot, someone has to pick a billing option in the Power Platform admin center, and finance wants a monthly number. Microsoft's pricing page says the two options are identical in product terms, "The only difference is the way a customer pays for the service," which is true and also the reason the decision is worth ten minutes. The wrong choice does not break anything. It just costs 25 percent more, every month, for a year.
This article works the break-even at real credit volumes, adds the two prepaid plans that only appear in the licensing guide, and then applies the result to the most common Copilot Studio deployment, an internal question-answering agent. The full rate card and purchasing options are on Copilot Studio pricing; this page is the arithmetic.
What the two options actually cost
Pay as you go is $0.01 per Copilot Credit. The Azure retail price list carries the meter as "Pay As You Go Copilot Credit" at $0.01, effective September 1, 2025, in every region; the older "Pay As You Go Message" meter at the same $0.01 dates from December 2024 and was renamed rather than repriced. Usage bills in arrears at the end of each month to an Azure subscription linked to the environment. There is no minimum, no term and, according to Microsoft Learn, no enforcement: "With pay-as-you-go, enforcement doesn't apply because overage is billed to your Azure subscription."
A capacity pack is $200 per month for 25,000 Copilot Credits. The pricing page prices it that way and the licensing guide adds two terms that change the comparison: the pack is "$200 per credit pack/month (billed annually)" and "Unused credits do not roll over to the next month." At full use a pack works out to $0.008 per credit, 20 percent below the meter. At half use it is $0.016, 60 percent above it. The pack is bought through the Microsoft 365 admin center and needs no Azure subscription on its own.
Copilot Studio pay as you go vs capacity packs: the break-even table
The break-even is 20,000 credits a month, because $200 divided by 20,000 is $0.01. Every row assumes steady usage; the uneven case is handled in the next section. Pack counts are rounded up, because you cannot buy four fifths of a pack.
| Credits used per month | Pay as you go | Packs needed | Pack cost per month | Pack rate per credit used | Cheaper option |
|---|---|---|---|---|---|
| 10,000 | $100 | 1 | $200 | $0.020 | Pay as you go, by $100 |
| 20,000 | $200 | 1 | $200 | $0.010 | Even |
| 25,000 | $250 | 1 | $200 | $0.008 | Pack, by $50 |
| 30,000 | $300 | 2 | $400 | $0.013 | Pay as you go, or 1 pack plus $50 of metered overage |
| 50,000 | $500 | 2 | $400 | $0.008 | Pack, by $100 |
| 100,000 | $1,000 | 4 | $800 | $0.008 | Pack, by $200 |
| 300,000 | $3,000 | 12 | $2,400 | $0.008 | Pack, by $600 |
| 1,000,000 | $10,000 | 40 | $8,000 | $0.008 | Pack, by $2,000 |
Two things stand out. First, the pack advantage is capped at 20 percent no matter how large the tenant gets, because packs have no volume tiers. Second, the 30,000 row shows the mixed configuration Microsoft itself recommends: buy packs for the base load and let a linked meter absorb the rest. Microsoft Learn describes it as prepaid credits used first, then "any usage beyond the prepaid capacity amount is automatically billed at the per-credit pay-as-you-go rate" with "no service interruption." Rounding up to the next pack for a small overage is the most common way to overpay.
What if usage is uneven month to month?
Uneven usage is where packs lose and the pre-purchase plans win, because pack credits die at month end and the pack count is fixed for the year. Take a tenant that uses 10,000 credits a month for six months and 40,000 for the other six, 300,000 credits a year. On pay as you go that is $3,000. Holding two packs all year to cover the peak is $4,800. Holding one pack plus a meter for the overage is $2,400 for the packs plus $900 of overage, $3,300, and the quiet months still waste 15,000 credits each.
The Copilot Credit Pre-Purchase Plan, added in October 2025 and documented only in the licensing guide, prices the same 300,000 credits at tier 1, a 5 percent discount, for $2,850 up front. The credits last the full year, so quiet months and busy months draw from the same pool, and "If usage exceeds the available number of credits, customers can purchase additional Copilot Credits or be billed on a pay-as-you-go basis." The tiers run 5 percent at 300,000 credits, 6 at 1.5 million, 7 at 3 million, 8 at 15 million, 10 at 30 million, 12 at 75 million, 14 at 150 million, 17 at 225 million and 20 at 300 million. Unused credits expire at the end of the annual term.
The Microsoft Agent Pre-Purchase Plan, added in February 2026, is the same idea in a different unit: Agent Commit Units worth $1 each, equal to 100 Copilot Credits, at 5 percent off for 20,000 ACUs, 10 percent for 100,000 and 15 percent for 500,000, spendable on Copilot Studio and Microsoft Foundry from one pool. Its entry point is $19,000 for 2,000,000 credits, so it is a plan for tenants already running several agents. Both prepaid plans count toward a Microsoft Azure Consumption Commitment, which is worth knowing if your Azure agreement has one to burn down.
| Annual usage pattern | Pay as you go | Packs sized to the peak | Packs sized to the base plus meter | Copilot Credit Pre-Purchase Plan |
|---|---|---|---|---|
| Steady 25,000 a month (300,000 a year) | $3,000 | $2,400 | $2,400 | $2,850 |
| Six months at 10,000, six at 40,000 (300,000 a year) | $3,000 | $4,800 | $3,300 | $2,850 |
| Steady 125,000 a month (1.5 million a year) | $15,000 | $12,000 | $12,000 | $14,100 at tier 2 |
| Seasonal, 50,000 for nine months and 350,000 for three (1.5 million a year) | $15,000 | $33,600 | $13,800 | $14,100 |
The last row is the one to remember. A seasonal tenant that sizes packs to its peak pays more than double the meter. Sizing packs to the base and metering the peak is the cheapest configuration in that row, and the prepaid plan is within $300 of it with less to manage. Steady tenants should buy packs. Everyone else should either meter or prepay for the year.
What happens if you pick packs and run out?
Without a linked meter, Microsoft switches your agents off. The enforcement policy on Microsoft Learn applies to "all tenants operating under the Copilot Studio prepaid capacity model" and is triggered "when a tenant reaches 125% of their prepaid capacity." The action is blunt: "Custom agents are disabled. Disabling an agent doesn't interrupt an ongoing conversation. All subsequent attempts to invoke the agent are rejected until capacity is increased or reset." End users see "This agent is currently unavailable. It has reached its usage limit."
Agent flows are cut off earlier. Their enforcement starts at 100 percent of prepaid capacity, not 125: "When a tenant's prepaid Copilot Studio capacity is fully consumed, new agent flow runs are blocked." The parent agent keeps answering, runs already in progress finish, and the block lifts when the monthly credits renew. So a pack-only tenant that budgets tightly can lose its automations in the last week of every month while the chat side keeps working, which is a confusing failure to diagnose if nobody has read that page.
The fix is the same as the cost fix: link an Azure subscription and a pay as you go billing policy behind the packs. Microsoft Learn is explicit that "You must have pay-as-you-go billing active as a safety net" for continuity. Admins can also cap individual agents under Licensing, Copilot Studio, Manage Agents in the Power Platform admin center, so one busy agent cannot drain the tenant pool for the rest.
Applying it to an internal Q&A agent
For an internal agent that answers employee questions from SharePoint, OneDrive and Teams content, each answer costs 12 credits: 10 for tenant graph grounding and 2 for the generative answer. That is Microsoft's own example in the billing rates article. For 200 employees who do not hold a Microsoft 365 Copilot license, asking five questions a day over 22 working days, that is 264,000 credits a month. On the meter it is $2,640. In packs it is 11 packs, $2,200, or $2,455 a month on the pre-purchase plan at the 7 percent tier. Per employee, $11 to $13.20 a month.
At ten questions a day the same 200 people consume 528,000 credits: $5,280 metered, 22 packs at $4,400, $22 to $26.40 a head. The crossover with a flat $20 per seat search product sits at roughly eight grounded questions per person per day, and it moves lower as soon as the agent uses actions (5 credits each), agent flows (13 per 100 actions) or a reasoning model (10 credits per 1,000 tokens on top of the feature rate). Employees who already carry the $30 Microsoft 365 Copilot seat are billed no credits for internal agents at all, within fair use, which is the strongest argument for Copilot Studio in a tenant that has already licensed Copilot for everyone.
Voice agents follow the same meter at much higher rates: 10 credits a minute for classic orchestration, 35 for generative AI voice and 75 for premium. A generative voice agent handling 2,000 five-minute calls a month bills 350,000 credits, $3,500 metered or 14 packs at $2,800, before any actions it takes. Teams whose whole requirement is that the phone gets answered and the appointment gets booked usually compare that figure with a flat-rate AI receptionist rather than sizing credit packs for it.
Which should you choose?
Choose pay as you go for any pilot, for any tenant under 20,000 credits a month, and for the overage safety net behind every other option. It is the only configuration that never switches an agent off.
Choose capacity packs when monthly usage is steady and predictably above 20,000 credits, size them to the base load rather than the peak, and link a meter behind them. Remember the licensing guide's terms: billed annually, no rollover.
Choose the Copilot Credit Pre-Purchase Plan when annual usage is at least 300,000 credits and the month-to-month pattern is uneven. The discount is smaller than a fully used pack's, but the credits survive the whole year and the plan burns down an Azure consumption commitment.
Choose a per-seat product instead when the job is not an agent at all but finding answers across company systems, the questions run past eight a day per person, or the content lives outside the Microsoft Graph in Slack, Google Drive, Notion, Confluence or Jira. Copilot Studio grounds on the Graph; everything else has to be brought into it first. InSearch indexes those sources directly, answers with a citation to the source document, enforces each person's permissions at query time, and costs $20 per seat per month with no credit meter, no pack count and no 125 percent cutoff. The choice between building an agent and buying an index is laid out in Copilot Studio alternatives, and the licensing overlap with the $30 seat in Copilot Studio vs Microsoft 365 Copilot licensing.
Frequently asked questions
Is Copilot Studio pay as you go cheaper than a capacity pack?
Below 20,000 credits a month, yes: $0.01 per credit on the meter beats $200 for a pack you do not fill. Above 20,000 the pack is cheaper, reaching $0.008 per credit at full use. Because pack credits do not roll over and the pack is billed annually, the comparison has to hold every month, not on average.
Do Copilot Studio capacity pack credits roll over?
No. The September 2026 Copilot Studio Licensing Guide states "Unused credits do not roll over to the next month." Credits bought through the Copilot Credit Pre-Purchase Plan last for the one-year term instead, and unused credits expire at the end of that term.
Can you combine capacity packs with pay as you go?
Yes, and Microsoft recommends it. Prepaid credits are consumed first, then overage bills automatically to the linked Azure subscription at $0.01 per credit with no service interruption. Microsoft Learn calls the pay as you go policy a "safety net" and notes that enforcement does not apply to environments billed that way.
Does Copilot Studio pay as you go require an Azure subscription?
Yes. The meter bills to an Azure subscription linked to the Power Platform environment through a billing policy, and the pricing page notes that an Azure subscription is required to use agents on the pay as you go and pre-purchase cards. Capacity packs alone can be bought in the Microsoft 365 admin center without one.
How many Copilot Credits does one question use?
A generative answer is 2 credits; add 10 if the agent uses tenant graph grounding, for 12 in total, about $0.12 on the meter. Agent actions add 5 each, agent flows 13 per 100 actions, and reasoning models add 10 credits per 1,000 tokens on top. Users licensed for Microsoft 365 Copilot are billed no credits for internal agents within fair usage limits.