What it does

Covers how you actually pay for Copilot: the per-user add-on for Microsoft 365 Copilot, and the consumption-based routes for agents built in Copilot Studio.

Key facts

• Microsoft 365 Copilot is a per-user, per-month add-on, typically on an annual commitment, bought through your usual channel (direct, CSP, or EA).
• Agents have a separate money model. Consumption is billed in Copilot Credits (the currency that replaced "messages" from September 2025).
• Two agent paths: prepaid credit packs, or pay-as-you-go metered through a linked Azure subscription — no upfront commitment, pay for what's used.
• Pay-as-you-go requires a Power Platform billing policy linking the environment to an Azure subscription.
• Some agent interactions are included/seeded for licensed Copilot users; overflow is what meters. Confirm what's included at purchase time.

When to use / skip

Per-user add-on for the core Copilot experience. Metered agents when you're building custom agents and can't predict volume — but only with cost controls in place. Avoid quoting exact prices; they move.

Configuration decisions

• Prepaid packs (predictable, capped) vs. pay-as-you-go (flexible, open-ended).
• Which Azure subscription and billing policy back metered usage, and who owns that spend.
• Spend caps and alerts on the Azure side.

Gotchas

• Pay-as-you-go with no cap is an open tap; an unpopular-then-suddenly-popular agent can spike a bill.
• Teams assume the Copilot licence covers unlimited agent use — it doesn't, and the Azure invoice is the reminder.

Consultant notes

• Separate the two budgets clearly: predictable per-user licences versus variable agent consumption. Finance needs to see them apart.
• Start metered agents with caps and alerts; loosen once you've real usage data.
• Name an owner for Azure-billed agent spend — orphaned meters are how surprise invoices happen.
• Describe pricing as structure to customers, not fixed figures; the numbers shift and you'll be quoted on it later.

---

*Recheck credit rates, pack sizes and the pricing landing URL —