Copilot is a commercial, run it that way
Microsoft Copilot is the largest enterprise product launch since Microsoft 365 itself and the most aggressive bundling exercise Microsoft has run in two decades: eight distinct SKU layers from $19 per developer to $50 per user per month plus consumption meters. Microsoft positions it as a unified package; the disciplined response is to unbundle the eight elements, anchor each to actual deployment requirement, and run Copilot as a separate commercial workstream from the EA renewal.
Prepared by Redress Compliance · August 7, 2026 · Microsoft advisory. The buyer side framework recovering 30 to 50 percent against the standard Copilot quote.
Executive summary
The portfolio is eight layers, and the bundle is the sales strategy.
Microsoft 365 Copilot at $30 per user per month is the load bearing SKU.
Around it sit Copilot Studio on pay per message, GitHub Copilot at $10, $19, and $39 per developer tiers, Sales Copilot and Service Copilot at $50, Copilot Pro at $20 for the consumer tier, Security Copilot on Security Compute Units at $4 per hour, and the surrounding consumption, Azure OpenAI.
Graph connector overage, and Power Platform Premium. Each layer prices on a different meter, and the unified package framing exists to stop you noticing.
The uplift population is the sizing truth Microsoft's coverage target ignores.
The user base breaks three ways: 15 to 25 percent high uplift, knowledge workers and document heavy roles, deployed year one; 25 to 40 percent medium, staged years two and three; and 40 to 60 percent low uplift, front line and transactional roles, deferred.
Microsoft positions immediate coverage at 60 to 80 percent of the M365 base; the staged trajectory runs 15 to 20 percent in year one, 25 to 30 in year two, 35 to 45 in year three, and steady state rarely exceeds 50 percent, because the productivity case is genuinely narrower than the positioning.
The consumption meters are where forecasts die.
Copilot Studio's $200 per month buys 25,000 messages with overage at a cent each.
And production agents routinely consumed 3 to 10 times what pilots forecast, with RAG queries burning messages on background activity no user sees and Power Platform Premium licenses stacking on top for the enterprise connectors.
Security Copilot compounds the same way: ten SCUs provisioned around the clock run roughly $30,000 a month, and the buyer move is the lowest committed baseline with bursts for incidents.
The one documented productivity case is also the cheapest SKU.
GitHub Copilot is the most successful layer by adoption, with independent research backing 15 to 30 percent code velocity improvement, and its discipline is population scoping: the active developer population, not the broader engineering organization of writers, QA analysts, and project managers.
Applied across all eight layers, unbundling plus staged deployment plus per SKU population scoping is the framework that recovered 30 to 50 percent against the standard Copilot quote, negotiated as its own workstream, never inside the EA renewal's trade space.
The eight SKU layers, priced
| SKU | List price | Meter | Population discipline |
|---|---|---|---|
| Microsoft 365 Copilot | $30 per user per month | Seats on E3 or E5 | The uplift segments, not the M365 base |
| Copilot Studio | $200 per month per 25,000 messages, then $0.01 | Messages, including RAG | Forecast at 3 to 10x the pilot |
| GitHub Copilot | $10, $19, $39 per developer | Seats by tier | Active developers only |
| Sales and Service Copilot | $50 per user or agent per month | Seats | Roles where $50 beats the $30 base |
| Security Copilot | $4 per SCU per hour | Provisioned compute | Lowest baseline, burst for incidents |
| Copilot Pro | $20 per month | Seats | Consumer and SMB, not enterprise |
The role SKUs price against the base SKU, not against zero.
Sales Copilot and Service Copilot at $50 sit on top of, or instead of, the $30 Microsoft 365 Copilot for the same person, so the question per role is whether the incremental layer earns its increment, with feature depth greatest inside Dynamics 365 even where the Salesforce integration exists.
And the eighth layer, the surrounding consumption of Azure OpenAI, Graph connector overage, and Power Platform Premium, arrives on invoices no Copilot line item warned about.
The staged trajectory, against the coverage pitch
- Year one, 15 to 20 percent: the high uplift population, knowledge workers, analysts, and document heavy roles, where the $30 provably returns.
- Year two, 25 to 30 percent: high plus the measured medium tier, Teams power users and mid tier collaborators, with real usage data steering the expansion.
- Year three, 35 to 45 percent: high plus medium plus targeted low uplift roles, each addition justified by the prior year's telemetry.
- Steady state, rarely above 50 percent: against Microsoft's 60 to 80 percent immediate coverage pitch, because 40 to 60 percent of most user bases is front line and transactional.
- The commercial consequence: a staged commitment with expansion options beats a broad year one commitment discounted for volume you will not use.
The Copilot licensing brief
The eight SKU map, the uplift segmentation, the consumption traps, and the eleven move framework worked on a representative estate.
Get the white paper →The consumption traps, Studio and Security
Copilot Studio's three traps compound: message volume estimation is notoriously inaccurate, with production agents consuming 3 to 10 times pilot forecasts; RAG queries count as messages even with no user in the conversation, burning volume on background retrieval.
And the enterprise data connectors often require Power Platform Premium per user licenses stacked on the consumption bill.
Security Copilot runs the same consumption logic on provisioned time, roughly $30,000 a month at ten SCUs around the clock, with the schedule and burst discipline worked in the Security Copilot pricing guide.
The adoption side, where the seats bought in the coverage pitch sit unused, is measured in the Copilot adoption analysis, and the agent platform layer arriving next to the Studio meter in the Agent 365 licensing guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
The separate workstream, and why it recovers the margin
The single most valuable structural decision costs nothing: Copilot negotiates as its own commercial workstream, never inside the EA renewal, because bundled into the renewal it becomes trade space, a Copilot discount funded by giving back EA concessions you had already won.
Run separately, each SKU anchors to its own deployment requirement and its own meter:
Code velocity improvement backed by independent research, the one SKU with proven uplift, scoped to active developers.
Against the standard quote, from unbundling, staged deployment, and per SKU population scoping.
The contract clauses signed at Copilot commitment carry the same weight as the price: expansion options priced at signature rather than at expansion, the right to reduce seats at anniversary, consumption caps with alerting on Studio and SCU meters, and pilot exit ramps that let telemetry.
Not the coverage pitch, decide the year two population.
Copilot is a genuinely useful product wrapped in the most aggressive bundling exercise Microsoft has run in two decades, and the buyer who prices the eight layers separately gets the product without funding the exercise.
Your first five moves
- Unbundle the eight layers and anchor each to its own deployment requirement and meter, refusing the unified package frame.
- Segment the user base by uplift, deploying the 15 to 25 percent high tier first and letting telemetry justify each expansion.
- Forecast Studio at 3 to 10 times the pilot, with RAG background burn and Power Platform Premium stacking counted.
- Commit Security Copilot at the lowest baseline and buy incidents as bursts, not standing capacity.
- Run Copilot as a separate workstream from the EA, where the 30 to 50 percent lives. The Microsoft practice runs the negotiation with you.
Frequently asked questions
What does Microsoft 365 Copilot cost?
$30 per user per month at list, as an add on to Microsoft 365 E3 or E5 through EA, MCA, and CSP channels, embedding AI across Word, Excel, PowerPoint, Outlook, Teams, and the Graph.
The real cost question is population: only 15 to 25 percent of a typical user base is high uplift, and steady state deployment rarely exceeds half the M365 base.
What are the eight Microsoft Copilot SKUs?
Microsoft 365 Copilot at $30 per user; Copilot Studio at $200 per 25,000 messages then a cent each; GitHub Copilot at $10, $19, and $39 per developer tiers; Sales Copilot and Service Copilot at $50; Copilot Pro at $20 for consumer and SMB; Security Copilot at $4 per Security Compute Unit hour.
And the surrounding consumption, Azure OpenAI, Graph connector overage, and Power Platform Premium.
How should enterprises stage a Copilot deployment?
Against the uplift segments, not Microsoft's 60 to 80 percent coverage pitch: year one at 15 to 20 percent of users covering the high uplift population, year two at 25 to 30 adding the measured medium tier, year three at 35 to 45, with steady state rarely above 50 percent.
Each expansion is justified by the prior year's usage telemetry rather than the positioning.
What are the Copilot Studio pricing traps?
Three that compound: production agents routinely consume 3 to 10 times what pilots forecast; RAG queries count as messages even with no user in the conversation, burning volume on background retrieval.
And enterprise data connectors often require Power Platform Premium per user licenses on top of the consumption bill.
Forecast at the production multiple and cap the meter with alerting.
Is GitHub Copilot worth it?
It is the most successful Copilot SKU by adoption and the only one with independently documented productivity benefit, 15 to 30 percent code velocity improvement.
The discipline is population scoping: deploy to the active developer population at the $19 Business or $39 Enterprise tier, not to the broader engineering organization of tech writers, QA analysts, and project managers.
Should Copilot be negotiated inside the EA renewal?
No, and this is the highest value structural decision available: bundled into the renewal, Copilot becomes trade space where its discount is funded by returning EA concessions you had already won.
Run it as a separate commercial workstream, each SKU anchored to actual deployment requirement, which is where the framework's 30 to 50 percent recovery against the standard quote comes from.
