Copilot Credit P3 vs Microsoft Agent P3: which pre-purchase plan should you buy?

The short version

• Copilot Credit Pre-Purchase Plan (P3) is the narrow one. You buy Copilot Credit Commit Units (CCCUs) and they pay down Copilot Credit usage across Microsoft Copilot Cowork, Copilot Studio, Dynamics 365 first-party agents, and Work IQ APIs.
• Microsoft Agent Pre-Purchase Plan (Agent P3) is the wide one. You buy Agent Commit Units (ACUs) and they pay down usage across Microsoft Foundry, Microsoft Copilot Studio, Microsoft Fabric, and GitHub Copilot
• Both are one-year, pay-up-front plans bought through Azure subscriptions. Both auto-renew by default. Both expire unused credits at the end of the term. Neither can be canceled or exchanged.
• The bigger your commitment, the deeper the discount tier.
• If your only AI spend is Copilot, Copilot P3 is the fit. If you're also running Foundry, Fabric, or GitHub workloads, Agent P3 covers all of it from one pool.

What is the Copilot Credit Pre-Purchase Plan?

Copilot Credit P3 is a one-year, pay-up-front purchase of Copilot Credits at discounted tiers. You buy Copilot Credit Commit Units, eligible usage draws them down, and nothing needs redeploying or reassigning.

Microsoft's worked example: an organization expecting 1,500,000 Copilot Credits from custom Copilot Studio agents, at an assumed pay-as-you-go rate of $0.01 per credit, would spend $15,000. Buying Tier 2 (15,000 CCCUs) at an illustrative $14,100 gives a 6% saving. Microsoft's announcement post puts the ceiling at "up to 20% discount at highest tier," with the caveat that realized cost per credit depends on how much of the pool you use. A 20% discount on credits you never spend is worth nothing.

Eligible services: Copilot Studio, Copilot Cowork, Dynamics 365 agents, Power Platform, and Work IQ APIs. Microsoft reserves the right to change that list.

What is the Microsoft Agent Pre-Purchase Plan?

Agent P3 is the same mechanic with a much wider blast radius. You commit up front to a pool of Agent Commit Units, and they pay down qualifying usage across Microsoft Foundry, Microsoft Copilot, Microsoft Fabric, and GitHub. Microsoft describes it as covering 30+ agentic services from one pool. The conversion works the same way: if Copilot Studio or Foundry generates $100 of retail cost, 100 ACUs are consumed.

Microsoft's example: 1,500,000 Copilot Credits plus 5,000 Foundry Provisioned Throughput Unit hours, which at assumed rates of $0.01 per credit and $1.00 per PTU comes to $20,000 pay-as-you-go. Tier 1 (20,000 ACUs) at an estimated $19,000 saves roughly 5%.

Two rules catch people. You can't split or merge the plan after purchase, and Agent P3 pays down usage costs only, never the purchase cost of another reservation or plan.

Copilot P3 vs Agent P3: what's the difference?

One caution on that last row. Microsoft publishes the live tier tables as graphics inside the Azure purchase flow, and the tier numbers don't map across the two plans. Tier 1 of Agent P3 is not a bigger or smaller version of Tier 1 of Copilot P3. Pull the current tiers from the Azure portal before you size anything.

Which pre-purchase plan should you buy?

Start with what your AI spend is going to look like over the next twelve months, not what it looks like this quarter. If you're still early and sizing the rollout itself, our take on what Microsoft Copilot readiness means in 2026 is the better starting point.

Buy Copilot Credit P3 if your consumption is Copilot Studio agents, Copilot Cowork, Dynamics 365 agents, Power Platform, or Work IQ APIs , with no Foundry or Fabric spend on the roadmap. It's the more granular benefit, and Microsoft's documented Azure consumption order preserves it for that usage.

Buy Agent P3 if you're building across the stack. Foundry deployments, Fabric capacity, GitHub, and Copilot Studio drawing from one pool means one line item, one renewal date, and one number for procurement to approve instead of four.

Buy both if you have heavy, predictable Copilot Studio or Copilot Cowork usage plus variable Foundry or Fabric usage. Microsoft's documentation walks through that combination, and it's where the consumption order below matters most.

Buy neither yet if you can't forecast. Unused credits expire, purchases are final, and pre-purchase discounts don't stack with any discount you already hold. Run pay-as-you-go for a quarter, pull real consumption data out of the Cost Management dashboard, then size the commitment.

How do the credits get consumed?

The order depends on which surface is doing the billing. Microsoft documents three different sequences across three different pages, and conflating them is what generates support tickets.

Azure benefit precedence. Microsoft's Agent P3 documentation states that reservations always apply before pre-purchase plans, and lays out the order as: Microsoft Foundry PTU reservations, then Microsoft Fabric Capacity reservations, then Copilot Credit P3, then Agent P3 applied last to remaining AI usage.

Microsoft 365 admin center, with capacity packs. If you select both capacity packs and an Azure subscription carrying P3 prepaid credits, the documented order is capacity packs, then P3 prepaid credits, then pay-as-you-go.

Microsoft 365 admin center, for AI experiences like Cowork. Most licensing conversations get this one wrong, so it's worth quoting Microsoft's usage-based billing documentation directly:

Customers can use Agent P3 and Copilot P3 credits for AI experiences, such as Cowork. Currently, the Microsoft 365 admin center displays only the credits available from Copilot Credit P3. However, if the subscription selected for the billing method includes Agent P3, the system uses the Agent P3 credits first and bills any overage charges only after those credits are exhausted.

Your admin center can show a smaller credit balance than you own. If Agent P3 credits sit on the subscription behind your billing method, they get spent first while the dashboard shows you the Copilot Credit P3 number. Reconcile a Cowork bill against that dashboard and you'll reach the wrong conclusion.

One more billing-method rule from the same page. Once you set a billing method on a spending policy and create the policy, you can't change it. You have to delete the policy and build a new one.

Frequently asked questions

Can Copilot P3 and Agent P3 credits both pay for Cowork?

Yes. Microsoft states that customers can use Agent P3 and Copilot P3 credits for AI experiences such as Cowork. The Microsoft 365 admin center currently displays only the Copilot Credit P3 balance, and Agent P3 credits are drawn down first when the billing subscription includes them.

What happens to credits we don't use?

They expire at the end of the one-year term. Both plans auto-renew by default, so check that setting if you don't want another year.

Can we cancel or exchange a pre-purchase plan?

No. Microsoft states that cancel and exchange operations aren't supported for either plan and all purchases are final.

Who needs to buy it?

On an Azure subscription, the Owner or Reservation purchaser role. On an Enterprise Agreement, an EA administrator enables the Reserved Instances policy option first. On a CSP subscription, your partner buys on your behalf or grants you permission to buy your own.

Do these discounts stack with our existing agreement discounts?

No. Microsoft is explicit that pre-purchase plan discounts don't combine with other discounts, and that an existing discount may leave you with a lower effective rate than the listed tier percentage.

Get the sizing right before you commit

Every hard edge on these plans points the same direction. Purchases are final, unused credits expire, discounts don't stack, and the consumption order changes depending on the surface. The savings are real, and they show up only if the forecast is right.

Every week, our licensing team helps Microsoft-committed organizations understand how Copilot Credits are calculated, find the right cost estimate calculator, and break down the pros and cons of each pre-purchase plan — so they land on the option that actually fits how they'll use it. As a Microsoft Solutions Partner, we can handle the CSP purchase mechanics too.

If you're rolling out agents and you're not certain which plan to buy, talk to our licensing team before you commit the budget.