In Short: One Brand, Four Charging Models
"Copilot" is a brand covering at least six products, and they are licensed in four fundamentally different ways: per user per month (Microsoft 365 Copilot, GitHub Copilot), included at no extra cost (Microsoft 365 Copilot Chat), consumption against Fabric capacity (Copilot in Fabric and Power BI), and metered consumption (Copilot Studio credits, Security Copilot compute, Foundry tokens). Budgeting goes wrong when organisations assume one model covers the family.
This guide maps the 2026 landscape. Prices quoted are list prices that have been stable for some time; always confirm against Microsoft's current price list and your own agreement, because packaging in this space changes faster than most procurement cycles.
Microsoft 365 Copilot: The Per-User Flagship
The product most people mean by "Copilot" - the assistant inside Teams, Word, Excel, Outlook and PowerPoint, grounded in your organisation's Microsoft 365 data - is licensed per user per month at a list price of 30 dollars, on annual commitment, on top of a qualifying Microsoft 365 plan.
What has changed by 2026 is not the headline price but what sits behind it: agent capabilities, the Microsoft IQ context layer grounding answers in enterprise data, and Copilot Cowork, the agentic workspace that reached general availability in June 2026. The licence increasingly buys an agent platform seat rather than a chat assistant.
The purchasing question is coverage, not price. Very few organisations need it for everyone; almost all have a tier of heavy Teams-Excel-Outlook users for whom the productivity case is straightforward. Start there, measure, expand.
Microsoft 365 Copilot Chat: The Free Tier That Changes the Maths
Included with Microsoft 365 subscriptions is Copilot Chat: web-grounded chat with enterprise data protection, plus pay-as-you-go agent access. It lacks the deep Office integration and work grounding of the full licence, but for a large population of staff it answers the question "can we give everyone something safe" without a per-user fee.
The practical pattern we recommend: Copilot Chat as the organisational default, full Microsoft 365 Copilot for the roles that demonstrably use the integration. That split is also the honest answer to shadow AI usage, because staff denied any sanctioned tool will use unsanctioned ones.
Copilot in Fabric and Power BI: Capacity, Not Licences
Copilot features across Fabric and Power BI are not sold per user. They draw capacity units from your Fabric capacity, appearing as consumption alongside refreshes and queries. Users need workspace access and an admin-enabled capacity, nothing more.
Two budgeting consequences follow. First, the marginal cost of a Copilot answer is invisible to the user producing it, so governance is about capacity monitoring rather than licence counts. Second, heavy Copilot usage on a small capacity competes with your refreshes and reports. We cover the mechanics, the SKU history and the monitoring approach in what Copilot in Fabric actually costs.
Copilot Studio and Foundry: Paying for Agents
Custom agents are billed on consumption in both platforms, differently.
- Copilot Studio - agent usage draws down purchased credit or message allowances, in prepaid packs or pay-as-you-go; simple to start, and costs scale with conversation volume
- Microsoft Foundry - pure Azure consumption: model tokens, hosting, storage and whatever services the agent touches; more control, more variables, and a real need for cost monitoring
Packaging in this layer has been revised repeatedly, which is itself the lesson: build the cost model around measured usage of one pilot agent before committing to volume. Our guide to what AI agents cost to run works through realistic scenarios, and Copilot Studio vs Microsoft Foundry covers which platform fits which build.
GitHub Copilot and Security Copilot: The Specialists
GitHub Copilot remains per-user monthly with individual, business and enterprise tiers; the business tiers add policy controls, IP indemnity and organisational management. For data teams, it is often the highest-return AI licence in the building, and agent skills for Fabric mean it now reaches into the data estate itself.
Security Copilot is billed through dedicated compute (security compute units), a consumption model aimed at security operations teams rather than general staff. It matters to data leaders mainly where security and data governance overlap.
The Decision Framework
Strip the brand away and the questions are ordinary procurement.
- Which roles measurably benefit from deep Office integration? Those get Microsoft 365 Copilot; everyone else starts on Copilot Chat
- Is your Fabric capacity sized for Copilot consumption on top of existing workloads?
- Do you have a concrete agent use case, or are you buying Studio credits on faith?
- Are engineers covered by GitHub Copilot business tiers with policy control?
Then measure. Every licence in this family produces usage telemetry, and six months of real data beats any projection. The organisations that overspend are the ones that bought the brand; the ones that get value bought against named roles and measured workloads.
Sources and Further Reading
- Microsoft 365 Copilot overview
- Copilot in Fabric overview
- Microsoft Copilot Studio documentation
- Microsoft Fabric pricing
Frequently asked
The list price has held at 30 dollars per user per month since launch, on an annual commitment, on top of a qualifying Microsoft 365 subscription. Volume agreements can land below list, and Microsoft has periodically bundled it into higher-tier suites, so check your enterprise agreement before assuming the list price.
Microsoft 365 Copilot Chat gives licensed Microsoft 365 users a secured chat experience with enterprise data protection at no extra per-user cost, without the deep integration into Word, Excel, Outlook and Teams data that the paid Microsoft 365 Copilot licence adds. It is the sensible default for staff who do not justify a full licence.
It is not licensed per user at all. Copilot in Fabric consumes capacity units from your Fabric capacity, so the cost shows up as capacity consumption rather than a licence line. Users need no Copilot licence to use Copilot features inside Fabric and Power BI; they need access and a capacity with Copilot enabled.
Copilot Studio is billed on consumption: agent usage draws down message or credit allowances purchased in packs or pay-as-you-go. The exact packaging has changed more than once, so treat any specific number you read as a snapshot and confirm against Microsoft's current pricing page before budgeting.
Microsoft Foundry is Azure consumption: you pay for model inference (tokens), hosting and associated Azure services rather than per-user licences. That makes Foundry agent costs scale with usage, which suits high-volume scenarios but demands cost monitoring from day one.
A common pattern: Microsoft 365 Copilot for the executives and analysts who live in Teams, Excel and Outlook; GitHub Copilot for the engineers; Copilot in Fabric via existing capacity for BI work; and Copilot Studio credits only once a concrete agent use case exists. Buying broad before proving value is the most common overspend we see.
