Where Organisations Stand After April 2026

The extended security update period for Exchange Server 2019 ended on April 14, 2026 — the six-month ESU programme Microsoft made available to organisations that had not completed migration by the October 2025 deadline. For organisations still running Exchange 2019 on-premises today, that means operating an unpatched email infrastructure with no support path from Microsoft and an expanding attack surface that threat actors actively target.

This is not a theoretical risk. End-of-life server software is a primary vector in enterprise breaches, and Exchange specifically has a long history of critical vulnerability exploitation — ProxyLogon, ProxyShell, and OWASSRF are all examples of Exchange vulnerabilities that caused widespread damage even when patches were available. Without active security updates, an organisation's risk exposure grows with every new vulnerability discovered in the Exchange codebase.

The commercial implications are equally serious. Cyber insurance policies increasingly require supported software versions as a condition of coverage. Regulatory frameworks including NIS2 in the EU and various US sectoral requirements treat end-of-life infrastructure as a compliance gap. Organisations delaying Exchange migration beyond this point are not simply accepting technical debt — they are accumulating regulatory and insurance liability.

The Three Migration Paths

Microsoft offers three supported migration destinations for Exchange 2019 customers. Each carries different commercial profiles, operational requirements, and long-term cost structures. The right choice depends on your organisation's data sovereignty requirements, compliance constraints, infrastructure appetite, and existing Microsoft licence portfolio.

Path 1: Exchange Online (Microsoft 365)

Migrating to Exchange Online within Microsoft 365 is Microsoft's preferred and most aggressively marketed path. It eliminates on-premises Exchange infrastructure entirely and shifts email to a cloud-hosted model with Microsoft managing availability, patching, and capacity. For most organisations without specific data residency or sovereignty requirements, this is the commercially simplest outcome.

Exchange Online is included in Microsoft 365 E3, E5, and E7 subscriptions. Standalone Exchange Online Plan 1 is also available at approximately $4 per user per month for organisations that need only mailbox functionality without the full M365 productivity suite. Exchange Online Plan 2 — which adds unlimited archiving and in-place hold — runs approximately $8 per user per month as a standalone.

The migration itself is executed through cutover, minimal hybrid, or full hybrid methods depending on mailbox volume and complexity. Cutover migration — moving all mailboxes simultaneously — is typically suitable for organisations with fewer than 150 mailboxes. Larger organisations typically use full hybrid migration, which allows phased mailbox movement while maintaining coexistence between on-premises and cloud mailboxes during the transition period.

The commercial advantage Microsoft rarely highlights directly: if your organisation already holds M365 E3 or E5 licences for productivity purposes, Exchange Online is included in those licences at no incremental cost. The migration cost is operational, not licensing. Many organisations running Exchange 2019 on-premises have already been paying for Exchange Online as part of their M365 suite — meaning migration eliminates on-premises infrastructure cost without adding to the per-user licence bill.

Navigating your Exchange migration commercial strategy?

Our Microsoft licensing advisory specialists have managed 200+ EA negotiations including infrastructure transitions.
Get Independent Advice →

Path 2: Exchange Server Subscription Edition (SE)

Exchange Server Subscription Edition is Microsoft's new on-premises continuation path for organisations that cannot or will not move email to the cloud. Exchange SE is a cumulative upgrade from Exchange 2019 — not a new product architecture — and supports both in-place upgrade from Exchange 2019 and hybrid coexistence with Exchange Online.

The licensing model for Exchange Server SE is fundamentally different from previous Exchange Server perpetual licences. Exchange SE requires an ongoing subscription, not a one-time perpetual purchase. Organisations can access Exchange SE through two mechanisms: holding qualifying Microsoft 365 cloud subscription licences (such as M365 E3 or E5) that include on-premises use rights, or purchasing Exchange Server SE Server licences and Client Access Licences with active Software Assurance.

