Copilot Studio licensing is more nuanced than it first appears. Here's a clear breakdown of the models, who needs what, and where costs can catch you out.
Two Licensing Models, Plus Two Additional Access Contexts
It helps to think of access to Copilot Studio in two distinct categories.
The actual licensing models:
- Monthly per-user licence — a Copilot Studio user licence assigned by an admin in M365 Admin Center. Requires the tenant to have a prepaid Copilot Credits pack subscription first. There's no additional per-user fee once your tenant has Copilot Credits provisioned.
- Pay-as-you-go — access granted via the Copilot Studio Authors role in PPAC, linked to an Azure subscription. No per-user licence required, but agent usage is metered and billed via Copilot Credits.
Additional access contexts (not full substitutes):
- Microsoft 365 Copilot licence — includes Copilot Studio agent capabilities, but scoped to M365 apps (Teams, SharePoint, Copilot Chat). Not a complete replacement for a standalone Copilot Studio licence in all scenarios.
- Trial licence — a temporary sandbox that lets you create and test agents but not publish them. See the separate post on the publishing workaround.
Builders vs Users — A Critical Distinction
One of the most important things to understand is that the people who build agents and the people who use agents are licensed differently.
Builders need appropriate licensing and environment permissions to create and publish agents.
End users — the people in your organisation who chat with a published agent — do not need a Copilot Studio licence. They just need access to the channel the agent is published to (Teams, SharePoint, a website etc.).
The Two Paid Models in Practice
Monthly Per-User Licence
Assign licences to your builders. End users chatting with published agents are not additionally metered per interaction — usage is bundled and predictable for typical scenarios rather than charged per conversation.
Best for: Organisations with consistent agent usage and a clear set of identified builders.
Pay-As-You-Go
Builders don't need per-user licences, but the setup requires:
- An Azure subscription
- Copilot Credits enabled in the tenant
- Appropriate environment configuration in PPAC
End user interactions are then metered and billed per Copilot Credit consumed via that Azure subscription. Costs are variable — the more conversations and actions your agents handle, the more you pay. Costs are especially sensitive to actions that call external systems or orchestrate multiple steps per conversation.
Best for: Pilots, low usage scenarios, or organisations where demand is uncertain. Start here, collect real usage data, then decide whether to switch to monthly.
Where Costs Can Catch You Out
Even on a monthly licence, there are edges where additional costs can apply:
Premium connectors — if an agent uses premium Power Platform connectors to integrate with third-party systems, this may introduce additional Power Platform licensing or pay-as-you-go costs. This is a Power Platform concern rather than a Copilot Studio-specific charge, but it affects your total cost of ownership.
Advanced compliance features — eDiscovery, insider risk management, sensitivity label enforcement — these are broader Microsoft 365 compliance capabilities (typically E5 level) that Copilot inherits and respects, but which require their own licensing. Depending on your governance model these may be a requirement rather than an optional extra.
Complex agent architectures — multi-agent orchestration and extensive knowledge source retrieval can consume more Copilot Credits per interaction than a simple single-turn FAQ agent.
Environment and DLP Strategy — Indirect but Significant Impact
Copilot Studio sits inside the Power Platform, which means your environment strategy and DLP policies directly affect both what your agents can do and what they cost.
- Environment isolation — building agents in the default environment vs a dedicated production environment affects governance, data separation, and who has access
- DLP policies — connector restrictions at environment or tenant level can block agent actions entirely, regardless of licensing
- DLP enforcement — as of early 2025, DLP enforcement for Copilot Studio is active by default for all tenants. Granular per-agent DLP exceptions are no longer generally supported in most tenants
Getting your environment strategy right before deploying agents is as important as getting the licensing right. An agent that's perfectly licensed but hits a DLP wall at runtime is still a failed deployment.
The Microsoft Estimator
Before deploying agents to a large organisation, use the Microsoft Copilot Studio agent usage estimator to forecast Copilot Credits consumption. Factor in:
- How many users will interact with the agent
- How frequently
- How complex the conversations are — simple FAQ vs multi-step actions with external connectors
This is especially important under pay-as-you-go where a heavily used agent deployed to a large user base can generate a significant and unexpected Azure bill, even though none of those end users need a licence.
Bottom Line
Most organisations should start with pay-as-you-go to understand real usage, then move to monthly licensing once demand stabilises.
Licensing at a Glance
| Plan / Licence | What it is / Who it's for | Key Features | What's Missing / Extra / Metered |
|---|---|---|---|
| Copilot Chat (Free) | Available to anyone with a Microsoft account or eligible work/school account without a paid Copilot licence. | Basic conversational AI. Web-grounded responses only. Copilot Chat available inside Microsoft 365 apps (Word, Excel, PowerPoint, Outlook, OneNote) — provides basic assistance and can reference the open document for context. | No access to Microsoft Graph data (emails, files, meetings). No full Microsoft 365 Copilot experiences. Some premium features and model upgrades may be limited or usage-metered. |
| Microsoft 365 Personal / Family | For home users. Personal = one user; Family = up to six users. | Copilot in Office apps (Word, Excel, PowerPoint, Outlook, OneNote). 1 TB OneDrive per user. Copilot features such as writing, summarisation, and design help. | Not connected to Microsoft Graph work data. No SharePoint/Teams integration. No admin or compliance features. Agent creation not supported. |
| Microsoft 365 Copilot – Business Plans | Add-on licence for Microsoft 365 Business Standard / Business Premium tenants. Supports up to 300 users. | Copilot in Word, Excel, PowerPoint, Outlook, Teams. Grounded in Microsoft Graph data (emails, files, Teams chats, SharePoint, OneDrive). Core security and compliance for SMBs. | No advanced enterprise compliance tools (Purview, Insider Risk Management). Hard cap at 300 licensed users. |
| Microsoft 365 Copilot – Enterprise Plans | Add-on licence for Microsoft 365 E3/E5, Office 365 E3/E5, F3. No user limit. | Same Copilot integration as Business: apps + Graph grounding. Enterprise security, compliance, and governance (DLP, eDiscovery, audit, Purview). Scales to thousands of users. | Some enterprise features require additional licences (advanced Purview scenarios, insider risk analytics). Copilot Studio usage may incur extra costs. |
| Copilot Studio / Agents | Add-on capacity for building and managing custom Copilot agents. Available to Business or Enterprise tenants. | Build custom agents in Copilot Studio. Integrate external connectors, APIs, and databases. Manage agent lifecycle in Teams or other apps. | Agent usage governed by Copilot Credits (capacity packs or pay-as-you-go). Premium connectors and large-scale publishing may incur extra costs. Not available for Personal/Family tenants. |
Table information drawn from Microsoft Learn — Copilot Studio licensing overview.