Microsoft 365 E7 pricing and negotiation. Price each layer before you accept the bundle.

Microsoft 365 E7 packs E5, Copilot, Entra Suite and Agent 365 into one $99 seat. Copilot is the costly layer, and buyers who gave it to everyone used a third of what they paid for.

What does Microsoft 365 E7 cost, and what is inside it?

Microsoft 365 E7 lists at $99 per user per month on an annual commitment, or $90.45 per user per month without Teams. Microsoft announced it on March 9, 2026 as "The Frontier Suite" and made it generally available on May 1, 2026.

The SKU stacks four products that Microsoft also sells on their own. At list they add up to $117 per user per month, an $18 gap on paper. The gap helps only users who need Copilot plus at least one of the two newer add ons, as the comparison below shows.

How the July 2026 price change moved the E7 gap

On July 1, 2026, Microsoft raised Microsoft 365 E5 from $57 to $60 and E3 from $36 to $39, and added Security Copilot and several Intune capabilities to E5. The step from E5 to E7 therefore shrank from $42 to $39 per user per month without E7 itself changing.

Expect a rep to present E7 as "only $39 more than you pay today." The uplift and the E7 list arithmetic are covered in our price increase brief, and the full SKU contents in the Microsoft 365 E7 guide.

Is E7 a product or a bundle?

It is a real product now, and it still behaves like a bundle. Before May 2026, "E7" was the label for Microsoft moving its top tier upward: E5 as the qualifying base, Copilot per user on top, and security capabilities that partly repeat what E5 carries. The SKU now exists; the mechanics are unchanged.

Treat any E7 offer as four prices packed into one, and ask for each layer's price in writing. If the bundle wins only on convenience, there is little reason to take it.

Why does Copilot drive most of the E7 premium?

Copilot is the most expensive layer above E5. In the quotes we reviewed, it added 50 to 90 percent on top of the net E5 seat price.

The range is worth reading closely. At list, $30 on a $60 E5 seat is exactly 50 percent, and before July it was about 53 percent on $57. Every quote above that had E5 discounted more deeply than Copilot. An E5 net rate of $40 against Copilot at $30 gives 75 percent, and $34 gives about 88 percent.

What bundling hides

A bundle's first job is to stop you seeing separate prices. Sold on its own line, a Copilot premium of that size draws hard questions from a CFO:

• Adoption. How many users will open Copilot every week, and by when?
• Scope. Which roles have a use case that saves measurable time?
• Return. What should the spend deliver in year one?

Folded into a single E7 tier, the same premium becomes a feature of a product, and products tend to be accepted or declined whole. The economics are identical; only the questions the quote invites have changed, and we read that as the purpose of the packaging.

Is E7 cheaper than buying E5 and the add ons separately?

Only for users who need Copilot plus Entra Suite or Agent 365 on top of E5. For a user who needs E5 and Copilot and nothing else, the parts cost $90 and E7 costs $9 more.

Discounts change the absolute numbers but rarely the order. Rerun the table with your quoted net rates, one row per user group, and count the users in the last three rows, where E7 comes out cheaper. That number, not your total headcount, is the size of a sensible E7 order.

A three year example for a 3,000 user tenant

Say 3,000 users all need E5, and Microsoft proposes E7 for everyone on a 36 month term. The alternative keeps E5, licenses Copilot for a pilot group of 600 in year one, then 1,200 and 1,800 as usage supports it. All figures are at list.

The phased option costs $2,916,000 less over the term, about 27 percent. If every user really needs Entra Suite, the gap narrows to $1,620,000, about 15 percent. That second case shows why the security layer deserves its own audit.

Why the E5 base upgrade costs more than it looks

E7 contains E5, so every user swept into the bundle is also upgraded to E5, whether the role needs it or not. From E3 at $39 to E5 at $60, that is $21 per user per month before any AI.

Take 2,000 E3 users moved to E7. The base upgrade alone adds $42,000 a month. If 30 percent of them use Copilot in year one, the seats in use are worth $18,000 a month, less than half the base upgrade. Our Microsoft 365 licensing guide sets out which roles need E5.

Check the security layer against what E5 already covers

E5 already includes Defender for Endpoint Plan 2, Defender for Office 365 Plan 2, Purview compliance, Entra ID P2 with Privileged Identity Management and access reviews, and now Security Copilot as well. Paying twice for what the base includes is the oldest overpay in the Microsoft stack.

The new security content in E7 is mainly Entra Suite and Agent 365. If you already run a third party secure access or identity governance product, map the overlap before giving the bundle credit. Our pages on Entra Suite, Agent 365 and E5 security cover the detail.

Why does an all in E7 rollout pay for adoption that has not happened?

Because the bundle prices every seat as a Copilot user from day one. Buyers who licensed the full bundle for all users reached 25 to 40 percent Copilot adoption in year one, while paying for 100 percent.

That leaves 60 to 75 percent of the most expensive layer unused in the first year. Training, use case design and manager support drive adoption, and none of them arrive with the license key.

Why we advise against licensing Copilot for everyone to drive adoption

A common argument, from Microsoft and some partners, is that adoption stalls when only some users have access, so you should license the whole company and let usage spread. We disagree. In the negotiations we advised, universal licensing did not produce universal use, and the unused seats stayed on the bill.

