Microsoft 365 July 2026 Price Increase: Complete Guide

The second wave of the 2026 cost reset

The November 2025 EA volume tier collapse was the first wave of Microsoft’s 2025–2026 commercial restructure. The July 2026 SKU price increase is the second — and for most enterprises it is the larger of the two in dollar terms. Where the tier collapse removed a structural discount (6–12% increase on affected line items, applied to one channel), the July 2026 increase raises the underlying list price itself (5–33% depending on SKU, applied across all channels). The two changes compound: every enterprise renewing after July sees both effects on the same line items.

Microsoft announced the July increase in late 2025, framing it as the company’s first comprehensive M365 pricing adjustment in several years and crediting the increase to substantial new value being added to the suites — specifically the Defender bundling into E3, the Security Copilot allocation into E5, and the broader Intune Suite consolidation. The framing is accurate; new value is genuinely being added. What is also accurate is that the price increase exceeds the marginal cost of the bundled additions, which means the net effect is a real cost increase for the average customer, not a value-neutral re-bundling.

For procurement teams, the July 2026 change has one essential property that distinguishes it from the tier collapse: it is partially avoidable. The lock-in window before the increase takes effect is real and material. Renewals that sign before 1 July 2026 can hold pre-increase pricing for the term of the new agreement — ordinarily three years. That single tactical move is the most valuable action a procurement team can take in 2026, and the window for it is closing rapidly.

This guide covers the full picture of the July 2026 change. The SKU-by-SKU breakdown for procurement modelling. The bundling changes that justify the increase from Microsoft’s perspective and that may or may not be valuable to your organisation. The interaction with the November 2025 tier collapse and the broader compounding effect on EA cost. The mechanics of the lock-in window, including the contract clauses that make the lock real versus the clauses that allow Microsoft to override it. And the decision framework for whether and how to accelerate a renewal that would otherwise land after 1 July.

SKU-by-SKU breakdown of the increase

The 5–33% range hides significant variation between specific SKUs. Procurement modelling needs the SKU-level numbers, not the aggregate range. The table below summarises the Enterprise stack — the SKUs that dominate spend for most enterprise EA customers. Business, Frontline, Government, and Education equivalents follow similar percentage logic, with some specific SKUs (notably the Government tier and certain Frontline configurations) seeing the higher end of the range.

Several observations matter for modelling. First, the Enterprise SKUs (E3, E5) see relatively modest percentage increases but apply to the largest seat counts and therefore drive the largest absolute dollar impact for most organisations. Second, the Frontline SKUs see the steepest percentage increases — particularly F1, which rises by roughly a third — affecting retail, hospitality, manufacturing, and other Frontline-heavy industries disproportionately. Third, Business Premium increases substantially in percentage terms; mid-market organisations using Business Premium rather than Enterprise SKUs see roughly 9% on their primary line item.

The pricing changes apply identically across channels — EA, MCA-Enterprise, and CSP all see the same list-price changes. Negotiated discount works on top of the new list prices, so a customer with strong negotiated discount mitigates a portion of the increase, but the underlying base has moved.

Historical context: how this increase compares

The July 2026 increase is the largest M365 pricing adjustment Microsoft has made since the introduction of M365 in 2017. Prior price changes have been narrower in scope. The 2022 increase — the most recent comparable event — raised some Office 365 SKUs by 8–25% but applied to a smaller portion of the M365 portfolio. The 2026 change applies across virtually the entire enterprise SKU set simultaneously, which is structurally different.

The breadth matters for negotiation strategy. When a pricing change is narrow, customers can often substitute an unaffected SKU for an affected one. When the change is broad, substitution becomes harder and procurement teams are forced to engage directly with the increase rather than route around it. Microsoft’s 2026 design appears intentional in this regard: the breadth eliminates most substitution paths and ensures the increase reaches the largest possible share of the installed base.

Channel impact: EA, MCA-Enterprise, and CSP

The change applies identically across the three major commercial channels, but its interaction with each is different.

