Copilot Studio pricing for licences and credits 2026
Estimate Copilot Studio costs for a store agent. See how licences, credits, pay-as-you-go billing and deployment requirements affect your budget.
- Published
- Last updated
Copilot Studio pricing starts at USD $0.01 per Copilot Credit on pay-as-you-go, or USD $200 per month for 25,000 credits with annual billing. A store agent’s cost depends on the answers and actions it performs. One shopper conversation can consume several credits.
The figures below use Microsoft’s public USD offers. Calculations exclude tax, currency conversion and implementation work. They estimate a customer-facing agent you operate on your own site.
What Copilot Studio charges for
Copilot Studio charges for agent usage through Copilot Credits, with separate access requirements for the people building the agent. Microsoft’s licensing guidance distinguishes these purchase arrangements.
| Arrangement | Public offer in USD | Capacity and commitment | Budget consequence |
|---|---|---|---|
| Pay-as-you-go | $0.01 per credit | Actual monthly usage, billed in arrears | Low usage costs less, while traffic spikes increase the bill |
| Copilot Credit capacity pack | $200 per pack per month, billed annually | 25,000 credits per month per pack | Unused monthly capacity expires |
| Copilot Credit Pre-Purchase Plan | Tiered upfront purchase | A credit pool usable over a one-year term | Allows uneven monthly use within the purchased annual pool |
A full pack works out to USD $0.008 per credit. That effective rate assumes you use all 25,000 credits that month. The annual commitment for one USD $200 monthly pack is USD $2,400.
Prepurchase plans have their own commitment sizes and discounts. Compare the annual spend with your expected usage before treating a discount as a saving.
Microsoft’s Studio plan comparison places website deployment under standalone Studio plans. Building a retailer-operated agent is a separate job from joining Copilot’s shopper-facing shopping channel.
Licences, free access and production use
Free Copilot Studio maker access lets a person build an agent under the relevant entitlement. It does not fund the deployed agent’s customer conversations.
Under the prepaid pack route, the tenant needs the paid capacity subscription. Each maker needs the free Copilot Studio User License assigned by an administrator. Under pay-as-you-go, Microsoft documents a free Copilot Studio Author role, with access controlled through a security group.
A trial lets you create an agent and use the test chat panel. It cannot publish the agent. Microsoft’s licensing documentation separates this trial access from the standalone subscription and Azure billing options.
For pay-as-you-go production use, connect the environment to an active Azure subscription through a billing plan. The administrator needs the relevant environment and Azure permissions. A free maker role alone leaves that billing setup unfinished.
Employee-agent entitlements depend on the licensed employee’s identity and supported usage. They do not make your public storefront traffic free. Budget shopper conversations under the standalone arrangement you choose.
How Copilot Studio credits become a bill
Copilot Studio adds the credit charges for each feature used during an interaction. Its standard-harness rate schedule lists the following units.
| Agent activity | Credit charge | Retail example |
|---|---|---|
| Classic answer | 1 | A fixed, authored delivery response |
| Generative answer | 2 | An answer generated from connected catalogue information |
| Agent action | 5 | An orchestrated action that retrieves an order |
| Tenant graph grounding | 10 per message | An answer grounded through tenant-wide Microsoft Graph search |
| Agent flow actions | 13 per 100 actions | Steps inside an agent flow |
Ordinary knowledge retrieval does not automatically mean tenant graph grounding. Apply the extra grounding charge when that feature is used. Microsoft’s example combines a generated answer with graph grounding for 12 credits.
Agent actions and the steps inside an agent flow are different billing items. Count the activity your design actually invokes. A reasoning model adds premium AI-tool token charges to the feature charge. Bring-your-own models have separate billing.
Microsoft’s billing FAQ also identifies charges for proactive greetings, including greetings that receive no reply. Triggering the agent to be ready can also incur a classic-answer charge without a visible greeting. Its test-chat exemption for the agent’s own activity does not cover every flow or prompt dependency. A quiet test panel therefore cannot establish your production bill.
When prepaid credits run out, configured pay-as-you-go covers additional consumption. Without available capacity or that billing cover, enforcement can interrupt service. Agent flows can have new runs blocked while other agent interactions remain available.
A product-question and order-lookup budget
A hypothetical store with 2,000 monthly conversations consumes 13,500 credits under the activity assumptions below. Its pay-as-you-go usage costs USD $135 before tax and other services.
Assume each conversation has one billed classic startup event and generates two catalogue answers using ordinary knowledge retrieval. In 500 conversations, the shopper also signs in and requests an order lookup. Each lookup uses one agent action and generates one further answer. The example uses the standard feature rates, without reasoning models, additional proactive greetings or extra flow steps.
| Workload item | Monthly calculation | Credits |
|---|---|---|
| Classic startup events | 2,000 events × 1 credit | 2,000 |
| Catalogue answers with retrieval | 2,000 conversations × 2 answers × 2 credits | 8,000 |
| Authenticated order-lookup action | 500 lookups × 5 credits | 2,500 |
| Generated order-status answer | 500 answers × 2 credits | 1,000 |
| Total | 2,000 + 8,000 + 2,500 + 1,000 | 13,500 |
Authentication protects order access. The five-credit item here is the designed lookup action, not a universal sign-in charge. Additional actions in your authentication or lookup process increase consumption.
If 400 answers also use tenant graph grounding, add 4,000 credits. The resulting 17,500-credit month costs USD $175 on pay-as-you-go. Use graph grounding only with source permissions suitable for the customer-facing agent.
One pack costs USD $200 for either workload, leaving unused credits that expire. At twice the base workload, 27,000 credits cost USD $270 on pay-as-you-go. One pack plus 2,000 pay-as-you-go credits costs USD $220 for that month. The pack still carries its annual commitment.
Keep implementation separate from these usage totals. Catalogue preparation and order-access development require work, as do ongoing testing and maintenance. The Copilot Studio implementation guide explains those responsibilities.
A connector marked premium does not automatically require a separate licence for every shopper. Microsoft’s agent-flow guidance permits premium connectors in consumption-billed agent flows without individual Power Automate licences. Separately licensed cloud flows and the connected commerce service can still add costs.
Add any external search infrastructure, custom model hosting and paid order-system access as separate budget lines. The credit calculation does not pay another provider’s invoice.
Choosing a studio billing arrangement
Start with pay-as-you-go when launch volume is uncertain. Buy monthly capacity against predictable usage only when its annual commitment makes financial sense.
At these public rates, USD $200 buys 20,000 pay-as-you-go credits. A pack becomes cheaper above that monthly usage level, up to its 25,000-credit allowance. Below 20,000 credits, pay-as-you-go costs less. This comparison excludes tax and any negotiated terms.
For seasonal peaks, packs plus pay-as-you-go can cover a steady baseline and occasional excess. For example, 30,000 credits cost USD $250 with one pack and 5,000 pay-as-you-go credits, compared with USD $300 entirely on pay-as-you-go. Low-volume months can erase that saving across the annual subscription. A prepurchase pool suits a different pattern when you can commit to annual usage but need flexible monthly consumption.
Before opening the agent to customers, configure its billing and monitoring.
- Identify the production environment and assign an operator responsible for its spend. For Azure billing, follow Microsoft’s pay-as-you-go setup with the correct subscription and resource group.
- Allocate prepaid capacity or enable the intended usage meter. Use the Copilot Studio capacity view to compare environment consumption with available credits.
- Create an Azure budget with actual-spend and forecast alerts. Microsoft’s budget documentation states that these notifications do not stop consumption. Reporting has a delay, so an alert cannot enforce an immediate spending cap.
- Decide who can disable the agent or costly features if spend exceeds your approved limit. Keep a customer-support route available when the agent stops.
- Review consumption after launch by agent and feature. Recalculate the budget when you add graph grounding, change models or expand order actions.
The pricing guides explain other billing units when you compare total store-agent costs. Choose the billing arrangement from the measured credit workload and your commitment period. Keep the operating budget large enough for the traffic you intend to serve, including the actions shoppers need after asking a product question.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.