The better course is a defined group with a real use case, Copilot priced on its own line, and expansion gates tied to measured usage. Pre agreed rates for later seats remove the risk that waiting costs you the discount. Our Copilot adoption research tracks what drives usage once seats are assigned.

Pay for Copilot after your users adopt it, at a rate you fixed before they did.

How to set the pilot group and the expansion gates

1. Pick roles. Find the ones with repeatable writing, summarizing or analysis work.
2. Measure for two quarters. Track active use in the Microsoft 365 Copilot usage report before you commit to more seats.
3. Write the gate into the contract. State the usage level that triggers the next tranche and the per seat price that applies to it.
4. Keep the add on separate. Buy Copilot as its own line on E5, so each tranche avoids a tier change.

Phased buyers paid for the curve they actually rode, and their deals came in 15 to 30 percent below the all in bundle for the same eventual footprint. The saving came from refusing to prepay for adoption. Our Copilot pricing guide covers current Copilot terms.

What have we seen in Microsoft 365 top tier negotiations since 2024?

Across 30 to 40 Microsoft 365 top tier negotiations we advised from 2024 to 2026, the bundle premium was consistently underestimated and adoption consistently overestimated. Most of that period predates the E7 SKU, so the early offers came as E5, Copilot and security add ons folded into one blended tier.

• Simplicity as the pitch. The bundle was presented as easier to manage, with one SKU and one invoice.
• No stated adoption number. The quotes assumed every seat would use Copilot but never wrote that assumption down.
• The base upgrade underneath. E3 users moved to E5 inside the AI conversation, with little discussion of whether their roles needed it.
• Bundle first, every time. Every phased deal we advised had been offered the full bundle first.

The E7 SKU has not changed these patterns. A single orderable SKU makes the all in offer easier to present, so expect to see it first.

What will the Microsoft account team say about E7, and how should you answer?

Expect a push toward one SKU for the whole tenant. These are the lines we hear most, with replies that keep the talk on your numbers.

• "E7 is simpler, one SKU for everyone." Simplicity is not worth $39 per user per month for users who will not touch the extra layers.
• "You get $117 of value for $99." Ask for the table by user group. The saving exists only for users who need all four products.
• "The E7 discount needs the whole tenant." Ask for E7 pricing at several quantities, and for Copilot as an add on to E5 at an equivalent discount. Compare in writing.
• "Adoption will follow once everyone has access." Ask Microsoft to commit to a reduction right if year one usage stays below an agreed level.
• "This price expires at quarter end." Quarter ends, and the June 30 fiscal year end above all, are when Microsoft has the most room to move. Start early enough that you can let one pass without signing.

Which contract terms protect the E7 price after you sign?

Price protection on every unit rate matters most, because the seats you add in year two should not arrive at that year's list price. A bundle rate without a cap is an introductory offer, whatever the quote calls it.

• Layer price schedule. An appendix with the net price of each component, so later changes are measured against known numbers.
• Rate hold for the term. Fixed unit prices for E7 and each component for all 36 months, including seats added later.
• Ramp schedule. Copilot quantities that step up by year, so cost follows adoption.
• Reduction or step down right. The option to move users from E7 to E5 plus Copilot, or to cut Copilot seats, at each anniversary. Do not assume the standard enrollment terms give you this; get it in writing.
• No forced tier change. The right to keep buying Copilot as an add on to E5, even if E7 becomes the preferred offer.

Benchmark the final bundle rate against independent pricing ranges before signature. Our guide to Microsoft contract terms covers the drafting.

How does the E7 decision change with your starting point and timing?

The more E3 users a tenant has, the more a whole tenant E7 deal overpays, and the larger the tenant, the more each $1 per user error costs. Start early; the table below sets out when.

Starting from E3 or from E5

From E3, the E7 conversation is really an E5 upgrade with AI on top, so right size the E5 population first. From E5 with a Copilot pilot already running, you have usage data, which is the strongest evidence you can bring. Use it to price only the next tranche.

How to check your own position

Most of the evidence comes from tools you already own:

• Microsoft 365 admin center. The Microsoft 365 Copilot usage report and the active users report show who uses what, by app.
• Copilot Dashboard in Viva Insights. Adoption and usage trends for Copilot, broken down by group.
• Microsoft Graph PowerShell. Get-MgSubscribedSku lists every SKU you own with purchased and assigned units.
• Microsoft Entra admin center. Shows whether Private Access, Internet Access or governance features are in use today.

More material on renewals sits in the Microsoft knowledge hub, and our E7 cost analysis models the return case.

What to do next

1. Get the layer prices in writing. Ask for E5, Copilot, Entra Suite and Agent 365 as separate net prices, and do not negotiate a single blended number.
2. Right size the E5 base. Confirm which roles need E5 before any user is moved to E7.
3. Define the pilot group from usage data. Choose roles with a demonstrable Copilot use case rather than a share of headcount.
4. Set expansion gates and rates now. Write the usage thresholds and the per seat prices for later seats into the agreement.
5. Audit the security overlap. Compare Entra Suite and Agent 365 with what E5 and your existing tools already cover.
6. Benchmark and lock the rates. Test the final structure against independent ranges and hold every unit price for the term. Our Microsoft advisory practice can run the decomposition with you.

Frequently asked questions