Microsoft Copilot licensing in 2026. Price each SKU on its own meter.

Copilot is Microsoft's largest enterprise launch since Microsoft 365 itself, sold as one package across eight separately metered layers from $10 per developer to $50 per user. Price each layer alone, stage seats by uplift, and negotiate outside the EA.

What does Microsoft Copilot licensing include in 2026?

Microsoft Copilot is a family of separately priced products, each on its own meter. We count eight layers: Microsoft 365 Copilot, Copilot Studio, GitHub Copilot, Sales Copilot, Service Copilot, Security Copilot, Copilot Pro, and the surrounding consumption from Azure OpenAI, Graph connector overage and Power Platform Premium.

Microsoft presents them as one AI offer. The meters are seats, prepaid credits, pooled developer credits and provisioned compute hours, and each grows differently once usage takes off. That is why we price every layer on its own.

What has changed since Microsoft first sold these SKUs?

Several quotes still in circulation reflect the old structure. Check any proposal against these changes:

• Role agents folded in. Since October 2025 the $30 Microsoft 365 Copilot seat includes Sales, Service and Finance agents.
• Copilot Pro retired. Microsoft stopped selling it in October 2025, moved consumers to Microsoft 365 Premium at $19.99 a month, and ended support on August 1, 2026.
• Studio bills in credits. Copilot Credits replaced messages, with a published rate for each agent feature.
• GitHub moved to usage billing. From June 1, 2026, seats include AI credits equal to the seat price.
• Security Copilot arrived in E5. Microsoft 365 E5 and E7 include a monthly allocation of compute units.

How much does Microsoft 365 Copilot cost, and who needs a seat?

Microsoft 365 Copilot lists at $30 per user per month on an annual subscription, or $31.50 paid monthly. It is an add on to an eligible base license, for most enterprises Microsoft 365 E3 or E5, bought through an EA, the MCA or CSP.

With the per seat price published, the number of seats decides most of the spend. Account teams typically propose covering 60 to 80 percent of the Microsoft 365 base from day one. The productivity case supports a much smaller group:

• High uplift, 15 to 25 percent of users. Knowledge workers, analysts and document heavy roles. Deploy in year one.
• Medium uplift, 25 to 40 percent. Teams power users and mid tier collaborators, staged over years two and three.
• Low uplift, 40 to 60 percent. Front line and transactional roles. Defer them and give them Copilot Chat, which Microsoft includes with eligible Microsoft 365 subscriptions.

How should Copilot seats be staged over three years?

Expand in steps and let each year's usage data justify the next block. In our experience steady state coverage rarely goes above 50 percent, because the low uplift group seldom produces usage that holds up at $30 a month.

Now say Microsoft proposes 6,000 seats, the low end of its coverage range, at a 20 percent volume discount. That is $1,728,000 a year and $5,184,000 over three years. The staged plan costs $3,096,000 at full list, about 40 percent less, because the discount is paid on seats that sit idle.

Our Microsoft 365 Copilot pricing guide covers the per seat terms in more detail.

How is Copilot Studio priced, and why do agent budgets overrun?

Copilot Studio costs $200 a month per pack of 25,000 Copilot Credits, or $0.01 per credit pay as you go through Azure. Each agent feature draws a published number of credits, and three problems compound on this meter:

1. Pilot forecasts run low. Production agents routinely consumed 3 to 10 times what their pilots forecast.
2. Retrieval burns credits with no user present. A generative answer costs 2 credits and tenant graph grounding 10, including when an agent retrieves in the background.
3. Connectors add per user licenses. Enterprise data connectors often require Power Platform Premium licenses on top of the credits.

What does a Copilot Studio overrun look like?

Take a hypothetical help agent for staff without Copilot seats. Each conversation runs two generative answers and one tenant graph grounding, 14 credits in all. The pilot handles 2,000 conversations a month, or 28,000 credits.

The larger risk is a stoppage. Microsoft enforces prepaid capacity at 125 percent, then disables custom agents until you add capacity or turn on pay as you go. Two packs sized from the pilot hit that limit at 62,500 credits, about three weeks into the first production month.

Which Copilot Studio usage is free?

Employee facing agents are zero rated, within fair usage limits, for users who hold a Microsoft 365 Copilot license, when the agent runs under the signed in user's identity. Customer facing agents, agents for unlicensed staff and computer using agents bill in full.

The Copilot Studio pricing guide covers the rate table, and the Agent 365 licensing guide covers the agent control layer arriving next to this meter.

How is Security Copilot billed, and how much capacity do you need?

Security Copilot bills $4 per provisioned Security Compute Unit for every hour it is provisioned, plus $6 per overage SCU. Ten SCUs running around the clock cost roughly $30,000 a month: 10 times $4 times 720 hours is $28,800.

Microsoft 365 E5 and E7 now include 400 SCUs a month per 1,000 paid licenses, capped at 10,000, with no rollover. In Microsoft's own example, 4,000 licenses receive 1,600 SCUs, about 2.2 units for every hour of a 30 day month.

