Is there a free trial for Copilot Studio?

Microsoft offers a trial that lets you build and test an assistant without a paid commitment. Check the current trial terms on the Microsoft Copilot Studio product page, as the length and scope can change.

What counts as a message in Copilot Studio?

A message is one unit of consumption charged per user interaction. Classic topic replies typically count as one message; generative AI replies, autonomous agent actions, and code execution can count several messages per turn. Microsoft publishes current rates in its licensing documentation.

Can you switch between capacity packs and pay-as-you-go?

Yes. Switching requires billing administrator access in the admin center. Consider the timing: moving mid-month may leave unused messages on a prepaid pack or result in an unexpected Azure charge for the remainder of the month.

Do the messages included with a Microsoft 365 plan expire?

Yes. Tenant entitlements included with a Microsoft 365 plan reset each calendar month and unused messages do not carry over.

What happens if you run out of messages mid-month?

By default, the assistant stops responding to users when the allocation is exhausted. You can configure pay-as-you-go overflow on a capacity pack so service continues at the per-message rate. Microsoft's licensing documentation explains how to enable that option.

Copilot Studio Pricing and Licensing: What You Need to Know

Copilot Studio charges by message, with some capacity bundled in qualifying Microsoft 365 plans and more available through capacity packs or pay-as-you-go billing. Here is how the structure works and what to confirm before you deploy.

September 15, 2026Updated October 21, 20266 min read

Copilot Studio pricing is built around messages: each time a user interacts with an assistant, one or more messages are counted against your allocation. Some capacity comes with qualifying Microsoft 365 plans, and you can add more through monthly capacity packs or by connecting Copilot Studio to an Azure subscription for pay-as-you-go billing.

Understanding the structure before you build saves surprises at invoice time. When a team chooses a billing route, that decision belongs somewhere the next person can find it. Tools like fenbs let you record the reasoning behind licensing choices alongside the project, so the whole team stays aligned even when the original decision-maker changes.

What drives the cost: messages

Copilot Studio meters usage in messages. A classic conversation message typically counts as one unit. Generative AI replies, agent-mode interactions, and code execution can count several units for a single turn. Microsoft publishes the message rates for each interaction type on its official Copilot Studio pricing page (opens in a new tab); check there for current numbers because rates change.

The practical implication is that an assistant built around generative AI replies or multi-step agent actions will burn through its monthly allocation faster than a classic topic-based assistant. Before you finalize the design, estimate the expected interaction type and volume, not just the user count.

What comes with your Microsoft 365 plan

Several Microsoft 365 and Dynamics 365 plans include a monthly message entitlement for Copilot Studio at the tenant level. That entitlement is pooled across everyone building and testing assistants in your organization. Microsoft's licensing overview (opens in a new tab) lists which plans qualify and how the pool is calculated.

If you already have a qualifying plan, check what is included before purchasing anything extra. Many teams can build and test an assistant without an additional purchase. The entitlement does not roll over between months, so unused capacity disappears when the month closes.

Capacity packs and monthly subscriptions

When your included allocation runs short, the most common next step is a monthly capacity pack. You purchase a fixed block of messages at a flat rate, and those messages are added to the tenant pool. The pack renews each month whether you use it or not, so it works best when your volume is consistent and predictable.

Capacity packs are managed in the Microsoft 365 admin center or the Power Platform admin center. Only a billing administrator can add or remove a pack. That means the person who approved the purchase may not be the person who handles the bill months later. Record the reason for any pack alongside who approved it.

Pay-as-you-go billing through Azure

Connecting Copilot Studio to an Azure subscription switches billing to a pay-as-you-go model. Usage is billed at the per-message rate with no upfront commitment. This suits pilots, low-volume assistants, and situations where demand is hard to predict. See the pay-as-you-go guide for steps on linking an Azure subscription.

Pay-as-you-go charges appear on the Azure bill rather than the Microsoft 365 bill, which matters to teams that manage those budgets separately. Confirm with your finance team which cost center covers Azure charges before you connect the subscription.

How fenbs helps

Record the licensing decision where the team can find it

When your team chooses a billing route, add a Decision in fenbs: billing route chosen, reason, who approved it, and when to review it. The next person who opens the invoice will have the context without hunting through old emails. Add a standing rule if your organization has a policy on maximum monthly spend so connected assistants read it first.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

What to check before you deploy

Before publishing an assistant to users outside your development group, verify these five points.

Billing route active: check the admin center and confirm the subscription or pack shows expected usage.
Message type mix: generative and agent responses consume more messages per interaction than classic topic replies.
Administrator access: confirm who can add capacity or adjust the Azure subscription and record their name in the project.
Usage alerts: set a threshold in the Power Platform admin center to notify your team before the allocation runs out.
Environment assignment: in multi-environment tenants, verify that billing tracks the right environment so development testing does not consume production capacity.

Licensing across multiple environments

Larger organizations often maintain separate Power Platform environments for development, testing, and production. Copilot Studio capacity is allocated at the tenant level by default, but admins can assign specific amounts to individual environments. Without that assignment, a burst of developer testing can reduce the allocation available to production users.

Separating environments is also a useful step when learning Copilot Studio. The training guide covers building your first assistant in a safe development environment. Keep the environment structure as a recorded decision so any new team member understands where work-in-progress assistants live.

How to do this with fenbs

Use fenbs to hold the licensing decisions that otherwise live in one person's inbox or a meeting note nobody can find six months later.

Create a free account and add a project for your Copilot Studio deployment.
Add a task for the licensing review. Note the billing route selected, the expected monthly volume, and who holds billing administrator rights.
Record the billing route as a Decision in fenbs with the approver's name and the review date.
Add a standing rule if your organization has a cap on unplanned spend, so any connected assistant reads it before recommending additional capacity.
Link the official Microsoft licensing documentation (opens in a new tab) from the project so it is one click away at renewal.

fenbs does not manage your Microsoft billing or send usage alerts. Use the Power Platform admin center for that. fenbs keeps the team's decisions and their reasoning in one record that the next assistant or colleague can read.