We’re launching a Pre-Purchase Plan (P3) for Microsoft Copilot Studio: a prepaid capacity option on Azure rails. This plan is Microsoft Azure Consumption Commitment (MACC)-eligible, offers annual commitment discounts, auto-monetizes overages at Pay-As-You-Go (PayGo) rates, and uses a single external meter that spans Copilot Studio, Dynamics 365 out-of-box (OOB) agents, and Moveworks OOB agents. Usage is externally reported under M365—Productivity & Business Process KPI.
[When this will happen:]
Customer availability begins November 1, 2025.
[How this will affect your organization:]
Who’s affected:
- IT administrators
 - Procurement and finance teams (MACC)
 - Platform owners for Copilot Studio, D365 OOB, and MW OOB
 
What’s changing:
- Purchase annual, prepaid Commit Units (CU) with tiered discounts; overages billed at PayGo rates
 - A single meter aggregates usage across Copilot Studio, D365 OOB, and MW OOB
 - MACC is decremented at purchase; revenue is recognized upon consumption; unconsumed credits are recognized in the final month
 
Copilot credit options (CU ↔ credits):
Standard P3 (fastest):
- 1 CU = $1
 - Example: 3,000 CU list price = $3,000; sold at $2,850 (5% discount)
 - Converts to 300,000 credits at $0.01/credit
 
Custom P3 (developer-friendly):
- 1 CU = $0.01 (CU ≡ Copilot Credit)
 - Example: 300,000 CU (credits) list price = $3,000; sold at $2,850 (5% discount)
 - Longer lead time (non-standard)
 
P3 Mechanics:
- 1-year prepaid, use-it-or-lose-it, auto-renewing model
 - Overage billed at PayGo
 - Revenue recognized as consumed; remaining credits recognized in the final month
 
[What you can do to prepare:]
- Choose between Standard and Custom CU mapping
 - Align MACC and budget with forecasted consumption
 - Review procurement processes for annual prepay and auto-renew
 - Coordinate with platform owners to leverage the single meter
 
Additional Information:
- Usage across Copilot Studio, D365 OOB, and MW OOB is metered together and reported under M365
 - Custom P3 offers intuitive credit mapping but requires longer implementation lead time
 