1. Consume the included units. Run the E5 or E7 allocation for a quarter and record daily use.
2. Commit a low baseline. Provision only the hourly SCUs your analysts need every day.
3. Burst for incidents. Pay overage when an incident needs capacity instead of holding it all month. The Security Copilot pricing guide works through the scheduling.

Is GitHub Copilot worth licensing for every engineer?

GitHub Copilot is worth it for active developers. It is the most successful Copilot SKU by adoption, and independent research backs a 15 to 30 percent improvement in code velocity.

Control the spend by scoping the population. Seats belong with people who write code most days; technical writers, QA analysts and project managers rarely justify one. Business lists at $19 and Enterprise at $39 per user per month, and the $10 Pro plan is for individuals.

What changed in GitHub Copilot billing in June 2026?

GitHub replaced premium requests with AI credits at $0.01 each. Business seats include 1,900 credits a month and Enterprise seats 3,900, pooled across the account with no carryover. Code completions stay unlimited.

Usage above the pool bills by default, so set enterprise or cost center budgets before the first month closes. The GitHub Copilot Enterprise licensing guide has the detail.

What happened to Sales Copilot, Service Copilot and Copilot Pro?

Sales Copilot and Service Copilot cost $50 per user or agent per month, the $30 seat plus a $20 role layer. Since October 2025 the $30 seat includes those agents, so move any $50 seats to the $30 seat at your next anniversary or renewal. Feature depth is greatest inside Dynamics 365, even where a Salesforce integration exists.

Why does the retired Copilot Pro still matter?

Copilot Pro sold at $20 a month and was never an enterprise SKU. Its replacement, Microsoft 365 Premium, allows employees to use a personal Copilot on work documents. If you do not want that, disable "Multiple account access to Copilot for work documents" in the Cloud Policy service.

Does Microsoft 365 E7 change the comparison?

E7 lists at $99 per user and bundles E5, Microsoft 365 Copilot, Agent 365 and the Entra Suite, which cost $117 bought separately ($60, $30, $15 and $12). E5 plus Copilot alone costs $90, so E7 saves money only for users who need both and at least one of the other two.

Agent execution still bills in Copilot Credits on top of E7. The Microsoft 365 E7 guide covers who it suits.

Why negotiate Copilot separately from the EA renewal?

Inside the renewal, Copilot becomes trade space, and its discount gets funded by giving back EA concessions you had already won. Run it as its own commercial workstream, with each layer priced against its own deployment need and meter. That costs nothing and is the most valuable structural decision in the purchase.

Why we advise against licensing the whole tenant for a bigger discount

A common recommendation is to commit broad coverage at signature because volume earns the best per seat price. We disagree. The discount is paid on seats that sit unused for a year or more, and it fixes a count before any telemetry exists. Buy the high uplift group, price later seats now, and let usage set each expansion.

What will the Microsoft account team say?

Which contract terms matter at Copilot signature?

The clauses signed at commitment carry as much weight as the price. Ask for these in writing:

• Expansion price hold. Additional seats at the signed price for the full term, fixed while you still have a choice.
• Anniversary reduction right. Seats that fail the usage test can go at each anniversary.
• Consumption caps with alerting. Written caps and alerts on the Studio and SCU meters.
• Pilot exit ramp. Pilot seats end or convert on agreed usage thresholds, so telemetry decides the year two population.

What have we seen in recent Copilot negotiations?

The largest savings came from how the purchase was structured. Unbundling the layers, staging deployment and scoping each SKU to its real population recovered 30 to 50 percent against the standard Copilot quote when Copilot ran as a separate workstream.

Consumption caused most budget failures. Studio agents that looked cheap in pilot ran far over forecast in production, and the Power Platform Premium licenses behind enterprise connectors arrived on invoices no Copilot line item warned about. Idle seats bought for the coverage pitch were the other cost, measured in our Copilot adoption analysis.

Copilot is a useful product wrapped in the most aggressive bundling exercise Microsoft has run in two decades. Price the layers separately and you get the product without paying for the bundle.

How do you check who should keep a Copilot seat?

The Microsoft 365 Copilot usage report in the admin center shows active users per app, and the Copilot Dashboard in Viva Insights breaks adoption down by team and app. Copilot Studio capacity sits in the Power Platform admin center, and GitHub shows credit use against budgets in its billing settings.

What to do next

1. Map the layers. List every Copilot SKU and meter in current quotes and contracts, including $50 role seats and Studio packs.
2. Segment users by uplift. Put the high uplift group in year one, name the medium tier for later, and give everyone else Copilot Chat.
3. Rebuild the Studio forecast. Apply the production multiple, check which agents are zero rated, and count Power Platform Premium users.
4. Use the included SCUs first. Measure three months of Security Copilot use against the E5 allocation before provisioning a baseline.
5. Scope GitHub Copilot. License active developers only and put budgets on the credit pool.
6. Separate the negotiation. Take Copilot out of the EA trade space and ask for the terms above. Our Microsoft practice can run it with you.

Frequently asked questions