Enterprise Agreement. EA customers see the price increase on their renewal date if that date is after 1 July 2026. The price increase compounds with the November 2025 tier collapse for affected line items. EA negotiated discount continues to work on top of the new list prices — meaning the percentage of structural recovery available is similar to pre-increase, but applied to a higher base.

MCA-Enterprise. MCA-E customers see the price increase on their billing month transitions after 1 July 2026. Because MCA-E does not have the November 2025 tier-collapse exposure (MCA-E was already flat-priced), the July 2026 increase is the only structural change affecting these customers in the 2025–2026 wave. The total impact on a typical MCA-E customer is therefore smaller in percentage terms than on a typical mid-market EA customer who absorbed both waves.

CSP. CSP customers receive the price change immediately on the effective date for new orders, with existing subscriptions repricing at their next term renewal. CSP pricing has always been flat (equivalent to Level A), so like MCA-E, CSP customers face only the July 2026 wave, not the cumulative tier-collapse-plus-July wave that EA customers face. Negotiated discount available through CSP is typically narrower than through EA, but the gap has narrowed substantially post-tier-collapse.

The bundling changes that come with the price increase

Microsoft has packaged the July 2026 price increase with bundling additions to each major SKU. Whether the bundled additions justify the price increase depends entirely on whether your organisation actually needed and used the previously-separate products.

Defender for Office 365 P1 folded into M365 E3

Customers on E3 today purchase Defender for Office 365 P1 separately at approximately $2 per user per month. From July 2026, that capability is included in E3 base. For organisations currently buying both, this represents a real value gain — roughly $24 per user annually no longer needed as a separate add-on. For organisations on E3 who did not buy Defender for Office 365 P1, the addition is functionally free but provides capability they may not need.

The procurement implication: organisations currently buying both E3 and Defender for Office 365 P1 can drop the separate Defender line item from their renewal. This saves real money. The savings partially offset the E3 price increase, though typically not fully — the math works out to net-positive for Microsoft and roughly neutral or modestly negative for the customer, depending on Defender attach rate.

Security Copilot SCU allocation built into E5

E5 tenants receive Security Copilot capacity built into the base subscription from July 2026. The allocation is 400 SCU per 1,000 paid users per month, capped at 10,000 SCU per tenant regardless of size. SCU (Security Compute Units) is Microsoft’s consumption unit for Security Copilot, used across security analyst, hunting, and investigation workflows.

The economic value of the bundled SCU depends entirely on whether the organisation is actually using Security Copilot. Customers with mature SOC operations using Security Copilot at scale will exceed the bundled allocation and continue to purchase additional SCU. Customers not using Security Copilot receive notional capacity they may not consume. For most E5 customers, the bundled allocation will go unused in year one, which makes the bundling value-neutral in practice even though Microsoft attributes meaningful value to it in the pricing rationale.

Additional Intune Suite features into E3 and E5

Several capabilities previously sold as Intune Plan 2 add-ons or in the Intune Suite SKU are folded into E3 and E5 base. The specifics vary between E3 and E5: E3 gets Intune Advanced Analytics and Remote Help; E5 gets those plus Endpoint Privilege Management (EPM), Enterprise Application Management (EAM), and Cloud PKI. For organisations currently purchasing Intune Suite or these add-ons separately, the bundling represents direct savings — typically $5–$8 per user per month per add-on dropped.

Industry impact: where the bundling matters most and least

The value of the bundled additions varies dramatically by industry profile. Three industry archetypes illustrate the variance.

Mature security buyers (financial services, regulated healthcare, defence). These organisations typically already deploy the now-bundled products. Defender for Office 365 P1 is universal in this cohort. Intune Suite features are deployed at scale. Security Copilot is being piloted or deployed in mature SOCs. For these customers, the bundling represents real offsetting value of $40–$80 per user annually, which substantially offsets the headline price increase. Net cost impact for this cohort is often 0–3% rather than the headline 5–10%.

