Guide · Copilot Studio and costs

How much does Copilot Studio cost: licensing, Copilot Credits and estimating consumption

Assaf Semoun, Founder & CEO of Zooz-TechUpdated 22.11.20267 min read
In short

Copilot Studio is priced by usage, in a unit called the Copilot Credit. Every response and action of the agent consumes a fixed number of credits: a classic answer consumes less, and a generative answer or an agent action consumes more. You pay with monthly capacity packs, pay-as-you-go through an Azure subscription, or a one-year pre-purchase. Employees with a Microsoft 365 Copilot license who use an internal agent are covered by their license, within fair-use limits. To keep cost low, move fixed logic to Power Automate and give the model only what only a model can do.

How much does Copilot Studio cost?

In short: it depends on how many conversations the agent will have and what it does in each one. There is no fixed price per agent and no price per user. There is consumption.

The cost of a Copilot Studio agent has two parts, like any AI agent: a one-time build and an ongoing cost. This guide covers licensing and ongoing consumption. For the build cost and what drives it, see the guide to AI agent cost.

How does Copilot Studio licensing work?

In short: all usage is measured in Copilot Credits, and there are three ways to pay for them. The figures in the table are as of 11.2026, according to Microsoft's Copilot Studio licensing guidance and the official pricing page:

OptionHow it worksList price
Capacity pack25,000 Copilot Credits per month, pooled across the whole organization (tenant). Unused credits do not roll over to the next month.$200 per pack per month, billed annually
Pay-as-you-goNo upfront commitment. Billed at the end of each month, through an Azure subscription linked to the environment.$0.01 per Copilot Credit
Pre-Purchase PlanOne year paid upfront in Copilot Credit Commit Units. Unused units do not roll over to the next year.$1 per unit, worth 100 Copilot Credits. Microsoft cites savings of up to 20%

Prices are in US dollars, as of 11.2026. They change, exclude VAT and discounts, and may vary by currency and country. According to Microsoft, there is no difference in capabilities between capacity packs and pay-as-you-go, only in how you pay.

What about a Microsoft 365 Copilot license?

According to Microsoft's documentation, when an employee with a Microsoft 365 Copilot license uses an internal agent, and the agent operates under that employee's identity, the usage is included in the license and no credits are consumed, within fair-use limits. This does not apply to an agent that serves customers or residents, to an agent that runs autonomously from a trigger, or to employees without the license. For those agents, all usage counts.

What consumes Copilot Credits?

In short: every response and action of the agent is counted by its type. These are the main rates, as of 11.2026, according to the Copilot Studio billing rates table:

What the agent doesCopilot Credits
Classic answer, authored in advance in a topic1
Generative answer, written by the model from knowledge sources2
Agent action: a trigger, reasoning step, topic transition or tool call5
Grounding in the organization's Microsoft Graph (tenant graph grounding)10
Agent flow: a fixed process the agent runs inside Copilot Studio13 per 100 actions
Content processing (documents)8 per page
Reasoning modelAn additional 10 per 1,000 tokens, on top of the feature rate
Voice conversation10 to 75 per minute, by voice tier

Two important notes. First, one response can consume several types at once: Microsoft gives the example of a Graph-grounded answer that consumes 12 credits, 10 for grounding and 2 for the generative answer. Second, with a reasoning model, billing is based on tokens, not messages, so long instructions, lots of retrieved knowledge and long conversations make every message more expensive.

Standard Power Automate processes (cloud flows) do not consume Copilot Credits. They are covered by Power Automate licensing.

How do you estimate monthly consumption?

In short: multiply the number of conversations per month by the average consumption of a conversation.

  1. Define a typical conversation. How many classic answers, how many generative answers and how many actions an average conversation has.
  2. Calculate credits per conversation. Using the rates table. If the agent uses a reasoning model, add an estimate of tokens.
  3. Multiply by volume. Conversations per day times active days per month.
  4. Separate the users. Conversations of employees with a Microsoft 365 Copilot license in an internal agent are not counted. Conversations of customers, of employees without the license and of autonomous agents are counted.
  5. Check against measurement. After a short pilot, compare the estimate with actual consumption in the Power Platform admin center, and update it.

An example from Microsoft's documentation: a customer service agent on a website that answers questions about return policies and product manuals. An average conversation has four classic answers and two generative answers, meaning 4×1 + 2×2 = 8 credits per conversation. At 900 conversations a day, that is 7,200 credits a day. In a 30-day month, that is 216,000 credits, a little under nine packs of 25,000.

