Copilot Studio Pricing, Licensing & Plans (2025 Guide)

What is Copilot Studio and what is it for?

Copilot Studio is Microsoft’s platform to design conversational agents and “copilots” with a visual interface, integrate them with your data and systems via connectors, plugins, and agent actions, and publish them to channels like Microsoft Teams, the web, or WhatsApp. It’s the evolution of Power Virtual Agents with generative capabilities, orchestration, and grounding over enterprise data.

As of 2025, usage is measured in Copilot Credits, a common unit across classic answers, generative answers, actions, grounding, and flows. You can buy monthly packs (prepaid capacity) and combine them with pay-as-you-go (PAYG) for spikes. If you already have Microsoft 365 Copilot, certain internal interactions in Microsoft 365 don’t decrement credits.

Copilot Studio pricing: packs, pay-as-you-go, and included usage

Purchase options

• Prepaid packs: 25,000 Copilot Credits for USD 200/month per tenant. Ideal for steady demand.
• Pay-as-you-go (PAYG): USD 0.01 per Copilot Credit billed in Azure based on actual consumption. No minimum.
• Included usage with Microsoft 365 Copilot: in Teams/SharePoint/Copilot Chat, certain events (classic, generative, grounding, and actions) don’t consume credits for users licensed for Microsoft 365 Copilot.

Rule of thumb

If your expected monthly conversations × average credits per conversation ≥ 25,000, purchase at least 1 pack. For seasonality, combine pack + PAYG for peaks. For small pilots or one-off campaigns, start with PAYG only.

Pricing in euros (indicative) and VAT example (Spain)

Microsoft publishes USD amounts and bills in your local currency. As a reference, using the ECB rate 1 EUR = 1.1744 USD (09-Sep-2025), USD 200 ≈ EUR 170.30 (ex-VAT).

Final EUR prices and taxes are confirmed in your Microsoft 365/Azure admin centers.

Copilot Studio licensing: who needs what

To create and administer agents you need a tenant subscription (packs or PAYG) and assign creators the Copilot Studio User License (no cost). Internal end users can use the agent without a specific Copilot Studio license. Guest users aren’t supported.

How Copilot Credits are consumed (with examples)

Each interaction adds credits based on the event’s complexity. Typical summary:

• Classic response (scripted topic): 1 credit.
• Generative response (model): 2 credits.
• Agent action (invoke tools/steps): 5 credits.
• Tenant Graph grounding (tenant context): 10 credits.
• Agent flows (per 100 actions): 13 credits.
• AI tools (basic/standard/premium bands): consumption per output blocks.

Quick budgeting formulas

Daily example: 900 conversations with 4 classic and 2 generative per conversation ⇒ (4×1 + 2×2) × 900 = 7,200 credits. In PAYG ≈ €61.3/day ex-VAT; with a pack your unit cost drops by ~20–25% (depending on FX).

Capacity, limits, and allocation across environments

• Tenant pool: pack credits are shared across environments; set quotas if multiple teams are building.
• 125% enforcement: if you exceed 125% of prepaid capacity, Microsoft may enforce controls. Avoid this by enabling PAYG.
• Quotas & alerts: enable consumption alerts and per-environment limits to protect production.
• Dev/Test/Prod: separate environments and enforce publication gates so test traffic doesn’t distort budgets.

Where to publish: Teams, web, and WhatsApp

You can publish your agent in Microsoft Teams/Microsoft 365, on the web or your own apps (via the web channel or the Microsoft 365 Agents SDK), and on WhatsApp/SMS through Azure Communication Services.

• Teams & Microsoft 365: the recommended channel for internal assistants; with M365 Copilot many interactions don’t consume credits.
• Web/Custom apps: use the “Web app/Custom app” channel (Direct Line under the hood) and control authentication/CORS.
• WhatsApp: great for customer service; check regional requirements and number verification.

Security, GDPR, and governance

Copilot Studio integrates with Microsoft 365 and Power Platform. Use roles and DLP policies to prevent risky connectors from touching sensitive data. Define:

• Data policy: which sources the agent can and cannot query.
• Auditing: logging of conversations and actions (retention aligned to GDPR).
• Privacy: AI notices, legal basis, and a channel to exercise data rights.
• Publishing controls: prompt reviews, action limits, and rate limits for external channels.

Scenarios and cost estimates

1) Internal agent in Teams (employees with M365 Copilot)

For users licensed with Microsoft 365 Copilot, interactions inside Microsoft 365 (classic, generative, grounding, actions) don’t consume credits. Use credits for automations calling external APIs or for non-M365 channels.

2) Public web agent (FAQ + search)

With a 70% classic / 30% generative mix, 10,000 conversations/month ⇒ (0.7×1 + 0.3×2) × 10,000 ≈ 13,000 credits. Fits within 1 pack (25,000). For peaks, spill over to PAYG.

3) WhatsApp with agent actions

If each conversation uses 2 generatives + 1 action ⇒ 2×2 + 5 = 9 credits. 5,000 conversations/month ≈ 45,000 credits ⇒ 1 pack + 20,000 PAYG (≈ €170.3 + €170.3 ex-VAT at the ECB rate). Add the channel cost (WhatsApp/ACS) if applicable.

4) Support portal with grounding over documentation

Conversations with 2 generatives + 1 grounding ⇒ 2×2 + 10 = 14 credits per conversation. 3,000/month ⇒ 42,000 credits (1 pack + 17,000 PAYG). Reduce grounding by caching validated answers and improving classic FAQs.

How to get started step-by-step

1. Select capacity: pack for steady usage; PAYG for pilots or variability.
2. Configure billing in Power Platform/Azure (PAYG billing policy and per-environment quotas).
3. Assign creator licenses (Copilot Studio User License) to the team building the agent.
4. Design the MVP: scope, allowed data sources, and action limits.
5. Publish to Teams or a demo web to measure real per-event consumption.
6. Harden security: DLP, governance, auditing, and channel controls (tokens/Direct Line).
7. Optimize: review metrics, replace generative with classic where viable, batch actions.

Best practices to pay less and scale better

• Combine pack + PAYG for seasonal peaks (avoid 125% enforcement).
• Balance events: use “classic” for FAQs; reserve generative/grounding for complex queries.
• Concise prompts & reuse: shorter, reusable answers lower tokens and calls.
• Cache & answer bank: store validated answers and serve them as classic.
• Observability: consumption dashboard, alerts, and per-environment limits; review weekly.
• A/B iterate: compare flows to minimize expensive events without hurting quality.

Common mistakes (and how to avoid them)

• Publishing without quotas: you’ll burn through packs early. Set limits and alerts.
• Using generative for everything: higher costs and response variability. Cover FAQs with “classic.”
• Forgetting the channel: WhatsApp or web need channel security and sometimes extra costs.
• No Dev/Test/Prod split: mixing tests with live traffic skews the budget.
• No governance: define who can publish, which data sources are allowed, and how auditing works.

Frequently asked questions (FAQ)

Official links & key documentation

• Copilot Studio: licensing & pricing
• Copilot Credits: rates per event & consumption management
• Get access & assign licenses
• Channels: Teams, web/custom apps
• Publish to WhatsApp (via Azure Communication Services)
• Connect to web/custom apps (embed)
• Web channel security (Direct Line)
• Analyze credit consumption
• ECB EUR↔USD reference rate

Conclusion and next steps

With credit packs and PAYG configured—and with some usage included if you already have Microsoft 365 Copilot—Copilot Studio lets you start fast and scale with cost control. Design an MVP, measure real per-event consumption, harden security, and optimize your classic/generative/action mix to reduce cost per conversation.