Productivity-focused buyers (professional services, mid-market manufacturing, retail HQ). These organisations typically deploy Microsoft 365 primarily for productivity rather than as a security stack. Defender add-ons are partial or absent. Intune Suite features are inconsistent across the estate. Security Copilot is not deployed. For these customers, the bundling represents notional value the organisation may or may not eventually use. Net cost impact for this cohort is close to the headline 5–10% because the bundling does not offset the increase.

Frontline-heavy buyers (retail floor, hospitality, manufacturing operations, healthcare nursing). These organisations are concentrated in F1/F3 SKUs that see the steepest percentage increases (12–33%) with the smallest bundling offsets. The Defender and Intune additions land primarily in E3 and E5, not in Frontline SKUs. Net cost impact for this cohort is often higher than the headline range because Frontline-heavy organisations carry the steeper percentages on the largest seat counts.

How July 2026 compounds with the November 2025 tier collapse

For procurement teams modelling 2026 EA economics, the two changes need to be considered together. The November 2025 tier collapse raised the effective price paid (by removing the volume discount). The July 2026 increase raises the underlying list price. Both apply to the same line items. The combined effect is multiplicative, not additive.

For a 2,800-seat customer who previously sat in Level B (approximately 7% effective tier discount):

• Pre-November 2025: E3 paid price was approximately $36 list × 0.93 tier discount = $33.48 per user per month.
• Post-November 2025 (tier collapse): E3 paid price is $36 list with no automatic tier discount = $36.00 per user per month. Structural increase: 7.5%.
• Post-July 2026 (price increase): E3 paid price is approximately $38.50 list with no automatic tier discount = $38.50 per user per month. Cumulative increase from pre-November 2025 baseline: 15.0%.

The 15% cumulative increase is before any negotiation response and before the additional Unified Support amplification (typically another 8–12% of incremental EA spend flowing into support costs automatically). The unmitigated cost wave on a $5M EA for a Level B mid-market customer reaches approximately $1M annually over the 18-month window through mid-2026.

Three additional scenarios for context

The Level B mid-market example illustrates the typical mid-market path. Three more scenarios show how the combined wave varies by cohort.

Scenario A: 1,200-seat professional services firm, previously Level A. No tier collapse impact (was already at Level A). July 2026 increase applies on a typical E3-dominated mix at approximately 8% on the affected line items. Total EA impact: roughly 5% on a $1.8M EA, or $90K annual increase. Recovery via lock-in window acceleration can reduce this to near zero.

Scenario B: 8,000-seat global manufacturer, previously Level C. Tier collapse impact of approximately 11% on online services. July 2026 increase on top at 5–8% depending on E5 vs E3 share. Heavy Frontline F3 deployment in factories adds 12–30% on those specific seats. Combined wave on a $14M EA reaches approximately 14%, or $2M annually before recovery measures. Best-case recovery through full lever set: $700K–$1M, leaving net 6–8%.

Scenario C: 25,000-seat financial services firm, previously Level D. Tier collapse impact of approximately 14% on online services. July 2026 increase of 5% on the E5-dominated stack with the Security Copilot SCU bundling now contributing meaningful offsetting value. Combined wave on a $35M EA: approximately 14% gross, reduced by 2–3% from the Security Copilot offset that this customer genuinely uses. Net pre-recovery: $4M annually. Recovery through credible competitive displacement work and Azure co-commitment routinely delivers $1.5M–$2.5M back. Final net: 4–7%.

The lock-in window: how it works and how to use it

The single most valuable action available to procurement teams in the first half of 2026 is the lock-in window. Renewals that sign before 1 July 2026 can preserve pre-increase pricing for the term of the new agreement — typically three years. For an organisation that would otherwise renew in October 2026 at post-increase pricing, accelerating the renewal by four months and signing in late June 2026 can save 5–9% of the M365 portion of the EA over the next three years.

