Microsoft Copilot Studio Licensing Guide

The four layers

1. Authoring access Makers need the appropriate Copilot Studio access and environment permissions to create and publish agents. A pay-as-you-go billing policy funds runtime consumption; it does not automatically grant every employee maker rights. Microsoft’s troubleshooting guidance distinguishes capacity from user authorisation. Administrators still need to assign access, security groups, roles, and any required user entitlement. Keep production authorship limited and separate maker, approver, and operator responsibilities.

• 2. Runtime capacity The agent consumes Copilot Credits when it performs metered actions. The rate depends on the feature—for example, a classic answer, a generative answer, an action, or graph grounding can have different consumption. This makes architecture a licensing decision. A high-volume agent that invokes several actions and grounding steps per turn may use substantially more capacity than a simple FAQ agent, even if both report the same number of conversations.
• Use Microsoft’s current rate table for modelling. Do not rely on historic “messages” or old fixed-price assumptions; Microsoft’s model and feature rates have changed. 3. User entitlement
• Identify whether users are employees with Microsoft 365 Copilot, employees without it, anonymous visitors, customers, partners, or service identities. Microsoft documents eligible no-charge use for certain authenticated Microsoft 365 Copilot user scenarios, subject to the agent, channel, and feature conditions. That is not a universal free-runtime rule. External users and employees outside the applicable entitlement can create metered consumption. Authentication design must therefore be part of the cost model. 4. Channels and connected services
• An agent published to Teams, Microsoft 365 Copilot, a website, or another channel can have different identity and runtime patterns. Premium connectors, Power Platform resources, Azure services, Dynamics 365 data, or other products may introduce separate licensing and consumption requirements. Copilot Studio capacity does not automatically license every connected workload.

Prepaid Copilot Credits

Prepaid capacity is purchased and pooled at tenant level, then allocated to environments. It is useful when production demand is reasonably predictable, budgets need a committed ceiling, or procurement prefers capacity purchased in advance. Pooling does not remove governance. Capacity should be allocated by environment, monitored by agent, and protected with alerts and operational ownership. Microsoft documents limits and enforcement behaviour that can throttle or stop an agent when capacity is exhausted. Prepaid capacity can become shelfware when a pilot forecast is treated as a production commitment. Start with measured behaviour, not an optimistic conversation estimate.

Pay-as-you-go

PAYG connects eligible environment consumption to an Azure subscription. It is useful for pilots, uneven demand, and agents whose

• activity is not yet predictable. It also avoids purchasing a large fixed capacity before the design is proven.
• The trade-off is exposure to variable Azure charges. Add an Azure budget, cost alerts, environment-level ownership, and an incident path for abnormal
• use. Validate which production and sandbox environments are covered and test how the agent behaves when limits or billing issues occur.
• PAYG should never mean “unmanaged”. A public agent with poor abuse controls,

Practical checks

expensive action chains, or a configuration loop can generate unexpected consumption.

A practical selection model

Use PAYG first when the use case is new, volume is uncertain, and the team needs real consumption data.

• Move a stable workload to prepaid capacity when the monthly
• profile becomes predictable and the commercial comparison justifies it.
• A hybrid model can also work: reserve prepaid capacity for stable production agents and use PAYG for pilots or bursts. Confirm
• how Microsoft applies and reports consumption in the current tenant

Practical checks

configuration before assuming one pool will automatically cover every environment.

Build a consumption forecast

For each agent, record: monthly active authenticated and unauthenticated users;

• sessions and turns per user; percentage of turns using generative answers;
• actions and connector calls per successful outcome;
• grounding method and frequency; escalation and fallback rate;
• test, sandbox, and production traffic; expected growth and peak factor.

Practical checks

Multiply the activity mix by Microsoft’s current Copilot Credit rates, then add a measured buffer. Recalculate after a pilot using actual analytics. A forecast without the feature mix is too weak for procurement.

Controls before production

Assign a business owner, technical owner, and cost owner. Restrict makers and publishing rights.

• Separate development, test, and production environments.
• Document authentication and user populations.
• Inventory connectors and separately licensed services. Set capacity alerts, Azure budgets, and a response threshold.
• Test throttling, fallback, and human escalation.

Practical checks

Review high-consumption topics and action chains monthly.

Common mistakes

Using an outdated per-message price in a business case. Assuming PAYG grants maker rights.

• Treating Microsoft 365 Copilot licensing as free use for every agent and user.
• Forecasting only conversations while ignoring actions and grounding.
• Publishing externally without abuse, authentication, and cost controls. Assuming Copilot Studio includes every connector or source-system licence.
• Buying tenant capacity without allocating or monitoring environments.

Practical checks

The most accurate estimate comes from a small, controlled pilot with representative workflows. If you need the architecture, entitlement, and consumption model reviewed together, contact Axeti . For the separate distinction between Microsoft 365 Copilot Chat and paid Copilot licences, see Axeti’s Copilot comparison .

Sources and scope: This article is based on Microsoft’s Copilot Credit rate documentation , capacity management guidance , and May 2026 Copilot Studio licensing guide . Rates, entitlements, and enforcement can change; revalidate the agent design and current documentation immediately before publication and purchase.