Your Exchange 2019 servers are still delivering mail, and the vulnerability scanner flags them every week. If you bought extended security updates, they bought some time, but Microsoft shipped the last of those in October 2026. Meanwhile the CFO wants to know why email needs a project at all, and nobody is quite sure which copiers, scanners, and line-of-business apps quietly send mail through the server.
You have two supported paths. You can upgrade to Exchange Server Subscription Edition (SE) and keep mail on premises, or you can move mailboxes to Exchange Online. Either can be the right answer. The choice shapes your costs, your staffing, and your exit options for years, so it deserves a decision you can explain later, even if you have to make it quickly.
At a glance
- Exchange 2016 and 2019 reached end of support on October 14, 2025, and the paid security update program for them has ended. Running them now means running mail servers that get no security fixes.
- Exchange SE keeps mail on premises under a subscription licensing model, with an in-place upgrade from Exchange 2019 CU14 or CU15. Exchange Online hands the infrastructure to Microsoft and changes what your team manages.
- Weigh cost, compliance and data location, staff skills, mail-relay dependencies, migration effort, and how you would leave either choice later.
Where things stand for Exchange 2016 and 2019
Support for Exchange Server 2016 and 2019 ended on October 14, 2025. Microsoft no longer provides technical support, bug fixes, security fixes, or time zone updates for those versions. The servers keep running, which is part of the problem: nothing forces the issue until a vulnerability does.
Microsoft offered a paid Extended Security Update program for organizations that needed more time. It was limited to Enterprise Agreement customers, purchased through the Microsoft account team, and covered only Critical and Important security updates for specific cumulative updates. It did not extend the product lifecycle. In October 2026, Microsoft released the final updates under that program and said future security updates would ship for Exchange SE only.
If your servers are still on 2016 or 2019, every week adds exposure on a system that faces the internet and holds some of your most sensitive correspondence. That urgency is real. It still shouldn't push you into a choice you haven't thought through.
What Exchange Server Subscription Edition changes
Microsoft released Exchange Server SE to general availability on July 1, 2025. Technically, it continues Exchange 2019. If you run Exchange 2019 CU14 or CU15, you can upgrade those servers in place, much like applying a cumulative update. Organizations still on Exchange 2016 have a longer road: new SE servers join the existing organization and mailboxes move to them. Microsoft ties how long that coexistence is supported to future SE updates, so check the current guidance before you plan.
The bigger change is commercial. SE follows Microsoft's Modern Lifecycle Policy, so it has no fixed end-of-support date as long as you keep it current. Licensing changes too. Microsoft's product terms require SE server licenses and client access licenses to be subscription licenses or licenses with active Software Assurance. A perpetual license without active Software Assurance won't satisfy that requirement. Confirm your exact position with your licensing reseller, since the answer depends on what you own today.
Staying on premises also means you keep the work: patching on Microsoft's cadence, certificates, hardware or virtualization, backups, spam filtering, high availability, and the skills to troubleshoot all of it.
What moving to Exchange Online changes
Exchange Online moves the servers, patching, and much of the availability engineering to Microsoft. Your team's work shifts toward identity, security policy, compliance settings, licensing, and user support. Cost becomes a per-user subscription, usually part of a Microsoft 365 plan, and it rises and falls with headcount and with Microsoft's pricing decisions. If recent price changes are already on your mind, see how to plan for Microsoft price increases.
Two dependencies grow in importance. Your identity provider becomes the front door to email, so sign-in security and conditional access matter more. Your internet connection also becomes part of the mail path for every user in the office.
Many teams assume they can switch off on-premises Exchange the day the last mailbox moves. If you sync accounts from an on-premises Active Directory, that hasn't always been possible, and organizations historically kept one Exchange server running just to manage recipient attributes. Microsoft now documents a path to remove the last Exchange server once every mailbox is in the cloud and the source of authority for Exchange attributes has moved to Exchange Online. It works, and it needs planning and testing.
Exchange Server Subscription Edition vs. Exchange Online, side by side
- Cost model
- Exchange Server SE: Subscription or SA-covered server licenses and CALs, plus hardware, storage, backup, and staff time
- Exchange Online: Per-user subscription, often within a Microsoft 365 plan
- Who patches and runs it
- Exchange Server SE: Your team, on Microsoft's update cadence
- Exchange Online: Microsoft runs the service; your team manages configuration and policy
- Data location
- Exchange Server SE: Your data center or hosting provider
- Exchange Online: Microsoft data centers, based on your tenant's geography
- Skills you need in-house
- Exchange Server SE: Exchange administration, Windows Server, certificates, high availability
- Exchange Online: Identity, security and compliance configuration, Microsoft 365 administration
- Apps and devices that relay mail
- Exchange Server SE: Existing connectors keep working
- Exchange Online: Need a new relay path before the last server is removed
- Migration effort
- Exchange Server SE: In-place upgrade from 2019 CU14 or CU15; a larger project from 2016
- Exchange Online: Mailbox migration, cutover or hybrid, plus decommissioning
- Exit path later
- Exchange Server SE: A hybrid migration to the cloud stays available
- Exchange Online: Mail has to be exported or migrated to another platform
Six factors that should drive the decision
1. Total cost over several years
Compare like with like. For SE, include licensing under the new model, server hardware or virtualization, storage growth, backup, filtering, monitoring, and the hours your team spends on patching and troubleshooting. For Exchange Online, include the subscription for every mailbox, any add-on licensing for compliance features, third-party backup, and migration labor. A three- to five-year view with a base case and one price-increase scenario is usually enough to show the real difference.
2. Compliance and data location
Some organizations have contracts, regulators, or policies that specify where data may be stored or who may administer it. Others simply assume they do. Find the actual requirement in writing. Exchange Online offers extensive retention, eDiscovery, and audit features, some of which depend on higher licensing tiers. On premises, you control location directly and carry every control yourself.
3. Staff skills and depth
An Exchange environment that only one person understands is a continuity risk whichever way you go. If that person leaves, an on-premises SE deployment gets harder to run safely. Exchange Online reduces server work, and it still needs someone who understands mail flow, identity, and security configuration.
4. Applications and devices that relay mail
This one is easy to underestimate. Copiers, scanners, alerting systems, ERP, and line-of-business applications often send mail through on-premises Exchange connectors. Inventory every one by reviewing connector configuration and message tracking logs, and give each an owner. Microsoft's decommissioning guidance warns that uninstalling the last Exchange server removes its receive connectors, which ends relay through that server for good. Set up a replacement path first, such as Exchange Online SMTP relay, and test each device. Some older devices may not support the connection or authentication methods a cloud relay expects.
5. Migration effort and timing
An in-place upgrade from Exchange 2019 to SE is the smallest technical step available. A move to Exchange Online is a larger project. Cutover and minimal hybrid methods suit smaller organizations, while full hybrid suits larger or more complex ones. Microsoft's own end-of-support guidance calls migrating to Microsoft 365 the best and simplest option, which is worth reading alongside your cost and compliance analysis.
6. The exit path from either choice
Every choice here should come with an answer to "what if we need to change this later?" If you upgrade to SE, a future move to Exchange Online stays open through a hybrid migration, and keeping the environment current keeps that path supported. If you move to Exchange Online, know how you would export mail at scale, keep an independent backup, and understand which other services, such as Teams, SharePoint, and sign-in for other apps, become tied to the same tenant. Either path is manageable when the way out is documented.
A practical sequence for the decision
- Confirm what you run: Exchange versions, cumulative updates, server count, and whether you already have a hybrid configuration.
- Reduce exposure on unsupported servers now by limiting external access to what's required, reviewing admin accounts, and watching for unusual activity.
- Inventory every app and device that relays mail, with an owner for each.
- Get your licensing position, including Software Assurance status, from your reseller.
- Build the multi-year cost comparison and write down the compliance requirement, if one exists.
- Make the decision, record why, and name the conditions that would cause you to revisit it.
Decide on purpose, even under pressure
Both paths are defensible. The risky part is making the choice in a hurry with no record of why it was made or how you would change it later.
At CTP, we help organizations weigh on-premises and cloud options with the same discipline: research first, a documented recommendation, and a back-out plan. If you are wondering when keeping servers on site still makes sense, read when an on-premises server is still the right call. When you're ready to plan the upgrade or the move, explore Microsoft 365 migration or schedule a conversation.
Sources and further reading
- Microsoft Learn, Exchange Server 2019 and 2016 end of support
- Microsoft Support, General availability of Exchange Server Subscription Edition
- Microsoft Exchange Team Blog, Period 2 Exchange 2016/2019 Extended Security Update program
- Microsoft Learn, Decommission the last Exchange server in a hybrid deployment
- Microsoft Licensing, Exchange Server product terms