The lock-in mechanism is straightforward but procedural. Microsoft has confirmed that customers signing before the effective date retain pre-increase pricing for their term, with the new pricing applying at the next renewal after that term ends. The mechanism is not a quirk or a loophole; it is an explicit transition policy designed to give the existing customer base predictability. Microsoft account teams will not always offer the lock-in proactively, however — procurement teams need to ask for it specifically and ensure the contract documents the locked pricing.

Three contract clauses that make the lock real

An EA signed in June 2026 with the wrong clauses can still see the July 2026 list-price increase applied at the first anniversary order. Three clauses determine whether the lock-in holds:

• Explicit unit price lock. The negotiated per-unit price for each affected SKU must be documented in the agreement, with a clear statement that the price applies for the term. “Subject to list-price adjustment at anniversary” clauses defeat the lock-in entirely.
• Anniversary order price-lock language. The price-lock must explicitly apply to anniversary orders, not just to the initial enrollment. Without this, anniversary order pricing can revert to the prevailing list price.
• True-up pricing protection. True-up orders for incremental seats during the term must price at the locked rate, not at the prevailing list rate. Without this, growth during the term is priced at post-July-2026 levels even if the base is locked at pre-July-2026 levels.

Two clauses that quietly defeat the lock

Two additional clauses appear in many Microsoft-drafted EAs and have the effect of nullifying the price lock in practice even when the explicit lock language is present. Procurement teams should specifically watch for and challenge both.

The currency adjustment clause. EAs signed in non-USD currencies frequently include a currency adjustment provision that allows Microsoft to adjust unit prices to reflect exchange rate movements. In practice, the clause is exercised one-directionally — Microsoft adjusts upward when the customer’s currency weakens but does not reduce when it strengthens. For organisations outside the USD zone, the currency clause can absorb 5–10% of locked-in discount over the term of the EA without any explicit price increase being applied. The clean version of the lock-in eliminates the clause entirely or makes it bidirectional.

The product-change clause. Microsoft retains the right under standard EA terms to modify product offerings during the term — including renaming SKUs, splitting bundled products, or replacing one SKU with a successor product. Each modification creates an opportunity to apply the prevailing pricing rather than the locked pricing for the successor product. The Power BI Premium to Fabric F-SKU migration is a current example of how this mechanism plays out in practice. The protective language requires that any successor or replacement SKU be priced at the locked rate for the original SKU, not at the prevailing rate for the successor.

Should you accelerate a renewal to land before 1 July?

Acceleration is not free. Moving a renewal forward has operational costs — truncated preparation, compressed negotiation, potentially weaker positions on non-price terms. The decision to accelerate should be modelled, not assumed. The structured math is:

• Acceleration cost: typically 2–4 months of pre-renewal preparation lost. For most organisations this translates to 1–3% of weaker negotiated discount because preparation depth correlates directly with negotiated outcome.
• Acceleration benefit: 5–9% of M365 portion locked at pre-increase pricing for the new term. For a typical EA with 60% online services share, this works out to 3–5% of total EA value.

The math favours acceleration in most cases by a margin of 2–3 percentage points net positive, but the margin is narrower than the headline benefit suggests. Procurement teams should not accelerate as a reflex; they should accelerate after running the specific calculation for their organisation. The calculation produces clear answers in most cases — either “accelerate” or “hold steady” with confidence above 70%.

What to do if your renewal is after July 1

For renewals that cannot be accelerated — either because the anniversary date is too late or because acceleration cost exceeds benefit — the strategy shifts. Post-July renewals are negotiating against the new list prices, not the old ones. The recovery levers from the tier collapse recovery playbook still apply, but they operate on a higher base. The realistic best case for a post-July 2026 renewal is to negotiate sufficient line-item discount to land roughly where a pre-July renewal would land at the equivalent organisational profile.