The critical commercial point: if your organisation does not already hold M365 E3 or E5 licences with Software Assurance, accessing Exchange SE requires either acquiring those licences or purchasing SA separately. For organisations that held Exchange 2019 perpetual licences without active SA, the SE transition requires a new procurement step that Microsoft did not communicate clearly when the SE programme was announced.

On-premises Exchange server and CAL pricing increased by 10 percent on July 1, 2025. Core CAL Suite and Enterprise CAL Suite pricing — which many large organisations use to licence Exchange alongside other Microsoft server products — increased by 15 and 20 percent respectively. These increases significantly change the TCO comparison between maintaining on-premises Exchange SE and migrating to Exchange Online.

Path 3: Hybrid Deployment

A hybrid Exchange deployment maintains on-premises Exchange infrastructure alongside Exchange Online, with mailboxes distributed between both environments based on organisational requirements. This is not a permanent destination — Microsoft treats hybrid as a migration state, not a long-term architecture — but it provides a phased transition path for organisations with complex compliance requirements, public folder dependencies, or significant on-premises integration needs.

Hybrid requires at least one Exchange server running on-premises (either Exchange SE or a supported legacy version during transition) to manage the hybrid configuration role. The commercial implication is that hybrid does not eliminate on-premises Exchange infrastructure cost during the transition period — it adds cloud licence cost on top of existing infrastructure cost until migration is complete.

The Commercial Case For and Against Each Path

The financial comparison between paths is not as straightforward as Microsoft's migration marketing implies. The right answer depends on three factors that vary significantly by organisation: your existing M365 licence position, your on-premises infrastructure cost, and your regulatory requirements around data residency.

When Exchange Online Wins on Cost

Exchange Online wins on cost for the majority of enterprise organisations when Exchange Online is already included in their existing M365 E3 or E5 licences. In these cases, migration eliminates Exchange server hardware, operating system licences, storage, backup infrastructure, and the IT staff time required to manage and patch on-premises email — all without any increase in the per-user licence cost they are already paying. Even factoring in migration project costs, payback is typically achieved within 12 to 18 months.

For organisations not yet on M365 (those running on standalone Exchange Server licences only), the economics require modelling. Exchange Online Plan 1 at approximately $4 per user per month costs $48 per user per year. Against that, on-premises Exchange server and CAL costs, hardware amortisation, and IT operational cost need to be quantified. For most organisations with 500 or more seats, Exchange Online is typically cheaper on a total cost basis within three years even without counting hardware refresh cycles.

When On-Premises SE May Be Justified

Exchange Server SE is justified in a narrow set of circumstances: organisations with regulatory requirements mandating on-premises data storage in specific jurisdictions, organisations with complex on-premises integrations that cannot be replicated through Exchange Online connectors, and organisations with significant existing SA investments that make SE transition straightforward without additional procurement. For these organisations, SE provides continuity without the architectural disruption of cloud migration. The trade-off is ongoing subscription cost combined with infrastructure maintenance overhead and the 10 to 20 percent price increases imposed in July 2025.

What Microsoft does not advertise: many organisations running Exchange 2019 already have Exchange Online included in their M365 licences and don't know it. The migration to Exchange Online costs zero in licensing — the cost is purely operational. Discovering this before renewing your EA could change your migration timeline significantly.

What Microsoft Doesn't Tell You About the Transition

Several commercially significant facts are absent from Microsoft's standard Exchange migration communications.

Existing M365 licences may already cover Exchange Online. Organisations that have been paying for M365 E3 or E5 licences — even for a subset of users — have Exchange Online Plan 2 included. If those licences are available, mailboxes can be migrated to Exchange Online without any new licence acquisition. Many IT and procurement teams do not know this because licences were provisioned for Teams and SharePoint rather than Exchange.

The on-premises price increases are not disclosed proactively. The 10 to 20 percent increase in Exchange server and CAL pricing effective July 2025 was announced in a Microsoft Community Hub post rather than through direct customer communication. Organisations renewing SA or acquiring new SE licences post-July 2025 are paying materially more than equivalent EA renewals from the previous cycle without having been explicitly notified.

