Three AI Products, Three Licensing Models
Microsoft's AI strategy delivers generative AI through three distinct products, each with a fundamentally different licensing and pricing structure. Understanding these differences is essential for CIOs managing budgets, compliance, and vendor negotiations.
GitHub Copilot
AI coding assistant for developers. Per-user SaaS subscription ($19–$39/month). Unlimited code suggestions. No long-term commitment required. Licensed through GitHub, not the EA.
M365 Copilot
AI assistant embedded in Word, Excel, Teams, Outlook. $30/user/month add-on to M365 E3/E5. Annual commitment required. Deeply integrated with Microsoft Graph and enterprise data.
Azure OpenAI Service
API access to GPT-4, GPT-3.5, DALL-E, and embeddings models. Consumption-based pricing (per token). Variable cost. Requires Azure subscription. Build custom AI applications.
Copilot Studio
Low-code platform for building custom AI agents on Azure OpenAI. Available as standalone subscription or with prepaid capacity packs. Extends Copilot beyond Office into custom workflows.
"The most common licensing mistake enterprises make with Microsoft AI is treating all three products as variations of the same thing. They are not. GitHub Copilot is a flat-rate developer tool. M365 Copilot is a fixed-cost productivity add-on with an annual lock-in. Azure OpenAI is a consumption service with variable, potentially unbounded costs. Each requires a different budgeting approach, a different negotiation strategy, and a different ROI framework."
GitHub Copilot: Licensing, Pricing, and Enterprise Controls
GitHub Copilot is an AI pair-programming tool that provides real-time code suggestions, code generation, and natural-language-to-code capabilities directly within developers' IDEs. For enterprises, it is available in two subscription tiers.
| Feature | Copilot Business ($19/user/month) | Copilot Enterprise ($39/user/month) |
|---|---|---|
| Code completions | ✅ Unlimited (within rate limits) | ✅ Unlimited (within rate limits) |
| Chat in IDE | ✅ General code questions | ✅ Code questions + private codebase context |
| Private codebase indexing | ❌ Not available | ✅ Indexes your repos for contextual answers |
| Pull request summaries | ❌ Not available | ✅ AI-generated PR descriptions and reviews |
| IP indemnification | ✅ Copilot Copyright Commitment | ✅ Copilot Copyright Commitment |
| Data privacy | ✅ No training on your code | ✅ No training on your code + enhanced isolation |
| Prerequisite | GitHub Team or Enterprise plan | GitHub Enterprise Cloud plan |
| Billing model | Per-seat monthly subscription | Per-seat monthly subscription |
Key licensing details: GitHub Copilot is licensed as a SaaS subscription outside the Microsoft EA. It is purchased through GitHub's platform, billed per assigned seat per month, with no long-term commitment. There is no usage-based component — developers get unlimited code suggestions within rate limits. GitHub has introduced the concept of "premium requests" for advanced features, with a generous monthly allowance per user. Enterprises can manage seat assignments through GitHub's organisation settings, integrating with SSO and Entra ID for access control.
Negotiation opportunity: GitHub Copilot is not typically included in EA pricing, but large enterprises have successfully negotiated volume discounts on Copilot seats when bundling with GitHub Enterprise Cloud or other Microsoft products. If you are purchasing 500+ developer seats, engage your Microsoft/GitHub account team — promotional pricing, extended evaluation periods, and bundled discounts are available for strategic accounts. Read GitHub Copilot Business: Licensing & Enterprise Controls.
Microsoft 365 Copilot: The $30/User Add-On
Microsoft 365 Copilot is an AI assistant embedded directly into Word, Excel, PowerPoint, Outlook, and Teams. It generates content, analyses data, summarises meetings, and answers natural-language questions using your organisation's data through Microsoft Graph — all within the security boundary of your M365 tenant.
$30/User/Month Add-On
M365 Copilot costs $30/user/month ($360/year), billed annually with a 12-month commitment. This is in addition to your existing M365 subscription. For an E5 user at ~$57/month, adding Copilot brings the total to ~$87 — a 53% increase. For E3 at ~$36/month, total reaches ~$66 — an 83% increase.
M365 E3/E5 Required
Copilot requires a base Microsoft 365 E3, E5, Business Standard, or Business Premium licence. Users on lower-tier plans, standalone Office licences, or legacy on-premises deployments are not eligible. Education (A3/A5) and Government (G5) plans have separate availability timelines and pricing.
No Obligation to Licence Everyone
You can purchase Copilot for a subset of users — specific departments, roles, or power users — rather than the entire organisation. The 300-seat minimum that existed at launch has been removed. Start with a targeted pilot to validate ROI before scaling.
Professional Services Firm: Targeted Copilot Deployment Saves $1.4M vs. Full Rollout
Situation: A 5,000-user professional services firm on M365 E5 evaluated Copilot at $30/user/month. A full rollout would cost $1.8M annually. Initial pilots showed that productivity gains were concentrated in document-heavy roles — consultants, analysts, and marketing — while operational staff (facilities, reception, field technicians) derived minimal benefit.
Decision: The firm licensed Copilot for 1,200 users (24% of the workforce) in high-value roles, at an annual cost of $432K.
Data Privacy and Compliance
M365 Copilot operates entirely within your Microsoft 365 tenant boundary. It accesses only data that the individual user already has permission to view — respecting existing security labels, DLP policies, and access controls. User prompts and AI responses are processed transiently in Microsoft's cloud and are not used to train the underlying AI models. Copilot inherits M365's compliance certifications (GDPR, ISO 27001, SOC 2, HIPAA eligible). Administrators can control Copilot availability per user, monitor usage through audit logs, and apply content-filtering policies.
Azure OpenAI Service: Consumption-Based AI Platform
Azure OpenAI Service provides direct API access to OpenAI's foundation models — GPT-4, GPT-4o, GPT-3.5 Turbo, DALL-E, and embedding models — through Azure's enterprise cloud infrastructure. Unlike the per-user Copilot products, Azure OpenAI is billed entirely on consumption.
| Model | Input Cost (per 1K tokens) | Output Cost (per 1K tokens) | Typical Use Case |
|---|---|---|---|
| GPT-4 (8K context) | ~$0.03 | ~$0.06 | Complex reasoning, document analysis, code generation |
| GPT-4 (32K context) | ~$0.06 | ~$0.12 | Long-document processing, multi-document synthesis |
| GPT-4o | ~$0.005 | ~$0.015 | General-purpose — lower cost than GPT-4 with comparable quality |
| GPT-3.5 Turbo | ~$0.0005 | ~$0.0015 | High-volume, lower-complexity tasks — chatbots, summarisation |
| Ada Embeddings | ~$0.0001 | N/A | Vector search, semantic retrieval, RAG applications |
| Prices are indicative and subject to change. Azure pricing varies by region and provisioned throughput tier. Enterprises with MACC (Microsoft Azure Consumption Commitment) can apply existing Azure credits toward OpenAI usage. | |||
Cost management challenge: Azure OpenAI's variable pricing is a double-edged sword. You pay only for actual usage — no cost for idle users or off-hours. But costs can scale rapidly if a high-traffic application or broad internal deployment drives millions of token requests daily. A single complex GPT-4 query costs pennies, but enterprise-scale deployment can generate five- or six-figure monthly bills without controls.
Implement Token Budgets and Cost Alerts
Use Azure Cost Management to set spending thresholds and alerts. Define per-application and per-department token budgets. Configure automatic throttling or model downgrading (GPT-4 → GPT-3.5) when budgets approach limits. Without these controls, a single misconfigured application can consume your entire Azure AI budget in days.
Choose the Right Model for Each Workload
Not every task requires GPT-4. Route simple queries (FAQ bots, basic summarisation) to GPT-3.5 Turbo at a fraction of the cost. Reserve GPT-4 and GPT-4o for complex reasoning, document analysis, and code generation where quality justifies the premium. Model routing alone can reduce Azure OpenAI costs by 40–60% without meaningful quality degradation for most enterprise workloads.
Negotiate Azure OpenAI into Your MACC
If your enterprise has a Microsoft Azure Consumption Commitment (MACC), Azure OpenAI usage counts toward that commitment. Negotiate your MACC to include projected AI consumption — this locks in committed-spend discounts for your OpenAI usage. For very high-volume AI workloads (millions of tokens daily), engage Microsoft about custom pricing agreements or reserved capacity. Read Negotiating Azure OpenAI Credits in New EAs.
IP Indemnification: The Copyright Commitment
Microsoft's Copilot Copyright Commitment, effective since late 2023, extends IP indemnification to all paid Copilot products (GitHub Copilot Business/Enterprise, M365 Copilot, and Azure OpenAI Service when using built-in content filters). If AI-generated output inadvertently infringes third-party copyrights, Microsoft will defend the customer and cover damages — provided the customer used the service as intended and did not deliberately bypass content filters.
This commitment is a significant contractual protection that competitors (including direct OpenAI API access) do not always match at the same level. Verify that your Microsoft Product Terms or enterprise agreement explicitly includes the Copyright Commitment for every AI service you deploy. The commitment applies only to paid tiers — free versions of Copilot are excluded. For regulated industries where IP liability is a board-level concern, the Copyright Commitment can be a decisive factor in favour of Microsoft's AI products over alternatives.
Negotiation Strategies for Microsoft AI Licensing
Microsoft is aggressively pushing Copilot adoption, which creates negotiation opportunities for well-prepared enterprises.
| Strategy | How It Works | When to Use |
|---|---|---|
| Bundle Copilot with EA renewal | Offer to add Copilot licences in exchange for a broader EA discount — Microsoft values Copilot adoption metrics and may discount the overall agreement | At EA renewal when adding new AI products to the agreement |
| Start with a pilot, expand conditionally | Negotiate a 3–6 month pilot at reduced pricing, with expansion contingent on measured ROI. Microsoft prefers conditional adoption over no adoption | When the organisation has not validated Copilot's value for its specific workflows |
| Reference competitive alternatives | Google Gemini for Workspace, direct OpenAI API, or AWS Bedrock are credible alternatives. Mentioning evaluation of these creates pricing pressure | When Microsoft is firm on Copilot list pricing |
| Negotiate Azure OpenAI into MACC | Include projected AI consumption in your Azure commitment to secure committed-spend discounts on token usage | When renewing or expanding Azure consumption commitments |
| Request deployment support | If Microsoft will not discount price, negotiate value-adds: free deployment consulting, training days, change management support, or extended pilot periods | When price flexibility is limited but Microsoft wants to drive adoption |
"Microsoft's Copilot pricing has softened considerably since launch. Initial demand justified list price, but as enterprises report mixed ROI — particularly for roles where AI productivity gains are modest — Microsoft's sales teams have become more open to creative deal structures: phased adoption, conditional expansion, bundled discounts, and deployment support at no charge. The leverage exists for enterprises willing to negotiate rather than accept list price."
Enterprise Deployment Best Practices
🎯 AI Deployment Readiness Checklist
- Involve your CISO from Day 1: Configure admin controls, sensitivity labels, and DLP policies before enabling Copilot. Establish guidelines for what users should and should not submit to AI tools.
- Run a structured pilot before scaling: Select 50–200 users in document-heavy roles. Measure time saved, output quality, and user satisfaction over 60–90 days. Use pilot data to build the business case for expansion.
- Deploy selectively, not universally: Copilot ROI varies dramatically by role. Licence high-value users first and review utilisation quarterly. Reassign underused seats to different users rather than paying for unused capacity.
- Implement Azure OpenAI cost controls: Set per-application token budgets, cost alerts, and automatic model-downgrading rules. Without controls, consumption costs can exceed budgets within days.
- Verify IP indemnification in your agreement: Confirm the Copilot Copyright Commitment covers every AI service you deploy. Ensure your Product Terms explicitly reference it.
- Monitor and optimise continuously: Review Copilot licence utilisation and Azure OpenAI consumption monthly. Reallocate licences based on actual usage patterns. Downgrade models where GPT-3.5 delivers adequate quality at a fraction of GPT-4 cost.
Strategic Recommendations for CIOs
🎯 Microsoft AI Licensing Master Checklist
- Map each AI product to the right licensing model: GitHub Copilot (per-seat SaaS), M365 Copilot ($30/user add-on with annual commitment), Azure OpenAI (per-token consumption).
- Budget for M365 Copilot as a 50–80% increase in per-user cost: $30/month on top of E3 ($36) or E5 ($57) changes the economics significantly. Validate ROI before committing.
- Deploy Copilot to high-value roles first: Consultants, analysts, marketers, and executives generate the strongest ROI. Operational roles typically see modest benefit.
- Negotiate Copilot pricing during EA renewal: Bundle AI licences with broader Microsoft spend. Reference competitive alternatives (Google Gemini, OpenAI direct) for pricing pressure.
- Include Azure OpenAI in your MACC: Projected AI consumption should be part of your Azure commitment to secure volume discounts.
- Implement token-level cost controls on Azure OpenAI: Set budgets, alerts, and model-routing rules. Use GPT-3.5 for simple tasks, GPT-4 only where quality demands it.
- Verify IP indemnification for every AI service: Confirm the Copilot Copyright Commitment is explicitly referenced in your agreement. It covers paid tiers only.
- Ensure data privacy commitments are documented: Confirm that prompts, responses, and enterprise data are not used to train AI models. Azure OpenAI provides stronger data isolation than direct OpenAI API.
- Review AI licence utilisation quarterly: Reassign underused Copilot seats. Adjust Azure OpenAI budgets based on actual consumption patterns.
- Engage independent advisers for AI contract negotiation: Microsoft's AI licensing is new, pricing is evolving, and standard terms may not protect your interests. Independent review ensures fair pricing and adequate contractual safeguards.