Three additional tactics apply specifically to post-July renewals. First, take credit for the bundled additions explicitly — the Defender, Security Copilot SCU, and Intune additions should reduce other line items on the bill, not be absorbed silently. Second, push aggressively on multi-year term commitment, because the next renewal in 2029 will likely face additional pricing changes and term-lock value increases when subsequent uncertainty increases. Third, consider whether E7 Frontier Suite ($99 bundling E5 + Copilot + Agent 365 + Entra Suite) is competitive against E5 plus separately purchased components; the new E7 economics may shift the right SKU decision for some organisations.

The bundling-credit conversation

Microsoft account teams routinely present the bundling additions and the price increase as a package — framing the conversation as “you are getting Defender for Office 365 P1, Security Copilot SCU, and additional Intune Suite features included, which more than offsets the price increase.” The framing is sometimes accurate and sometimes not, depending on whether the customer was actually purchasing the now-bundled products separately. Procurement teams should explicitly separate the components in the conversation.

The clean version of the conversation: “We currently spend $X per user per year on the products that are now being bundled. After bundling, that $X disappears from our bill. Your price increase is $Y per user per year. The net effect for our organisation is $(Y minus X) per user per year — please confirm we agree on the math.” This forces the bundling-credit conversation into explicit numbers and prevents Microsoft from absorbing the bundled-product savings silently while presenting the headline price increase as offset by them.

The SKU-mix optimisation conversation

The July 2026 changes also create the opportunity to rebalance SKU mix at renewal. Three specific cases regularly produce material savings:

• E5 to E3 downgrade candidates. The bundling additions narrow the value gap between E5 and E3 by approximately $4–$7 per user per month for organisations that did not use Security Copilot or the now-bundled Intune features. Some users currently on E5 may now make sense on E3, particularly in cohorts where E5 was deployed reflexively rather than for specific Security or Compliance feature usage.
• Business Premium to E3 review. The Business Premium price increase (~9%) is steeper than the E3 increase, and the Business-versus-Enterprise SKU cross-over point has moved. Organisations between 300 and 800 seats on Business Premium should re-model the cross-over to E3 as part of the renewal.
• E3 to Frontline review for shift workers. Organisations with shift workers, kiosk users, or shop-floor staff currently on E3 should review whether F3 (or F1 for the most basic profiles) is appropriate. Even with the Frontline percentage increase, F3 at ~$10 per user is substantially cheaper than E3 at ~$38.50 for users whose actual feature needs map to Frontline.

Action plan for the next four weeks

For procurement and IT leadership responsible for an EA renewal in 2026 or 2027, three actions in the next four weeks compound into materially better outcomes:

1. Confirm your renewal date and run the acceleration math. If your natural renewal date is between July 2026 and December 2026, you may be able to accelerate the signing by 1–6 months and lock in pre-increase pricing. The calculation takes a day; the payoff is 2–5% of total EA value.
2. Model the SKU mix impact for your specific tenant. The 5–33% headline range hides significant SKU-specific variation. Pull your current SKU mix and apply the SKU-level percentage to each line item. This produces your specific cost wave estimate — not the generic range.
3. Quantify the bundled additions for your environment. Identify which of the now-bundled products (Defender for Office 365 P1, Intune Plan 2 features, Security Copilot capacity) you currently purchase separately. Document the savings from dropping those separate line items. This is the legitimate offset against the price increase — and procurement teams who calculate it precisely negotiate better than teams who guess.

The strategic bottom line

The July 2026 M365 price increase is the second of the three commercial waves restructuring Microsoft enterprise economics in 2025–2026 — with the November 2025 tier collapse before it and the ongoing Unified Support escalation alongside it. Each wave can be modelled, negotiated, and partially neutralised individually. Together they require systematic preparation that most procurement teams running renewals on internal capacity alone will struggle to deliver in the available timeframe.

The lock-in window for pre-July pricing is the single highest-value action available. The bundling-additions accounting is the second-highest. The recovery levers from the tier collapse playbook remain the third. Worked together by a prepared procurement team, the combined impact of the 2026 cost wave can be reduced from a structural 15–25% to a manageable 4–8%. The work that closes that gap begins now. Schedule a scoping call when you are ready to start.