Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 14:23 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Copilot Studio: Introducing the pre-purchase plan (P3)

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

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

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 14:23 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current