Microsoft Copilot Studio pricing has three main payment routes: pay as you go at $0.01 per Copilot Credit, a tenant-wide capacity pack at $200 per month for 25,000 Copilot Credits, and prepaid commitment plans for larger or variable demand. Microsoft 365 Copilot users can also build and use internal agents in eligible Microsoft 365 scenarios without separate Copilot Studio usage charges for covered actions.
Quick answer: Pay as you go is usually the safest starting point for a small business testing an external or customer-facing agent because there is no upfront capacity commitment. The $200 capacity pack becomes cheaper than pay as you go when eligible monthly usage rises above roughly 20,000 Copilot Credits, assuming the published $0.01 pay-as-you-go rate. Microsoft 365 Copilot may be the better route for internal agents used only by licensed employees in Copilot Chat, Teams, or SharePoint.
Pricing was last checked on October 3, 2026 using Microsoft's Copilot Studio pricing page, licensing guidance, and billing documentation. Microsoft bills different agent capabilities at different credit rates, so a conversation count alone is not enough to forecast cost.
Copilot Studio Pricing at a Glance
| Option | Published price | Included capacity | Best fit | Main limitation |
|---|---|---|---|---|
| Pay as you go | $0.01 per Copilot Credit | None prepaid | Pilots, seasonal demand, and uncertain usage | Requires an Azure subscription and costs rise directly with consumption |
| Copilot Credit capacity pack | $200 per pack per month | 25,000 credits monthly | Steady production usage | Upfront annual subscription commitment; unused monthly capacity does not carry over |
| Pre-purchase plan | Tiered commitment pricing | Chosen credit commitment | Larger or variable enterprise demand | Requires forecasting and procurement; exact tier economics depend on the selected commitment |
| Microsoft 365 Copilot use rights | Included with an eligible Microsoft 365 Copilot license | Covered internal use for licensed users | Employee-facing agents inside Microsoft 365 | Does not replace standalone licensing for every external or non-licensed-user scenario |
| Trial | $0 for a limited evaluation | Test capacity | Building and testing a proof of concept | Trial users can test agents but cannot publish them |
The standalone product is tenant based rather than a conventional per-maker subscription. Makers still need access through a free Copilot Studio user license, a Microsoft 365 Copilot license, a Copilot Studio author role, or a trial. People who use a published standalone agent do not need their own Copilot Studio license.
How Copilot Credits Work
Copilot Credits are the billing unit for the work an agent performs. A single user turn may consume more than one credit because retrieval, generation, actions, grounding, agent flows, voice, or premium reasoning can carry different rates.
Microsoft currently lists these common standard-harness rates:
| Agent activity | Billing rate |
|---|---|
| Classic answer | 1 Copilot Credit |
| Generative answer | 2 Copilot Credits |
| Agent action | 5 Copilot Credits |
| Microsoft Graph tenant grounding | 10 Copilot Credits |
| Agent flow actions | 13 Copilot Credits per 100 actions |
| Premium reasoning-model text and generative tools | 10 Copilot Credits per 1,000 tokens, in addition to the feature rate |
These rates explain why two agents with the same conversation volume can have very different costs. A simple FAQ agent that returns classic answers is cheaper than an agent that grounds every response in tenant data, calls business systems, and uses a reasoning model.
The cost formula is straightforward:
Pay-as-you-go cost = total billable Copilot Credits × $0.01
For a capacity pack, usage consumes the tenant's pooled monthly credits. Microsoft states that unused subscription capacity does not carry into the next month. Administrators should allocate capacity to environments, monitor each agent, and set alerts before production traffic grows.
Worked Cost Examples
The following examples apply Microsoft's published rates to hypothetical workloads. They are planning calculations, not measured customer results.
Simple FAQ agent
If an agent produces 1,000 classic answers in a month:
- 1,000 answers × 1 credit = 1,000 credits
- 1,000 credits × $0.01 = $10 on pay as you go
If those same 1,000 interactions use generative answers instead:
- 1,000 answers × 2 credits = 2,000 credits
- 2,000 credits × $0.01 = $20 on pay as you go
Agent that takes actions
If an agent completes 1,000 billable agent actions:
- 1,000 actions × 5 credits = 5,000 credits
- 5,000 credits × $0.01 = $50 on pay as you go
The external API, database, messaging, telephony, Azure, or premium connector involved may create separate charges. Copilot Credits cover Copilot Studio consumption, not every connected service.
Microsoft Graph-grounded internal agent
If 1,000 billable responses use tenant Graph grounding:
- 1,000 grounded operations × 10 credits = 10,000 credits
- 10,000 credits × $0.01 = $100 on pay as you go
For a licensed Microsoft 365 Copilot user accessing an eligible internal agent through Microsoft 365 Copilot, Teams, or SharePoint, Microsoft lists classic answers, generative answers, actions, tenant Graph grounding, and qualifying agent-flow use as no-charge consumption. Identity and deployment context matter, so administrators should confirm that traffic is actually attributed to licensed users in a covered scenario.
Mixed production workload
Consider a hypothetical month with 5,000 generative answers, 1,000 agent actions, and 500 Graph-grounded operations:
- Generative answers: 5,000 × 2 = 10,000 credits
- Agent actions: 1,000 × 5 = 5,000 credits
- Graph grounding: 500 × 10 = 5,000 credits
- Total: 20,000 credits
- Pay as you go: 20,000 × $0.01 = $200
At this point, the published $200 capacity pack has the same nominal monthly cost while providing 25,000 credits. The pack leaves 5,000 credits of headroom, but it also involves a subscription commitment and monthly capacity expiration. Premium reasoning, voice, connected-service charges, taxes, and region-specific terms are outside this simplified calculation.
The Practical Break-Even Point
At $0.01 per credit, $200 buys 20,000 credits through pay as you go. The capacity pack provides 25,000 credits for $200, which gives it an effective rate of $0.008 per credit when fully used.
That creates a useful decision rule:
- Below 20,000 monthly credits, pay as you go normally costs less.
- At about 20,000 credits, the monthly cost is roughly equal.
- Between 20,000 and 25,000 credits, the capacity pack offers more included usage for the same published monthly amount.
- Above 25,000 credits, compare multiple packs, pay-as-you-go overage, and pre-purchase tiers using a realistic forecast.
The arithmetic does not make the pack automatically better. A workload that swings between 5,000 and 30,000 credits may waste prepaid capacity in quiet months. A stable agent using 23,000 credits every month can use a pack more efficiently. Procurement terms, annual commitment, regional currency, and tax can also change the commercial decision.
What Is Included With Microsoft 365 Copilot?
Microsoft 365 Copilot includes Copilot Studio capabilities for internal agents used by licensed people in Microsoft 365. This route is attractive when the agent supports employees and stays inside Copilot Chat, Teams, or SharePoint.
Examples include:
- An HR policy agent grounded in approved SharePoint content.
- A sales enablement agent that answers licensed employees from internal documents.
- A project assistant used in Teams by Microsoft 365 Copilot subscribers.
- A departmental agent that invokes covered actions for authenticated licensed users.
The key boundary is the user and channel. A public website agent serving customers, an agent used by unlicensed workers, or an external-channel deployment can require standalone Copilot Studio capacity. The included use rights should not be treated as unlimited free capacity for every agent the organization builds.
Licenses Makers and Users Need
For a standalone subscription, Microsoft distinguishes the tenant license from maker access:
- The organization acquires Copilot Studio capacity through a tenant subscription or connects an Azure subscription for pay as you go.
- Each person who creates or manages agents needs appropriate maker access, such as the $0 Copilot Studio User License tied to the tenant subscription, an author role, or Microsoft 365 Copilot rights.
- End users of a published agent do not need a Copilot Studio user license.
- Guest users cannot access the Copilot Studio authoring experience.
- A trial can be used to build and test in the test panel, but it does not qualify the maker to publish an agent.
This separation is easy to miss. Buying capacity does not automatically assign authoring access to every employee, and assigning a free user license does not create production capacity on its own.
Real Costs Beyond Copilot Credits
Copilot Credits are only one line in the operating budget. A useful forecast should also consider:
Connected services
An agent may call Azure AI services, Azure Functions, external APIs, databases, telephony providers, premium data services, or software with usage-based billing. Bring-your-own-model configurations are billed separately from Copilot Studio's included models.
Implementation and governance
Someone must design topics and tools, prepare knowledge, configure authentication, apply data-loss-prevention policies, test failure paths, monitor analytics, and maintain the agent. A cheap agent that exposes the wrong data or repeatedly hands users a dead end is not a low-cost deployment.
Knowledge preparation
Agents perform better when source material has clear ownership, permissions, dates, and structure. Teams may need to clean SharePoint libraries, remove duplicate policies, define authoritative sources, and fix access control before rollout.
Human handoff
Customer-facing agents need a route for billing disputes, cancellations, complaints, account access, sensitive data, and uncertain answers. The support platform and staff time required for that handoff should be included in the business case.
Practical Use Cases and Likely Cost Drivers
Customer support
A support agent can answer FAQs, explain onboarding steps, collect details, look up an order, or open a ticket. Classic and generative answers may be inexpensive, while actions, authentication, CRM calls, Graph grounding, and voice increase consumption and connected-service cost.
Employee knowledge
An internal agent can help licensed employees find policies, procedures, and project information. Microsoft 365 Copilot use rights can materially change the economics when the audience is authenticated and the agent runs in covered Microsoft 365 channels. For broader platform choices, see our guide to the best AI agent platforms for small business.
Workflow automation
An agent can collect a request, validate fields, trigger an approval, create a record, and notify an owner. Agent actions and flow actions become the important meters. Teams focused mainly on deterministic back-office automation should also compare Make vs n8n and Zapier vs Make.
External self-service
A website agent can serve customers who do not hold Microsoft 365 Copilot licenses. Standalone capacity or pay as you go is the relevant budget path. Traffic seasonality, abuse controls, response design, and escalation rates become important forecast inputs.
How to Estimate Your Monthly Bill
1. Separate audiences. Count licensed Microsoft 365 Copilot employees, other authenticated employees, customers, partners, and anonymous visitors separately. 2. Map each journey. List answers, actions, grounding operations, flow actions, premium reasoning, voice, and connected services used by a typical successful journey. 3. Estimate monthly volume. Multiply expected journeys by the activity mix, then add realistic retry and error volume. 4. Apply official rates. Convert each activity into Copilot Credits and calculate pay-as-you-go cost. 5. Compare purchase routes. Test pay as you go, one or more 25,000-credit packs, and any eligible pre-purchase tier. 6. Add external costs. Include Azure, models, APIs, connectors, support systems, implementation, and human review. 7. Run a controlled pilot. Compare forecast credits with actual consumption by agent before increasing traffic. 8. Set monitoring. Assign an owner for capacity, alerts, environment allocation, and monthly variance review.
Microsoft provides an agent usage estimator, but the strongest forecast still starts with a concrete conversation and action map.
Pros and Cons of Each Pricing Route
| Route | Pros | Cons |
|---|---|---|
| Pay as you go | No upfront capacity purchase; good for pilots and variable demand; usage follows actual consumption | Azure setup required; less discount at steady higher volume; surprise costs need monitoring |
| Capacity pack | Better effective rate when well utilized; predictable monthly capacity; pooled at tenant level | Annual commitment; unused credits expire monthly; pack sizing can create waste |
| Pre-purchase plan | Designed for larger commitments and variable enterprise demand; volume economics may improve | More complex procurement and forecasting; exact fit depends on selected tier |
| Microsoft 365 Copilot use rights | Covered internal usage can avoid separate agent-consumption charges for licensed users | Limited to eligible users, identity, capabilities, and Microsoft 365 deployment contexts |
Alternatives to Copilot Studio
| Alternative | Best for | Pricing consideration | Main trade-off |
|---|---|---|---|
| Relevance AI | Multi-agent teams and business task automation | Subscription and usage structure differs by plan | Less native alignment with Microsoft 365 governance; see our Relevance AI review |
| n8n | Technical teams building flexible workflows and AI automations | Cloud plans use workflow executions; Community Edition is self-hosted | More engineering and operational responsibility |
| Zapier | Broad no-code app automation for business teams | Task and plan limits shape cost | Agent depth and Microsoft-specific governance differ |
| Microsoft Azure AI Foundry | Custom model, agent, and application engineering | Azure resource and model consumption can be granular | Requires stronger development and cloud architecture skills |
Copilot Studio is strongest when Microsoft identity, Power Platform connectors, Teams, SharePoint, Dataverse, governance, and external agent channels belong in one managed environment. It is not automatically the cheapest option for a simple internal FAQ or a deterministic integration that does not need an agent.
Best For and Not Best For
Best for: Microsoft-centered organizations building governed internal or external agents; teams that need low-code agent actions and Power Platform integration; businesses that can measure agent activity and allocate capacity across environments.
Not best for: A very small team that only needs a static website FAQ; developers seeking full infrastructure control at minimal software cost; organizations without an Azure or Power Platform owner; projects whose main need is ordinary trigger-and-action automation rather than conversation and reasoning.
Final Recommendation
Start with pay as you go when demand is unknown, the agent is still being validated, or usage is highly seasonal. Move to a 25,000-credit capacity pack when a stable production workload consistently approaches 20,000 monthly credits and the subscription commitment makes operational sense. Evaluate pre-purchase tiers when several agents or environments push demand beyond a few packs.
For internal employee agents, first determine how much usage is already covered by Microsoft 365 Copilot licenses. That can be more important than the standalone pack calculation. Whichever route you choose, budget from agent activities rather than conversation count, include connected-service costs, and monitor consumption after launch.
FAQs
How much does Microsoft Copilot Studio cost?
Microsoft lists pay as you go at $0.01 per Copilot Credit and a tenant-wide capacity pack at $200 per month for 25,000 Copilot Credits. It also offers pre-purchase plans for larger commitments and included internal-agent rights with eligible Microsoft 365 Copilot licenses.
Is the Copilot Studio user license really free?
The maker user license is listed at $0, but it works alongside tenant capacity or another qualifying access route. It gives a person authoring access; it does not provide standalone production consumption by itself.
Do customers need a Copilot Studio license to use an agent?
No. Microsoft states that users of a published agent do not need a special Copilot Studio license. The organization pays for eligible agent usage through capacity, pay as you go, pre-purchase credits, or covered Microsoft 365 Copilot use rights.
Do unused Copilot Credits roll over?
Included subscription capacity resets monthly and unused capacity does not carry over. That makes utilization important when comparing a capacity pack with pay as you go.
What happens when capacity runs out?
Microsoft applies capacity enforcement and can deny service when an environment exceeds available capacity without an appropriate billing route. Administrators should allocate capacity, monitor usage, and configure pay as you go or additional capacity before a critical agent reaches its limit.
Are reasoning models more expensive?
They can be. Microsoft applies the normal feature rate and adds the premium text and generative-tools rate based on reasoning-model token usage. A cost estimate should include both components.
Is Copilot Studio included with Microsoft 365 Copilot?
Microsoft 365 Copilot includes agent-building and eligible internal usage for licensed users in Microsoft 365 contexts. Standalone Copilot Studio remains relevant for external channels, non-licensed users, broader deployment choices, and usage outside those included rights.
What is the cheapest way to start?
A trial is useful for building and testing but cannot publish. For a production pilot, pay as you go avoids an upfront capacity commitment and lets the organization observe real credit consumption before choosing a pack.