Microsoft also publishes a usage estimator for agents, by agent type, volume, knowledge and tools.

How do you reduce consumption?

In short: give the model only what only a model can do.

  • Calculations and rules in Power Automate. Dates, amounts and rule-based checks do not need a model. A fixed process gives the same result every time, and saves the agent actions and reasoning.
  • Classic answers for recurring questions. A question whose answer does not change, such as opening hours, is better answered in a fixed topic: one credit instead of two, and a consistent answer.
  • A non-reasoning model when reasoning is not needed. A reasoning model is billed by tokens and makes every message more expensive. Keep it for tasks that genuinely need multi-step planning.
  • Short instructions and focused knowledge. Less text in every model call, and knowledge sources that contain only what the agent needs.
  • Graph grounding only when needed. It consumes 10 credits per message, and you can turn it on or off for each agent separately.
  • A monthly limit per agent. The administrator sets a cap in the Power Platform admin center, so one agent does not use up everyone's capacity.

Gil Car · invoice agent with SAP on-premises: the Copilot Studio agent reads the invoice and checks it against SAP to prevent duplicates. Four dates are calculated in Power Automate, with fixed logic, and not by the agent. This keeps the result consistent for every invoice, and the model does less work. The draft is created through an MCP layer, and an authorized user approves it inside SAP.

What happens when capacity runs out?

In short: after a certain margin, the agents are blocked, unless a pay-as-you-go fallback is linked to the environment.

According to Microsoft's documentation, capacity packs allow some overage. When the organization's consumption reaches 125% of the purchased capacity, the agents are blocked and show a message that they have reached their usage limit. For an agent that serves customers this is not acceptable, so you link a pay-as-you-go plan to the environment to cover the overage, or allocate dedicated capacity to the critical environment.

When is Azure AI Foundry cheaper or a better fit?

In short: at high volume, when you need full control over the model, or when the agent serves customers across several channels.

Azure AI Foundry has no Copilot Credits: you pay for model tokens, Azure AI Search and the infrastructure the agent runs on. Development and maintenance take more work, but you can choose a small model for each simple task, cache recurring answers and control every call. For internal agents and low to medium volume, Copilot Studio usually saves development time. For high volumes of customer conversations, on WhatsApp, voice or a custom interface, it is worth calculating both options.

CriterionCopilot StudioAzure AI Foundry
Billing modelCopilot Credits by type of response and actionTokens, search and infrastructure
BuildFaster, low-codeFull development, more work
Cost controlType of answer, logic in Power Automate and a limit per agentA model per task, caching and optimization of every call
Best suited toInternal agents, Microsoft 365 and Power PlatformHigh volume, customer channels and full control

The full comparison is in the guide Copilot Studio vs Azure AI Foundry.

How does Zooz-Tech estimate the cost of an agent?

In short: we measure on a real process before you commit.

In a Copilot Studio agents project, the ongoing consumption estimate is part of what we deliver: an estimate of Copilot Credit consumption based on expected usage volume, before you commit. We start with a POC on one process and your data, measure real consumption, and only then expand. After go-live we track usage, quality and costs. The full process is described on the How we work: Delivery and POC page.

Frequently asked questions

How much does Copilot Studio cost?

Copilot Studio is priced by consumption in Copilot Credits. As of 11.2026, according to Microsoft, a pack of 25,000 credits costs 200 US dollars per month, and with pay-as-you-go each credit costs 0.01 US dollars, before VAT and discounts. The actual cost depends on the number of conversations and what the agent does in each one.

What is a Copilot Credit?

The unit that measures agent usage in Copilot Studio. Every response and action consumes credits by type: a classic answer consumes one credit, a generative answer two and an agent action five.

Does a Microsoft 365 Copilot license include Copilot Studio?

Partly. An employee with a Microsoft 365 Copilot license who uses an internal agent under their own identity is covered by the license, within fair-use limits. Customer-facing agents, autonomous agents and employees without the license consume Copilot Credits.

What happens if credits run out mid-month?

Capacity packs allow some overage. When consumption reaches 125% of capacity, the agents are blocked. To prevent this, link a pay-as-you-go plan to the environment to cover the overage.

How do you reduce an agent's consumption?

Move calculations and rules to Power Automate, answer recurring questions with classic answers, use a reasoning model only when needed, and set a monthly limit per agent.

Assaf Semoun
Assaf Semoun

Founder & CEO of Zooz-Tech, solutions architect, Microsoft 365 Architect Expert.

Want to estimate how much your agent will consume?

Book a call