Contents
- Fast answer
- Quick facts
- What this covers
- Why it matters
- Where to go next
- Outcomes
- Step by step
- What P3 actually is, and why people cannot find it
- What one CCCU is worth
- Buying it, and who is actually allowed to
- What Microsoft will not tell you about tiers
- All purchases are final
- When a pre-purchase plan is the wrong move
- At a glance
- Mistakes to avoid
- FAQ
- Related guides
Fast answer
P3 is the Copilot Credit Pre-Purchase Plan, and the first thing to know is where it lives: it is an Azure reservation bought in the Azure portal under Reservations, not a Microsoft 365 purchase. It is a one-year, pay-up-front commitment of commit units bought at discounted tiers in your purchasing currency, and Microsoft's stated rule is that the more you buy the greater the discount. The unit is the Copilot Credit Commit Unit, or CCCU, and its value is fixed against retail cost in US dollars. Microsoft's own example: if Microsoft Copilot Studio generates a retail cost of $100 based on Copilot Credit usage, then 100 CCCUs are consumed. So one CCCU pays down one dollar of qualifying retail cost. The plan pays down eligible usage automatically for its one-year term or until the units run out, renews automatically by default, and cannot be split or merged. Cancellations and exchanges are not supported and all purchases are final.
Facts last verified 2026-09
Quick facts
- P3
- Copilot Credit Pre-Purchase Plan (read 2026-09-01)
- Instrument
- Azure reservation, bought in the Azure portal under Reservations
- CCCU
- Copilot Credit Commit Unit. 100 CCCUs cover $100 of retail cost
- Term
- One year, pay up front
- Renewal
- Configured to renew automatically by default
- Roles required
- Owner or Reservation Purchaser; EA needs the Reserved Instances policy enabled
- Billing
- Separate invoice line item. Not deducted from Azure Prepayment
- Scopes
- Resource group, subscription, shared, or management group
- Changeable after purchase
- Scope, and who can view or manage it
- Cancellations and exchanges
- Not supported. All purchases are final
- Split or merge
- Not supported
- Tier sizes and discounts
- Not published by Microsoft in this documentation
- Copilot Credit PAYG rate
- Not published. $0.01 appears only as an assumption in an example
On this page
What this page covers
A comparison visitor should understand the tradeoff, the best-fit scenario, and the next diagnostic tool to confirm the choice.
- 01What P3 actually is
- 02What one CCCU is worth
- 03Buying it, and who is allowed to
- 04What Microsoft will not tell you about tiers
- 05All purchases are final
- 06When a pre-purchase plan is the wrong move
Why does this matter now?
Two things make this SKU easy to get wrong. The first is that it is an Azure reservation, so the person who needs to buy it is an Azure subscription owner or reservation purchaser, not whoever administers Microsoft 365, and on an Enterprise Agreement the Reserved Instances policy option has to be enabled first. Teams routinely go looking for it in the wrong portal. The second is that it is final. Azure reservations usually offer some exchange or cancellation path; this one explicitly does not. A commitment sized from a guess is a commitment you keep.
Internal path
Where to go next from this page
These links are part of the A8gent learning and conversion path. Use them to move from concept, to diagnosis, to workflow build, to course.
What you should be able to do after this
- Understand what a CCCU is worth
- Buy it in the right portal with the right role
- See what Microsoft does and does not publish about tiers
- Avoid a purchase you cannot cancel
How do you do it, step by step?
1. Confirm you are buying a reservation, not a licence
Purchase happens in the Azure portal under the Reservations service, selecting Copilot Credit Pre-Purchase Plan on the Purchase reservations page. It is billed as a separate charge and appears as its own line item on the invoice. Microsoft is explicit that charges are not deducted from the enrolment's Azure Prepayment balance and are not charged as overage.
2. Get the right role in place first
For an Azure subscription you need the owner role or the reservation purchaser role. For an Enterprise Agreement subscription the Reserved Instances policy option must be enabled by an EA administrator. For a Cloud Solution Provider subscription, the partner either buys on the customer's behalf or grants the customer permission to buy their own reservations. Sorting this out is usually the longest part of the process.
3. Estimate usage in dollars, then convert to CCCUs
Because one CCCU pays down one dollar of qualifying retail cost, the sizing question is simply what your annual Copilot Credit retail spend will be. Take measured monthly consumption, multiply by twelve, and that is your CCCU target. Do not try to work backwards from a credit count, because the retail rate per Copilot Credit is not something Microsoft publishes as a committed figure.
4. Choose the scope deliberately
The purchase flow asks for a scope: a single resource group, a single subscription, a shared scope covering eligible subscriptions in the billing context, or a management group scope. Scope decides which usage the plan can pay down. Scope and ownership can be changed after purchase, which is one of the very few things about this reservation that is adjustable, so it is worth knowing that the irreversible part is the size, not the scope.
5. Decide about auto-renewal before you forget
Microsoft states plans are configured to renew automatically by default at the end of the one-year term. On a purchase you cannot cancel, a default-on annual renewal deserves a calendar reminder at month ten rather than a discovery in month thirteen. Set the reminder at purchase time.
What P3 actually is, and why people cannot find it
P3 is short for the Copilot Credit Pre-Purchase Plan, and the single most useful fact about it is architectural rather than financial: it is an Azure reservation. Microsoft documents it in the Azure Cost Management and Billing section, under reservations, and you buy it in the Azure portal by navigating to the Reservations service and selecting Copilot Credit Pre-Purchase Plan on the Purchase reservations page. It is not a Microsoft 365 licence, it is not bought in the Microsoft 365 admin centre, and it does not appear alongside Copilot Studio's monthly capacity packs.
Microsoft's own definition of the instrument: pre-purchase plans are commit units bought at discounted tiers in your purchasing currency for a specific product, and the more you buy the greater the discount. Purchased commit units pay down qualifying costs in US dollars. The plan runs a one-year term, automatically applies your commit units to eligible Copilot Credit usage during that term or until the units run out, and requires no redeployment or reassignment to start working.
Billing behaves like a reservation too, with one consequence worth flagging to finance. Microsoft states that the payment method of the subscription is charged the upfront costs, that charges are not deducted from the enrolment's Azure Prepayment balance and not charged as overage, and that the pre-purchase plan is billed as a separate charge appearing as its own line item on the invoice. If you were expecting it to draw down an existing Azure commitment, it does not.
The reason this SKU generates search traffic under the name P3 rather than its full name is that the documentation URL and page title both carry it while the body text uses the descriptive name throughout. If you have been handed the string P3 by a Microsoft representative or a procurement document and cannot find a product by that name, this is it.
What one CCCU is worth
The unit is the Copilot Credit Commit Unit, abbreviated CCCU, and Microsoft defines its value by worked example rather than by rate: if Microsoft Copilot Studio generates a retail cost of $100 based on Copilot Credit usage, then 100 Copilot Credit CUs are consumed. One CCCU therefore pays down one US dollar of qualifying retail cost. That is a clean definition and it is the only firm number on the whole page.
Note carefully what the unit is anchored to. It is anchored to retail cost in US dollars, not to a count of Copilot Credits, even though you buy the plan in your own purchasing currency. That indirection is deliberate and it matters for sizing: the right way to size a plan is to forecast your annual Copilot Credit retail spend in dollars and buy that many CCCUs. Trying to size from a credit count requires knowing the retail rate per credit, which Microsoft does not commit to.
That last point deserves emphasis because it is the most likely place for a bad number to enter a budget. Microsoft's sizing example says, in its own words, assuming the pay-as-you-go rate for Copilot Credit to be $0.01, and then builds an illustration on that assumption. It is an assumption stated inside an example, not a published rate. Any calculation that turns a credit count into dollars using $0.01 is inheriting an assumption from a hypothetical, and should be labelled as such wherever it appears.
The corollary is that a CCCU does not float. Whatever a Copilot Credit turns out to cost at retail, a CCCU covers a dollar of it. That makes the instrument straightforward to reason about even without a published per-credit rate: you are pre-buying dollars of consumption at a discount, not pre-buying credits at a fixed rate.
Buying it, and who is actually allowed to
The role requirements are the most common blocker and they are worth checking before anyone builds a business case. For an Azure subscription you need either the owner role or the reservation purchaser role. For an Enterprise Agreement subscription the Reserved Instances policy option must be enabled, and enabling it requires an EA administrator. For a Cloud Solution Provider subscription, the partner either buys the reservation on the customer's behalf or grants the customer permission to buy their own.
None of those roles typically sits with the person who owns Copilot Studio. The Copilot Studio owner is usually a Power Platform administrator or a business application owner; the purchaser is an Azure billing role. In practice this means the purchase involves at least two people and one internal permission request, which is worth starting early because the roles are not usually granted casually.
The purchase flow asks for a scope, and the options are the standard reservation set: single resource group, single subscription, shared scope covering eligible subscriptions in the billing context, or management group scope covering subscriptions in both the management group and the billing scope. Scope determines which usage the plan can pay down, so a plan scoped to one subscription will sit unused while another subscription accrues retail charges. For most organisations buying centrally, shared scope is the intent.
Two things remain adjustable after purchase and it is worth knowing which. Microsoft states you can update the reservation scope and update who can view or manage the reservation. Everything about the size is fixed. So a mis-scoped plan is recoverable and a mis-sized plan is not, which is the right way round but only if you know it going in.
What Microsoft will not tell you about tiers
The pre-purchase plan is sold in discounted tiers where larger commitments earn larger discounts, and Microsoft's documentation does not publish either the tier sizes or the discount percentages. The screenshot in the article shows discount tiers and term lengths, but the article's only numeric treatment is a hypothetical, and it flags itself as one twice over.
Here is that hypothetical in full, because the framing is the point. Microsoft supposes you expect to consume 1,500,000 Copilot Credits with custom agents in Copilot Studio. It then says, assuming the pay-as-you-go rate for Copilot Credit to be $0.01, this will cost $15,000 at the pay-as-you-go rate. It continues: by purchasing a Tier 2 15,000 CU pre-purchase plan, let us say the cost of that tier is $14,100, giving a 6 percent saving. Two assumptions and a let-us-say, chained. Nothing in that paragraph is a price.
So the honest position on discounts is that the real tier list is visible in the Azure portal at purchase time and nowhere else we can verify. Any specific savings range you find published elsewhere is third-party, derived either from a portal screenshot at one moment or from the hypothetical above. We are not repeating a range, because we cannot source one to Microsoft.
There is also a stacking caveat that will change the number you actually see. Microsoft notes that pre-purchase plan discounts do not combine with other discounts you might have, and that where you hold additional discounts the pre-purchase plan discount is applied independently, which may result in a lower effective discount rate than the listed tier percentage. Organisations with negotiated Microsoft pricing should therefore expect the headline tier discount to overstate their benefit, and should factor existing discounts in when estimating savings.
All purchases are final
Azure reservations generally come with some escape hatch, whether an exchange for a different reservation or a cancellation with a fee, and that expectation is exactly what makes this SKU dangerous. Microsoft's statement is unambiguous: cancel and exchange operations are not supported for Copilot Credit Pre-Purchase Plans, and all purchases are final. There is no published refund path, no exchange into another reservation type and no partial return.
Nor can you restructure one after the fact. Microsoft states you cannot split or merge a Copilot Credit Pre-Purchase Plan. With most reservation families, splitting is the standard remedy for a commitment that turns out to be scoped or sized against the wrong shape of consumption. That remedy is not available here, so the sizing decision made at purchase is the sizing you live with for the full year.
Renewal is the compounding risk. Microsoft states plans are configured to renew automatically by default at the end of the one-year term. Combine default-on annual renewal with no cancellation path and a plan sized on a bad estimate renews itself into a second year unless somebody actively intervenes. The mitigation is trivial and almost never done: put a calendar reminder at month ten, owned by a named person, at the moment of purchase.
The behavioural implication is to buy small first. Commit units pay down usage until the term ends or the units run out, and running out simply means falling back to normal billing. An undersized plan therefore costs you a missed discount. An oversized plan costs you the money. Given an asymmetry that sharp, the rational first purchase is conservative, informed by measured consumption, and revisited at renewal rather than optimised on day one.
When a pre-purchase plan is the wrong move
If you cannot produce twelve months of measured Copilot Credit consumption, or a very well-founded forecast, this is not the instrument to start with. Copilot Studio's published monthly capacity pack is $200 a month for 25,000 Copilot Credits, and its virtue here is not price but reversibility: you can stop buying it. Three months of that data is worth more than any discount tier, because it converts the sizing question from a guess into arithmetic.
If your Copilot Credit consumption is about to change shape, wait. Anyone whose AI Builder workloads are moving onto Copilot Credits on 1 November 2026 is in exactly that position, and Microsoft publishes no conversion ratio to forecast with, saying only that rates are different for each scenario. Committing a year of spend immediately before a currency migration you cannot yet price is the clearest case for holding off.
If the purchasing roles are not in place and cannot easily be arranged, the plan is not available to you in practice regardless of the business case. The owner or reservation purchaser role, or an EA administrator enabling the Reserved Instances policy, is a hard prerequisite rather than a formality, and organisations with tight Azure governance can take weeks to grant it.
And if your consumption is genuinely small, the discount does not justify the irreversibility. A pre-purchase plan trades flexibility for a percentage. On a modest annual spend that percentage is a modest number of dollars, and it is being paid for with a commitment that cannot be cancelled, exchanged, split or merged. The discount has to be worth more than the option to change your mind, and below a certain scale it simply is not.
At a glance
Copilot Credit Pre-Purchase Plan (P3), read from learn.microsoft.com/en-us/azure/cost-management-billing/reservations/copilot-credit-p3 on 1 September 2026
| Attribute | Published position | Note |
|---|---|---|
| Product name | Copilot Credit Pre-Purchase Plan | Documented under the short name P3 |
| Purchase location | Azure portal, Reservations service | Not the Microsoft 365 admin centre |
| Unit | Copilot Credit Commit Unit (CCCU) | Bought at discounted tiers in your purchasing currency |
| CCCU value | 1 CCCU pays down $1 of qualifying retail cost | Microsoft example: $100 retail cost consumes 100 CCCUs |
| Term | One year | Plan applies units until term end or units run out |
| Auto-renewal | On by default | Configurable at purchase |
| Azure subscription role | Owner or Reservation Purchaser | Required to purchase |
| Enterprise Agreement | Reserved Instances policy option must be enabled | Requires an EA administrator |
| CSP | Partner buys on behalf, or grants customer permission | Two documented routes |
| Invoice treatment | Separate line item, charged to the subscription payment method | Not deducted from Azure Prepayment, not charged as overage |
| Scope options | Resource group, subscription, shared, management group | Scope is changeable after purchase |
| Cancellation | Not supported | All purchases are final |
| Exchange | Not supported | All purchases are final |
| Split or merge | Not supported | Explicitly stated |
| Discount stacking | Does not combine with other discounts | Applied independently, may give a lower effective rate |
| Tier sizes | Not published | Visible in the Azure portal at purchase |
| Tier discount percentages | Not published | Article shows only a hypothetical 6 percent in an example |
| Copilot Credit pay-as-you-go rate | Not published | $0.01 stated as an assumption within an example |
| Local currency prices | Not published | Plans are bought in your purchasing currency; no rate card published |
What mistakes should you avoid?
- Looking for the Copilot Credit Pre-Purchase Plan in the Microsoft 365 admin centre
- Starting the purchase without owner or reservation purchaser rights on the subscription
- Sizing a one-year commitment from an estimate rather than measured consumption
- Assuming an Azure reservation can be cancelled or exchanged, when this one cannot
- Expecting the tier discount to stack with existing discounts
- Leaving auto-renewal at its default and not diarising the term end
FAQ
- What does CCCU stand for?
- Copilot Credit Commit Unit. Microsoft's example is that if Microsoft Copilot Studio generates a retail cost of $100 based on Copilot Credit usage, then 100 Copilot Credit CUs are consumed. One CCCU therefore pays down one US dollar of qualifying retail cost, regardless of your purchasing currency.
- What are the P3 tier sizes and discounts?
- Microsoft does not publish them in this documentation. The article shows tiers only inside a hypothetical, saying let us say the cost of that tier is $14,100 for a 15,000 CU Tier 2 plan, which is an illustration and not a price. The tier list and its discounts are shown in the Azure portal at purchase. Any specific percentage range you find elsewhere is third-party.
- What is the pay-as-you-go rate for a Copilot Credit?
- Microsoft does not commit to one in this document. Its worked example says assuming the pay-as-you-go rate for Copilot Credit to be $0.01, which is an assumption inside an illustration rather than a published rate. Treat any figure derived from it as unconfirmed.
- Can I cancel or exchange a Copilot Credit Pre-Purchase Plan?
- No. Microsoft states cancel and exchange operations are not supported for Copilot Credit Pre-Purchase Plans and that all purchases are final. You also cannot split or merge one. What you can change after purchase is the reservation scope and who can view or manage it.
- Does the pre-purchase discount stack with my other Microsoft discounts?
- No. Microsoft's note says pre-purchase plan discounts do not combine with other discounts, and that where you hold additional discounts the pre-purchase discount is applied independently, which may produce a lower effective discount than the listed tier percentage.
Sources & further reading
Done for you
Want this built for your business?
Tell us the workflow. We scope, build, and ship the agent with guardrails and the numbers to prove it worked. The scoping call is free.
Free scoping call. You own the code.
Was this page helpful?

