Why Organisations Still Running On-Premises Exchange Need to Act Now: Exchange Server Subscription Edition Explained

If you are still running Exchange Server 2016 or 2019 on premises, you have probably heard Exchange Server Subscription Edition mentioned and struggled to work out how much of it matters to you. Most of what is written about it describes the licensing change, which is the least interesting part.

What matters is that support has already ended, that there are two quite different upgrade paths depending on which version you are on, and that one of them has a deadline most people have not noticed.

What Exchange Server SE actually is

Released by Microsoft in July 2025, Exchange Server Subscription Edition is the current and, on Microsoft's stated direction, final version of on-premises Exchange. The headline change is licensing: it moves from a perpetual licence you buy once to a subscription, the same model already used for SharePoint Server Subscription Edition.

Technically it is less of a leap than the name suggests. At release, Exchange SE is built directly on Exchange Server 2019 CU15, and under the hood it is largely the same product. If you have been putting off the upgrade because you expected a rebuild, that expectation is out of date.

The more meaningful change is how updates arrive. Rather than large, infrequent cumulative updates, Exchange SE receives ongoing security and feature updates, which is closer to how Windows is serviced now. It means less accumulated risk between updates and it also means the environment cannot be left untouched for two years and still be current.

Support has already ended, and this one is not soft

Microsoft ended support for both Exchange Server 2016 and Exchange Server 2019 on 14 October 2025. Microsoft was explicit that the date would not move and that Extended Security Updates were not planned, although a limited contingency programme was later announced for organisations that genuinely could not finish migrating in time.

Three consequences, in the order they tend to bite:

• •No security patches. Anything found after October 2025 stays unfixed in 2016 and 2019. Exchange has a long history as a high value target and the vulnerabilities exploited in recent years were exploited at scale, quickly. This is a live risk rather than a theoretical one.
• •No technical support. If mail flow breaks in a way you cannot resolve, Microsoft will not help. For a business whose email is the business, that is an operational exposure rather than an inconvenience.
• •Compliance exposure. Regulated sectors increasingly require supported, patched software, and running an unsupported mail platform is the kind of finding that is easy for an auditor to write up and hard for you to argue with.

Why not just move to Exchange Online?

It is a fair question and for many organisations it is the right answer. If nothing specific holds you on premises, the cloud path is usually simpler and cheaper over time.

Not everyone is in that position. The reasons to stay tend to be:

• •Data sovereignty obligations about where email is stored and processed, which are common in government-adjacent work
• •Regulatory requirements for on-premises control of archiving, data loss prevention or audit trails
• •Genuine hybrid complexity, where a large Active Directory estate, custom mail flow or third party integrations make a full migration expensive and disruptive rather than merely large
• •Applications that submit mail directly to a local server and cannot be changed, which is more common than anybody admits

If one of those applies, Exchange SE is not a consolation prize. It is the correct choice, and the migration to Exchange Online you would otherwise be forced into is the more expensive mistake.

The two upgrade paths, and which one you are on

This is the part worth getting right, because the two paths differ enormously in effort.

If you are on Exchange Server 2019 CU14 or CU15, you can upgrade in place. That is a genuine change from every previous Exchange upgrade, which required building a parallel environment, moving mailboxes and decommissioning the old servers. Configuration, mailbox data and customisations stay where they are. For most organisations this is a change window rather than a project.

If you are on Exchange Server 2016, you cannot go in place. You introduce Exchange SE alongside the existing servers, move mailboxes across, then decommission 2016. That is the traditional migration and it should be planned as one.

The deadline behind the deadline

Exchange SE at release, and CU1 scheduled for the first half of 2026, both support coexistence with Exchange 2016 and 2019. Exchange SE CU2, planned for the second half of 2026, will block coexistence with all previous versions, and that is the constraint worth planning against.

If you are on 2016 and migrating by coexistence, that is your window. It is not a support deadline, so it will not appear on the lifecycle pages people check, and it constrains the project more tightly than the October 2025 date does. Plan against it rather than against end of support.

Licensing, briefly

Exchange SE needs subscription licences, either bought new or covered by existing licences with active Software Assurance. If your Software Assurance has lapsed, or you have been running perpetual licences without it, that cost belongs in the upgrade plan and it is worth establishing before anything else.

The free Hybrid server licence continues for organisations running Exchange in hybrid with Microsoft 365, so the server that exists only to manage a hybrid relationship does not need a paid licence.

What to do now

• •Establish exactly what you are running. Version, cumulative update level, mailbox count, data volume, and every third party connector or application that talks to Exchange. The connectors are what turn a clean upgrade into a bad weekend.
• •Decide between Exchange SE and Exchange Online on the merits of your obligations rather than on inertia. Both are defensible. Doing nothing is not.
• •Check your Software Assurance position before you plan anything, because it can change the shape of the decision.
• •Pick your path. CU14 or CU15 means an in-place upgrade and a change window. Exchange 2016 means a migration project against the CU2 coexistence deadline.
• •Validate DNS, certificates, mail flow, connectors and hybrid configuration as part of the plan rather than after the cutover, because those are where in-place upgrades still go wrong.