Hybrid deployment costs are additive, not transitional. During a hybrid migration, organisations pay for both on-premises infrastructure and cloud licences. Microsoft's migration guidance focuses on the destination state, not the overlap cost during the hybrid period. For large organisations with 12 to 24 month migration timelines, this dual-cost period needs to be budgeted explicitly.

EA Q4 is the right moment to negotiate migration terms. Microsoft's fiscal year ends June 30, making April through June the period when field representatives have maximum authority to offer migration incentives, step-up discounts, and FastTrack engineering support at no charge. Organisations that approach Microsoft during Q4 with a migration commitment in scope extract significantly better commercial terms than those negotiating outside this window. Q4 deals consistently outperform Q1 deals by 15 to 20 percent on discount depth.

Negotiation Levers for the Exchange Migration

If your Exchange migration coincides with an EA renewal — which it should, if you are structuring the transition intelligently — there are specific negotiation levers that move in your favour.

When migrating to Exchange Online as part of a broader M365 commitment, use the migration commitment as leverage for better E3 or E5 pricing. Microsoft's field teams are compensated on seat count and annual commit value, not just licence tier — a 3,000-seat Exchange Online migration commitment has real value to a Microsoft account team that translates directly into negotiated unit price flexibility.

If you are considering Exchange Server SE alongside Exchange Online, build that competitive tension explicitly into your negotiation. Microsoft's preferred outcome is Exchange Online — using SE as a credible alternative forces the field team to offer better cloud pricing to win the migration commit. This leverage evaporates if you signal early that Exchange Online is your only path.

FastTrack for Exchange migration is available at no charge for organisations with 150 or more seats committing to Exchange Online. Ensure this is confirmed and documented in your EA addendum — it is a commercially valuable item worth approximately $15,000 to $50,000 in equivalent professional services that many organisations fail to claim.

Priority Actions for Organisations Still on Exchange 2019

Audit your existing M365 licence portfolio immediately. Determine whether Exchange Online is already included in licences you hold. If M365 E3 or E5 licences are in place for any user population, Exchange Online is available — the migration may be a zero-incremental-licence-cost decision.

Quantify your on-premises Exchange TCO. Include server hardware (including refresh cost), OS licences, storage, backup, and IT operational hours. This is the baseline against which Exchange Online cost should be compared — not just the per-user cloud licence cost in isolation.

Engage Microsoft in Q4 — April through June 2026. If your EA renewal falls in this window or can be structured to include a migration commitment, Q4 is when Microsoft field teams have maximum authority to offer incentives. An independent adviser can ensure your migration conversation is positioned as a commercial negotiation, not just a technical project.

Do not sign Exchange SE agreements without independent review. Exchange SE licensing is more complex than perpetual Exchange licensing was, and the SA and subscription requirements introduce procurement steps that are easy to misconfigure. The cost consequences of getting Exchange SE licensing wrong are significant and recurring.

Stay Current on Microsoft Infrastructure Licensing

Exchange SE, on-premises pricing changes, and M365 migration incentives are evolving. Subscribe to our Microsoft Knowledge Hub for licensing updates relevant to infrastructure decisions.

In one engagement, a 4,200-seat European manufacturing group came to us after their Exchange 2019 ESU window had closed. They had provisionally agreed to an Exchange Server SE deployment. Our licence review found they already held M365 E3 licences covering Exchange Online Plan 2 for the full user population — the cloud migration cost zero in additional licensing. The on-premises infrastructure renewal they were about to execute at $340,000 was unnecessary. Advisory fee: less than 2% of the avoided spend.
FF
Fredrik Filipsson
Co-Founder, Redress Compliance

Fredrik Filipsson is a Co-Founder of Redress Compliance and a specialist in Microsoft Enterprise Agreement negotiation, EA True-Up strategy, and M365 licensing optimisation. He has led 200+ Microsoft EA engagements across EMEA and North America, working exclusively on the buyer side. Redress Compliance is Gartner recognised and has completed 500+ enterprise software licensing engagements.

Connect on LinkedIn →