The Copilot Studio Licensing Summary
Microsoft rebranded Power Virtual Agents (PVA) as Copilot Studio in November 2023. The product has also expanded significantly — it now encompasses both the original PVA chatbot builder and a new generative AI agent-building capability that integrates with Azure OpenAI and Microsoft's broader Copilot ecosystem.
The licensing model is one of Microsoft's most complex, combining a session-based consumption model for traditional PVA-style bots with a message-based model for generative AI agents, plus a Microsoft 365 Copilot add-on path and a standalone Copilot Studio add-on. Understanding which licensing path applies to your use case is essential before building anything.
This guide explains the full licensing structure, what's included in existing M365 plans, where the costs accumulate, and how to negotiate Copilot Studio in your Enterprise Agreement.
The Rebranding and Architecture Change
Power Virtual Agents was Microsoft's low-code chatbot building platform — integrated with Power Automate, Dataverse, and Teams. Copilot Studio extends this with a fundamentally new capability: generative AI agents that use large language models (GPT-4 via Azure OpenAI) to answer questions from knowledge bases, SharePoint content, websites, and custom data sources without requiring explicit conversation flows.
From a licensing standpoint, this creates two distinct product types within Copilot Studio:
Classic bots (topic-based): Built using the traditional PVA conversation designer with explicit topics, branching, and actions. These are licensed on a session basis.
Generative AI agents (knowledge-based): Built using Azure OpenAI integration, consuming content from knowledge sources to answer questions dynamically. These are licensed on a message basis.
Many enterprise deployments use both capabilities within the same agent — the licensing model applies to the dominant interaction type, which creates confusion during build and estimation.
Licensing Paths: The Four Routes to Copilot Studio
| Licensing Path | What It Includes | Cost Basis | Best For |
|---|---|---|---|
| M365/Teams (Included) | Copilot Studio for Teams — bots scoped to Teams only, no Dataverse, no external channels | Included in M365 E1/E3/E5 | Simple internal Teams chatbots only |
| Copilot Studio Add-On | Full Copilot Studio — all channels, Dataverse integration, generative AI, external access | ~£150/tenant/month (25,000 messages included) + overage | Standalone bot deployment, single use case |
| Power Platform per-user | Power Apps per-user includes Copilot Studio with Dataverse — tenant-wide bot building | ~£15/user/month (Power Apps per-user) | Organisations with broad Power Platform deployment |
| M365 Copilot Extension | Build Copilot extensibility agents deployed within M365 Copilot for the licensed user | M365 Copilot licence (£24.70/user/month) | Extending M365 Copilot with custom agents for Copilot-licensed users |
The Teams-Scoped Version: What's Included in M365
Every M365 E1, E3, and E5 licence includes access to a Teams-scoped version of Copilot Studio. This allows users to build and deploy bots within Microsoft Teams without any additional licence cost. The key constraints of this Teams-only version:
- Bots can only be deployed within Teams (no web, email, phone, external channels)
- No Dataverse database integration (Power Apps Dataverse requires a separate licence)
- No premium connectors in Power Automate flows triggered from the bot
- No external knowledge sources for generative AI (SharePoint knowledge with Copilot Studio requires the add-on)
- Limited to Microsoft's standard AI features — no Azure OpenAI custom configuration
For simple internal HR FAQ bots, IT helpdesk first-response automation, or leave request handling within Teams, the included version is functional. For anything requiring external data sources, multiple channels, or significant AI capability, you need the add-on.
The Teams-scoped Copilot Studio is frequently overlooked during Power Platform licensing discussions. Before purchasing the Copilot Studio add-on, map whether your use cases can be delivered within Teams. If they can, you have a deployed capability with zero incremental cost. The add-on is only necessary when you genuinely need external channels, Dataverse, or the full generative AI toolkit.
The Copilot Studio Add-On: Session and Message Licensing
The Copilot Studio standalone add-on is the primary purchase path for organisations building enterprise chatbots and agents. It is priced based on consumption — specifically, sessions for classic topic-based bots and messages for generative AI agents.
Session-Based Licensing (Classic Bots)
A session is a single conversation between a user and a bot, from initiation to completion or timeout. Each session consumes one unit regardless of the number of exchanges within that session. Sessions time out after 30 minutes of inactivity.
The Copilot Studio add-on includes 25,000 sessions per month at approximately £150/month (around £6/1,000 sessions). Additional sessions beyond the included pool are charged at approximately £0.60/100 sessions.
The critical planning question is: how many sessions will your bot actually generate? For an internal IT helpdesk bot serving 5,000 employees with a 10% monthly interaction rate (500 sessions/month), the included pool is vastly more than sufficient. For a high-volume customer service bot handling 100,000 interactions per month, you are well into overage territory.
Message-Based Licensing (Generative AI Agents)
When bots use generative AI capabilities — answering questions from knowledge sources, using Azure OpenAI for dynamic responses, or operating in "generative answers" mode — consumption is measured in messages rather than sessions. Each AI-generated response consumes one or more messages depending on the complexity of the query and the knowledge retrieval involved.
The Copilot Studio add-on includes approximately 25,000 messages per month. A typical generative AI conversation consumes 3–5 messages per user interaction (query + knowledge retrieval + response generation). At 5 messages per interaction, 25,000 messages supports approximately 5,000 user interactions per month — significantly fewer than the session-based equivalent.
Generative AI message consumption is dramatically higher than session consumption for the same conversation volume. Organisations that size their Copilot Studio purchase based on session-equivalent assumptions for generative AI bots routinely see 3–5× their budgeted consumption. Build a usage model before going live — not after. Microsoft's own usage analytics in the Copilot Studio admin centre are essential monitoring tools during the first 60 days of deployment.
Copilot Studio Pricing: Full Cost Structure
| Licence Component | Approximate Cost | Includes | Overage Rate |
|---|---|---|---|
| Copilot Studio Add-On (per tenant/month) | ~£150/month | 25,000 sessions + 25,000 messages | £0.60/100 sessions; £0.006/message |
| Additional session pack (1,000 sessions) | ~£6 | 1,000 additional sessions | — |
| Additional message pack (25,000 messages) | ~£200 | 25,000 additional messages | — |
| Copilot Studio in Teams (M365 E1/E3/E5) | Included | Teams channel only, no Dataverse | No overage model |
| Copilot Studio via Power Apps per-user | Included | Full Copilot Studio for bot builders | Session/message consumption still applies for deployed bots |
An important clarification: the Copilot Studio per-tenant add-on gives you the environment to build and deploy bots. The session and message consumption charges apply to the actual use of deployed bots. Bot builders (the employees creating the bots) need either the Copilot Studio per-user licence or Power Apps per-user — they are separate from the consumption charges.
Copilot Studio and M365 Copilot: The Intersection
The introduction of M365 Copilot (£24.70/user/month) created an important but often misunderstood relationship with Copilot Studio. M365 Copilot users can access custom agents built in Copilot Studio within their M365 Copilot interface — these appear as additional Copilots in Microsoft 365. For M365 Copilot users, their agent interactions draw from the M365 Copilot licensing, not from the Copilot Studio session/message pool.
This means organisations deploying M365 Copilot broadly have a mechanism to deploy Copilot Studio agents to their Copilot-licensed population without incurring additional session/message consumption costs. For organisations with 500+ M365 Copilot licences building internal-facing agents, this is a materially different cost model than using Copilot Studio standalone.
The practical implication: if you are deploying M365 Copilot for knowledge workers, build your internal agents as M365 Copilot extensions first, consuming the Copilot licence. Use standalone Copilot Studio consumption licences for external-facing bots, customer service channels, and non-Copilot user populations. This architecture minimises your total spend.
Governance and Cost Control
Copilot Studio consumption can grow unpredictably in organisations that enable low-code bot building broadly. The following governance framework prevents uncontrolled spend:
Centralised bot registration: Require all Copilot Studio bots to be registered with IT/Power Platform governance before deployment. This gives you visibility of the bot population and the ability to estimate consumption before going live.
Consumption monitoring: The Copilot Studio admin centre provides session and message consumption reporting. Configure monthly alerts at 70% and 90% of included quota. Don't discover overages in the invoice — monitor proactively.
Development vs production environments: Use Copilot Studio's environment segregation to keep development and testing bots isolated from the production consumption pool. Test traffic should not consume production licences.
Channel restriction policy: For internal bots, restrict deployment to Teams and internal web only. Each additional external channel (website, WhatsApp, Dynamics, etc.) multiplies potential session/message volume. External channel approvals should require a usage estimate and governance sign-off.
For the broader governance context, see our guide to Power Platform governance and the complete Power Platform licensing guide.
Negotiating Copilot Studio in Your EA
Copilot Studio is one of the few Microsoft products where consumption-based pricing creates genuine negotiation leverage — because your actual usage is a variable that neither party knows with certainty at EA signing.
Commit to capacity, not seat count. Unlike M365 licences, Copilot Studio consumption can be negotiated as a capacity commitment over the EA term. Propose a three-year message/session commitment in exchange for a per-unit discount. Microsoft will typically offer 15–25% discount for a meaningful three-year volume commitment.
Negotiate overage rates separately. Standard EA terms will include list-rate overages. Negotiate a capped overage rate as part of the EA — this protects you from unexpected spikes while giving Microsoft confidence in your long-term consumption commitment.
Use Power Platform as portfolio leverage. If your organisation uses Power Apps, Power Automate, and Copilot Studio, negotiate these as a Power Platform portfolio commitment rather than as separate products. The combined spend creates discount leverage on each individual product. See our Power Platform licensing complete guide for the full portfolio context.
Pilot before committing. Negotiate a 90-day pilot at reduced rates or within the base add-on before committing to a large session/message pool at EA renewal. This gives you real consumption data to base your three-year commitment on.
Copilot Studio vs Third-Party Alternatives
| Dimension | Copilot Studio | ServiceNow Now Assist | IBM Watson Assistant | Google Dialogflow CX |
|---|---|---|---|---|
| M365/Teams integration | Native | Via connector | Custom integration | Custom integration |
| Low-code builder | Strong | Moderate | Moderate | Moderate |
| Generative AI quality | GPT-4 based | LLM-based | Watson NLP | Gemini-based |
| Enterprise ITSM integration | Via Power Automate | Native (ServiceNow) | Strong | Moderate |
| Governance/compliance | Full M365 perimeter | ServiceNow scope | IBM Cloud | Google Cloud |
| Consumption model predictability | Session/message variable | User-based | MAU-based | Request-based |
For organisations standardised on Microsoft 365, Copilot Studio's primary advantage is native integration: Teams deployment, SharePoint knowledge sources, Power Automate triggers, Dataverse data, and M365 security/compliance. If your bot's primary function is answering questions from SharePoint content or automating M365 workflows, the integration advantage is substantial.
ServiceNow's chatbot capability has the edge for organisations where ITSM is the primary use case and ServiceNow is already deployed. IBM Watson and Google Dialogflow offer more sophisticated NLU for complex conversational scenarios but require more significant integration investment in Microsoft-first environments.
Frequently Asked Questions
Is Power Virtual Agents still available?
Power Virtual Agents was rebranded as Copilot Studio in November 2023. The product is the same platform, now with additional generative AI capabilities layered on top of the original PVA framework. All existing PVA bots continue to function and can be managed in Copilot Studio. There is no separate PVA licence — it is now all Copilot Studio.
Do I need a Copilot Studio licence to build a Teams bot?
No. The Teams-scoped Copilot Studio experience is included in M365 E1/E3/E5 licences. You can build and deploy bots within Teams without any additional licence. The Copilot Studio add-on is only required when you need external channels, Dataverse integration, or generative AI capabilities beyond what's available in the Teams-scoped version.
What counts as a session vs a message?
A session is a single conversation from start to end (timeout or closure). A message is a single AI-generated response within a conversation when using generative AI / knowledge retrieval features. A 10-message conversation with a generative AI agent = 10 messages consumed. The same conversation with a classic topic-based bot = 1 session consumed. Generative AI agents are typically 3–5× more expensive on a per-conversation basis.
Can I use Copilot Studio to build agents for M365 Copilot users?
Yes. Copilot Studio is the primary tool for building Microsoft 365 Copilot extensions (declarative agents and plugin agents). These appear as custom Copilots within the M365 Copilot interface. M365 Copilot-licensed users interact with these agents through their Copilot licence; the consumption does not draw from the standalone Copilot Studio session/message pool.