Microsoft has built “Copilot” into a brand that spans the entire product portfolio — and in doing so, has created one of the most confusing licensing landscapes in enterprise software. There is Copilot for Microsoft 365, which costs $30 per user per month and requires a qualifying M365 plan. There is Copilot Studio, which uses a consumption-based messaging model. There is Copilot for Sales, which bundles M365 Copilot with CRM-specific capabilities. There is Copilot for Service, Copilot for Finance, and Microsoft Copilot for Security — each with a different pricing model, different prerequisites, and different entitlements. They share a name. They share very little else. An enterprise that purchases Copilot for Microsoft 365 expecting it to include Copilot Studio capabilities, or that licenses Copilot for Sales without realising it already includes the M365 Copilot entitlement, will either overpay or under-deliver. This guide maps every Copilot product, its licensing model, its prerequisites, what is included, what is not, and the commercial strategy for managing AI licensing costs as Microsoft embeds Copilot into everything.
Microsoft has deployed the Copilot brand across six distinct products. Understanding which product does what — and how each is licensed — is the essential first step before any procurement conversation.
The three pricing models at work across the Copilot family:
Model 1 — Per-user subscription. A flat monthly fee per assigned user, requiring a qualifying base licence. This is how Copilot for Microsoft 365, Copilot for Sales, Copilot for Service, and Copilot for Finance are priced.
Model 2 — Consumption-based (messages). A pool of “messages” purchased monthly or annually, consumed as users interact with custom AI agents and automations. This is how Copilot Studio is priced.
Model 3 — Capacity-based (security compute units). A per-unit-per-hour pricing model tied to the volume of security data processed. This is how Microsoft Copilot for Security is priced.
Each model creates different cost dynamics, different governance requirements, and different optimisation opportunities. Let us work through each product.
Copilot for Microsoft 365 is the product most enterprises think of when they hear “Microsoft Copilot.” It embeds AI assistance directly into the Microsoft 365 applications that every knowledge worker uses daily: Word, Excel, PowerPoint, Outlook, Teams, OneNote, and Loop.
In Word, Copilot drafts documents, summarises content, and rewrites text. In Excel, it analyses data, generates formulas, creates charts, and identifies trends. In PowerPoint, it creates presentations from prompts or existing documents. In Outlook, it summarises email threads, drafts replies, and prioritises the inbox. In Teams, it summarises meetings in real time, generates action items, and answers questions about meeting content. Across all applications, it accesses the user’s Microsoft Graph data — emails, files, chats, calendar — to provide contextually relevant responses.
Price: $30 per user per month.
Prerequisite: A qualifying Microsoft 365 plan. The qualifying plans are Microsoft 365 E3, E5, Business Standard, or Business Premium. Microsoft 365 F1, F3, and Business Basic do not qualify. This means Copilot cannot be deployed to frontline workers on F3 or to users on the entry-level Business Basic plan without first upgrading their base licence.
Total per-user cost: The Copilot licence is additive to the base M365 licence. An E3 user with Copilot pays $66/month ($36 + $30). An E5 user with Copilot pays $87/month ($57 + $30). A Business Standard user with Copilot pays $42.50/month ($12.50 + $30). See E3 vs E5 vs F3 and Business vs Enterprise plans for the base plan comparison.
Minimum purchase: Microsoft has removed the initial 300-seat minimum that was in place during early access. Copilot can now be purchased for any number of users. However, the per-user pricing does not decrease with volume through the standard EA discount structure — Copilot pricing is relatively firm compared to other M365 products. See negotiating Copilot pricing for the negotiation levers that do work.
The $30/user/month Copilot for M365 licence includes all Copilot capabilities within the M365 application suite: Word, Excel, PowerPoint, Outlook, Teams, OneNote, Loop, Whiteboard, and Microsoft 365 Chat (the cross-application AI assistant). It also includes a limited Copilot Studio entitlement: each Copilot for M365 licence includes the ability to create and use custom Copilot agents within the M365 environment, subject to a shared pool of Copilot Studio messages (discussed below).
Copilot for M365 does not include Copilot capabilities in Dynamics 365 (Sales, Service, Finance), Power Platform (Power Apps, Power Automate, Power BI), Azure OpenAI Service, or Microsoft Security products. Each of these requires separate Copilot licensing. Copilot for M365 also does not include the full Copilot Studio capacity for building enterprise-grade AI agents — the included entitlement is limited and additional capacity requires a Copilot Studio subscription.
For a 5,000-user enterprise deploying Copilot to all knowledge workers, the annual Copilot cost is $1.8 million — on top of existing M365 spend. The productivity gains must be substantial and measurable to justify this investment. Enterprises that deploy Copilot to 100% of users on day one pay for 100% of the licences while the productivity benefit concentrates in perhaps 20–30% of the user base. A phased rollout — starting with high-value user segments (executives, analysts, sales, content creators), measuring productivity impact, and expanding only where ROI is demonstrated — is the commercially disciplined approach. See the Copilot ROI assessment and how to justify or challenge AI feature costs.
Copilot Studio is Microsoft’s platform for building custom AI agents — conversational bots, automated workflows, and domain-specific AI assistants that go beyond the out-of-the-box Copilot for M365 capabilities. If Copilot for M365 is the AI assistant embedded in Office, Copilot Studio is the tool for building your own AI assistants for specific business processes.
Copilot Studio enables the creation of custom agents that can answer questions from enterprise knowledge bases, automate multi-step business processes, interact with external systems through connectors, handle customer-facing conversations (chatbots on websites and in Teams), and orchestrate complex workflows that combine AI reasoning with business logic. Agents built in Copilot Studio can be deployed within Teams, on websites, in Power Apps, or through other channels.
Pricing model: Consumption-based, measured in “messages.” A message is a single interaction between a user and a Copilot Studio agent — a question asked, a response generated, a workflow triggered. The pricing is structured as a monthly capacity allocation.
Standalone Copilot Studio subscription: Approximately $200 per tenant per month for 25,000 messages. Additional message capacity can be purchased in packs. The per-message cost at base pricing works out to approximately $0.008 per message, but the effective cost depends on agent complexity, response length, and whether the agent invokes external connectors or AI models that consume additional capacity.
Included entitlement with Copilot for M365: Each Copilot for M365 licence includes a limited Copilot Studio entitlement. As of 2026, each M365 Copilot user contributes a pooled message allocation that the tenant can use for custom agents. This included entitlement is sufficient for light usage — a handful of simple agents used by a small subset of users. Enterprises building production-grade AI agents that serve hundreds or thousands of users will exhaust the included entitlement quickly and require the standalone Copilot Studio subscription for additional capacity.
No prerequisite base licence: Unlike Copilot for M365, Copilot Studio does not require a specific M365 plan as a prerequisite. Any user with a Microsoft 365 or Office 365 licence (including F1, F3, E1) can interact with Copilot Studio agents. This makes Copilot Studio the only Copilot product accessible to frontline workers on F3 licences — a critical consideration for enterprises building AI agents for retail, manufacturing, or field-service use cases.
Copilot Studio’s consumption model creates cost unpredictability that per-user licensing does not. A popular agent that goes viral within the organisation can consume the entire monthly message allocation in days. An agent connected to an Azure OpenAI model for complex reasoning may consume multiple messages per interaction. And message consumption is difficult to forecast before the agent is deployed at scale. Governance is essential: set per-agent message limits, monitor consumption daily during rollout, and establish approval processes for new agent deployments that could consume shared capacity. For the broader AI cost management framework, see Azure OpenAI budgeting for CFOs and Power Platform licensing strategy.
Copilot for Sales embeds AI capabilities specifically designed for sales teams, connecting Microsoft 365 productivity tools with CRM data from Dynamics 365 Sales or Salesforce.
Copilot for Sales summarises CRM records in Outlook and Teams, drafts emails with CRM context (deal stage, recent interactions, account history), generates meeting preparation briefs from CRM data, updates CRM records from Outlook and Teams conversations (capturing notes, action items, and deal updates without switching to the CRM), and provides AI-generated sales insights based on pipeline and activity data.
Price: $50 per user per month.
Prerequisite: A qualifying Microsoft 365 plan (E3, E5, Business Standard, or Business Premium) — the same requirement as Copilot for M365.
Critical detail — Copilot for M365 is INCLUDED: The $50/month Copilot for Sales licence includes the full Copilot for Microsoft 365 entitlement. A user with Copilot for Sales does not need a separate $30/month Copilot for M365 licence. The $50 covers both the M365 Copilot capabilities (Word, Excel, PowerPoint, Outlook, Teams) and the sales-specific CRM integration features.
CRM requirement: Copilot for Sales requires either Dynamics 365 Sales Enterprise/Premium or Salesforce (Sales Cloud or Service Cloud). The CRM licence is separate and not included in the Copilot for Sales price.
The savings calculation: For a sales user who would otherwise have both Copilot for M365 ($30) and needs the CRM integration, Copilot for Sales at $50 represents $20/month incremental cost for the sales-specific features, not $50. The enterprise that purchases Copilot for M365 AND Copilot for Sales for the same user is paying $80/month when $50 would cover both. This is the most common Copilot licensing mistake in enterprises with large sales teams.
Adding to the confusion: Dynamics 365 Sales Enterprise and Premium already include embedded Copilot features within the Dynamics 365 application itself — AI-generated opportunity summaries, email drafts within D365, lead scoring, and pipeline analysis. These D365-native Copilot features are included in the Dynamics 365 licence and do not require the separate Copilot for Sales licence. The Copilot for Sales licence adds the M365 integration layer: the CRM context in Outlook and Teams, the cross-application AI assistance, and the ability to update CRM from M365 applications. See Dynamics 365 licensing and negotiating Dynamics 365 contracts.
Copilot for Service mirrors the Copilot for Sales model but targets customer service agents rather than sales representatives.
Copilot for Service connects Microsoft 365 with customer service CRM data (Dynamics 365 Customer Service, Salesforce Service Cloud, ServiceNow, or Zendesk). It summarises case histories, drafts response emails with case context, suggests knowledge base articles, provides real-time guidance during customer interactions in Teams, and helps agents resolve cases faster by surfacing relevant information from across the CRM, knowledge base, and previous interactions.
Price: $50 per user per month.
Prerequisite: A qualifying Microsoft 365 plan (E3, E5, Business Standard, or Business Premium).
Copilot for M365 is INCLUDED: Identical to Copilot for Sales, the $50/month includes the full Copilot for Microsoft 365 entitlement. A service agent with Copilot for Service does not need a separate M365 Copilot licence.
CRM requirement: Requires Dynamics 365 Customer Service, Salesforce Service Cloud, ServiceNow, or Zendesk. The CRM licence is separate.
The same overlapping-licence trap applies: do not purchase both Copilot for M365 ($30) and Copilot for Service ($50) for the same user. The $50 licence covers both.
Copilot for Finance targets finance professionals, connecting Microsoft 365 with ERP and financial systems.
Copilot for Finance assists with financial reconciliation in Excel (matching transactions across systems), variance analysis (identifying and explaining budget-to-actual discrepancies), collections management (drafting collection communications with account context), and financial reporting (generating narrative commentary on financial data). It connects to Dynamics 365 Finance, SAP, and other ERP systems through pre-built connectors.
Price: $30 per user per month.
Prerequisite: A qualifying Microsoft 365 plan (E3, E5, Business Standard, or Business Premium) AND a Copilot for Microsoft 365 licence. This is a key difference from Copilot for Sales and Service: Copilot for Finance does NOT include the M365 Copilot entitlement. It is an add-on to M365 Copilot, not a superset of it.
Total per-user cost: E3 ($36) + Copilot for M365 ($30) + Copilot for Finance ($30) = $96 per user per month. This is the most expensive per-user Copilot stack in the Microsoft ecosystem.
The licensing logic: Microsoft positioned Copilot for Sales and Service as standalone products that include M365 Copilot (making them attractive as a single purchase for sales/service teams). Copilot for Finance is positioned as a specialist add-on for users who already have M365 Copilot. The inconsistency is deliberate — sales and service teams are large and represent high-volume Copilot adoption opportunities that Microsoft wants to accelerate. Finance teams are smaller and already more likely to have M365 Copilot, so the add-on model generates incremental revenue without cannibalising existing M365 Copilot purchases.
Microsoft Copilot for Security is architecturally and commercially different from every other Copilot product. It is not a per-user subscription. It is a capacity-based service priced in Security Compute Units (SCUs).
Copilot for Security provides AI-assisted security operations: incident summarisation, threat intelligence analysis, script and query generation (KQL queries for Sentinel, PowerShell scripts for remediation), vulnerability assessment, posture management recommendations, and natural language investigation of security events across Microsoft Sentinel, Defender, Intune, and Entra ID. It enables security analysts to investigate threats faster by asking questions in natural language rather than writing complex queries.
Pricing model: Pay-as-you-go based on Security Compute Units (SCUs). Each SCU provides a defined amount of compute capacity per hour. The price is approximately $4 per SCU per hour. Organisations provision a number of SCUs based on their expected usage and can scale up or down.
No per-user pricing: Unlike every other Copilot product, there is no per-user-per-month fee. The cost is based on capacity provisioned and consumed, similar to Azure consumption pricing. A security team of 10 analysts using Copilot for Security might provision 3–6 SCUs at a cost of $12–$24 per hour, or approximately $8,640–$17,280 per month (assuming standard business hours). The actual cost depends on query volume, investigation complexity, and data volume processed.
Prerequisites: Copilot for Security works best with (but does not strictly require) Microsoft Sentinel, Defender for Endpoint, Defender for Office 365, and Entra ID. Organisations using Microsoft’s security stack get the most value. Organisations using third-party security tools can still use Copilot for Security but with reduced integration depth.
The cost management challenge: The capacity model makes costs proportional to usage, which is good for cost efficiency but challenging for budgeting. A major security incident that triggers intensive investigation will spike SCU consumption. Organisations should establish SCU provisioning policies, usage monitoring, and monthly budget caps to prevent cost surprises. See AI budgeting for CFOs.
The most expensive mistakes in Copilot licensing come from purchasing overlapping entitlements. Here is the complete overlap map:
Copilot for Sales ($50) INCLUDES Copilot for M365 ($30). A user with Copilot for Sales should NOT also have a Copilot for M365 licence. The $50 covers both. Purchasing both costs $80/month when $50 would suffice — a $360/user/year waste.
Copilot for Service ($50) INCLUDES Copilot for M365 ($30). Same structure as Sales. Do not stack M365 Copilot on top of Copilot for Service.
Copilot for Finance ($30) REQUIRES Copilot for M365 ($30). This one is additive, not inclusive. Copilot for Finance is an add-on to M365 Copilot, not a replacement for it. Total: $60/month for the combined capability.
Copilot for Sales + Copilot for Service: If a user needs both sales and service capabilities (rare but possible in hybrid roles), the licensing is not clearly discounted. Consult Microsoft or your Licensing Solution Partner for combined pricing.
Copilot Studio entitlement in M365 Copilot: Every Copilot for M365 licence includes a limited Copilot Studio message allocation. This included allocation is pooled at the tenant level. Before purchasing a standalone Copilot Studio subscription, verify whether the included M365 Copilot entitlement is sufficient for your custom agent needs.
Copilot for Security is independent: Copilot for Security operates on a completely separate licensing model (SCU capacity) and has no overlap with any per-user Copilot product. It does not include or require any other Copilot licence.
Dynamics 365 embedded Copilot features are independent: Copilot features built into Dynamics 365 applications (Sales, Customer Service, Finance) are included in the Dynamics 365 licence and do not require any separate Copilot purchase. The separate Copilot for Sales/Service licences add M365 integration, not D365-native AI features.
Copilot pricing is among the firmest in the Microsoft portfolio. Microsoft has limited discounting flexibility on Copilot compared to mature products like M365 E3 or Azure. However, several negotiation strategies exist:
Copilot purchased as part of an EA renewal or major amendment provides more negotiation leverage than a standalone Copilot purchase mid-term. Microsoft’s account team has more flexibility when Copilot is part of a larger commercial conversation that includes M365 renewal, Azure commitments, and Dynamics 365. See key leverage points for Microsoft deals.
Rather than purchasing Copilot for all eligible users at once, negotiate a phased commitment: 500 users in Year 1 with the right to expand at the same pricing in Years 2 and 3. This provides cost control and ROI validation while locking in pricing for future expansion. Microsoft may accept lower initial volume if the expansion path is contractually committed.
The per-user model assumes equal usage across all licensed users. In practice, Copilot usage varies dramatically: power users may interact with Copilot 50+ times daily, while occasional users may use it once a week. Advocate for usage-based or tiered pricing that reflects actual consumption patterns. Microsoft has been resistant to this approach but the pressure from enterprises is growing. See negotiating Copilot pricing models.
Before purchasing any Copilot licences, map every user’s complete Copilot entitlement. Identify users who would receive Copilot for Sales (which includes M365 Copilot) and remove them from the M365 Copilot purchase list. Identify users with Copilot for M365 and verify whether the included Copilot Studio entitlement covers your custom agent needs before buying a separate Copilot Studio subscription. The overlap audit should save 5–15% of total planned Copilot spend.
Copilot Studio’s message-based pricing can escalate quickly for popular agents. Negotiate a message capacity commitment within the EA at a discounted per-message rate, with overage protection (a cap on per-message overage pricing) to prevent cost surprises. Treat Copilot Studio capacity like Azure consumption: negotiate the commitment and the overage rate separately. See negotiating Azure commitments for the analogous approach.
Copilot products process enterprise data through Microsoft’s AI models. The data usage and privacy terms should be reviewed and negotiated as part of the Copilot procurement: data residency, model training opt-out, output ownership, and liability for AI-generated content. See the AI services terms analysis for legal teams.
Microsoft’s AI licensing strategy is still evolving, and procurement leaders should plan for the trajectory, not just the current state.
Copilot will be embedded everywhere. Microsoft is systematically embedding Copilot capabilities into every product in the portfolio: M365, Dynamics 365, Power Platform, Azure, Security, Windows, and more. Each embedding creates a new licensing decision. The cumulative effect for an enterprise that says “yes” to every Copilot product is an AI cost layer that could add 20–40% to total Microsoft spend within 2–3 years.
Per-user pricing may evolve. The $30/user/month per-user model is under pressure from enterprises that argue (correctly) that not all licensed users derive equal value. Microsoft may introduce tiered pricing, usage-based options, or bundled AI entitlements within higher-tier M365 plans. Enterprises negotiating multi-year Copilot commitments should include provisions for pricing adjustment if Microsoft changes the model.
Copilot Studio consumption will grow. As enterprises build more custom agents, Copilot Studio message consumption will become a significant and growing cost category. Treat it with the same governance rigour as Azure consumption: monthly budgets, usage monitoring, department-level chargebacks, and regular optimisation reviews.
Competitive alternatives are emerging. Google Gemini for Workspace, Salesforce Einstein Copilot, and dedicated AI platforms (OpenAI Enterprise, Anthropic) provide competitive pressure on Microsoft’s AI pricing. Evaluating alternatives — even partially — creates negotiation leverage. An enterprise that demonstrates it can deploy Google Gemini for specific use cases has more pricing flexibility in the Microsoft Copilot conversation than one that is fully committed to the Microsoft AI stack. See Azure OpenAI vs OpenAI for enterprise use and keeping agreements flexible for future AI services.
“Microsoft has made Copilot the centrepiece of its revenue growth strategy. Every enterprise conversation with Microsoft in 2026 will include a Copilot pitch. The enterprises that manage this well will deploy Copilot selectively, measure ROI rigorously, avoid the overlap traps, and negotiate with the understanding that Microsoft needs Copilot adoption numbers as much as the enterprise needs AI productivity gains. The enterprises that manage this poorly will add $30 per user per month across the entire workforce, discover that 70% of licences are underutilised, and face a renewal negotiation where Microsoft has no incentive to reduce a price the enterprise already accepted.” — Fredrik Filipsson, Co-Founder, Redress Compliance
Yes. Copilot for Sales ($50/user/month) includes the full Copilot for Microsoft 365 entitlement. A user with Copilot for Sales gets all M365 Copilot capabilities (Word, Excel, PowerPoint, Outlook, Teams) plus the sales-specific CRM integration. Do not purchase both Copilot for M365 and Copilot for Sales for the same user — the $50 licence covers both.
Copilot for Microsoft 365 provides AI assistance within the M365 applications (Word, Excel, Outlook, Teams). Copilot Studio is a platform for building custom AI agents that can be deployed in Teams, on websites, or within business applications. They are complementary products with different licensing models: M365 Copilot is per-user ($30/month), while Copilot Studio is consumption-based (messages). Each M365 Copilot licence includes a limited Copilot Studio entitlement for light custom agent usage.
Frontline workers on Microsoft 365 F3 cannot use Copilot for Microsoft 365, Copilot for Sales, Copilot for Service, or Copilot for Finance — all of these require E3, E5, Business Standard, or Business Premium as a prerequisite. However, F3 users can interact with Copilot Studio agents because Copilot Studio does not require a specific M365 plan as a prerequisite. This makes Copilot Studio the primary path for delivering AI capabilities to the frontline workforce.
Copilot for Security uses a capacity-based model measured in Security Compute Units (SCUs) at approximately $4 per SCU per hour. It is not priced per user. Organisations provision SCUs based on expected security analyst usage and pay for the provisioned capacity. A typical deployment for a 10-person security team might cost $8,640–$17,280 per month depending on SCU provisioning and usage patterns.
No. Unlike Copilot for Sales and Copilot for Service (which include M365 Copilot), Copilot for Finance ($30/user/month) is an add-on that requires a separate Copilot for Microsoft 365 licence ($30/user/month). The total cost for a finance user is M365 plan + M365 Copilot ($30) + Copilot for Finance ($30). This is the most expensive per-user Copilot stack at $96/month for an E3 user.
Redress Compliance helps enterprises evaluate Copilot products, avoid licensing overlaps, negotiate favourable AI pricing terms, and build Copilot deployment strategies that deliver measurable ROI. Independent advisory with no Microsoft commercial relationship.