What it does

Copilot Studio is licensed on a consumption model measured in messages. You either prepay a capacity pack or pay-as-you-go through an Azure subscription, and agent interactions draw down that capacity.

Key facts

• Consumption is counted in messages, and different actions consume different numbers — generative answers, orchestration and tool calls cost more than a simple scripted reply.
• The prepaid capacity pack is a monthly tenant-level allocation; pay-as-you-go bills usage to Azure with no cap.
• Some Copilot Studio use is included with Microsoft 365 Copilot, but custom autonomous and heavier scenarios draw metered capacity.
• Premium connectors used by an agent's tools can carry their own separate licensing.

When to use / skip

Model capacity before you scale any agent past a pilot. Prepaid packs suit predictable volume; pay-as-you-go suits spiky or uncertain usage where you don't want to over-buy — but it has no ceiling, so set budget alerts.

Configuration decisions

• Prepaid capacity vs pay-as-you-go, or a mix.
• Budget alerts and, for PAYG, spend limits in Azure.
• Whether to consolidate capacity centrally or charge back to business units.

Gotchas

• Pay-as-you-go has no cap by default — a runaway autonomous agent bills straight to Azure. Alert on it.
• Message costs per interaction change with the release; last quarter's estimate can be wrong.

Consultant notes

• Model worst-case message volume, not average — autonomous and voice scenarios blow through estimates.
• Confirm current per-action message rates directly with Microsoft; they shift and public summaries lag.
• Get finance to own the capacity model early; this is the commercial risk in every Copilot Studio programme.

---

Reconfirm rates and pack sizes against current Microsoft pricing.