Skip to main content
Guide, 8 minute read

Exchange 2016 and 2019 End of Support: Exchange SE or Microsoft 365

Exchange Server 2016 and 2019 support ended October 14, 2025, and the paid ESU program has delivered its final updates. What ended, what Exchange SE requires, how Microsoft 365 and hybrid fit, and why Windows Server 2016 shapes the plan.

Planning guidesIT managers, messaging administrators, and finance leads at organizations still running Exchange Server 2016 or 2019 on premises, including those on Windows Server 2016By , Founder and CEO, Days Dynamics. Published November 10, 2026.

Exchange Server 2016 and 2019 support ended October 14, 2025

Microsoft ended support for Exchange Server 2016 and Exchange Server 2019 on October 14, 2025. A paid Extended Security Update (ESU) program ran in two periods through the end of October 2026. Microsoft released the final updates under it on October 13, 2026, and says no more updates will be released for Exchange 2016 or 2019. The supported paths are Exchange Server Subscription Edition (SE) on premises or a move to Microsoft 365.

Exchange Server and Windows Server lifecycle dates

The last day of each support phase as Microsoft lists it on its lifecycle pages, checked November 2026. Exchange Server 2016, Exchange Server 2019, and Windows Server 2016 follow the Fixed Lifecycle Policy. Exchange Server SE follows the Modern Lifecycle Policy and has no end date listed.

VersionReleasedMainstream support endsExtended support ends
Exchange Server 2016October 1, 2015October 13, 2020October 14, 2025
Exchange Server 2019October 22, 2018January 9, 2024October 14, 2025
Exchange Server SEJuly 1, 2025None listed (Modern Lifecycle Policy)None listed (Modern Lifecycle Policy)
Windows Server 2016October 15, 2016January 11, 2022January 12, 2027

What the Exchange ESU program covered, and where it stands now

End of support stopped Microsoft technical support, bug fixes, security fixes, and time zone updates for Exchange 2016 and 2019. The servers keep running, but Microsoft strongly recommends migrating. The ESU program was a short, paid bridge for security updates only. Microsoft said it was not an extension of the support lifecycle, and ESU customers could open support cases only for problems with an ESU update.

ESU periodCoverage windowTerms Microsoft published
Period 1October 2025 through April 14, 2026Optional and bought through a Microsoft account team. Critical and Important security updates for Exchange 2016 CU23 and Exchange 2019 CU14 or CU15, provided privately to ESU customers.
Period 2Start of May 2026 through the end of October 2026For customers with a Microsoft Enterprise Agreement. Period 1 customers had to buy again. Priced per server through the account team. Microsoft did not commit to releasing any updates. No further extensions.
  • Final updates are out. On October 13, 2026, Microsoft released the final set of updates under the Exchange 2016/2019 ESU program and said updates will be released for Exchange SE only.
  • Late purchases only catch you up. Microsoft says Period 2 can still be bought for a limited time, but it only brings servers current with the October 2026 release.
  • Plan on no further security updates. Treat any Exchange 2016 or 2019 server still in service as a migration task, not a patching task.

Your options for Exchange 2016 and 2019 servers

Microsoft documents two supported destinations: upgrade on premises to Exchange Server SE, or migrate mailboxes and other data to Microsoft 365. Which route fits depends on the Exchange version you run, the Windows Server version under it, and whether mailboxes need to stay on premises.

OptionWhat it involvesUsually fits when
Upgrade Exchange 2019 in place to Exchange SEMicrosoft supports in-place upgrade only from Exchange 2019 CU14 or CU15. It works like installing a cumulative update.The servers run Exchange 2019 on Windows Server 2019 or later and mail stays on premises
Legacy upgrade from Exchange 2016 to Exchange SEJoin a new Exchange SE server to the organization, move the mailboxes, then decommission Exchange 2016Mail stays on premises and the Exchange 2016 servers are due for new hardware or a newer Windows Server anyway
Migrate to Microsoft 365Move mailboxes, public folders, and other data with cutover, minimal hybrid, or full hybrid migration, then remove or reduce on-premises ExchangeThere is no requirement to keep mailboxes on premises and the organization already uses or plans Microsoft 365
Keep running Exchange 2016 or 2019No further security updates after the final October 2026 ESU releaseOnly as a short, isolated stopgap while one of the paths above is finished

See the Microsoft 365 services and the Microsoft 365 Business Standard vs Business Premium.

What Exchange Server SE requires

Exchange Server SE is the on-premises successor to Exchange 2016 and 2019. It changes two things buyers need to plan for: how it is licensed and how long it is supported.

  • Licensing. Microsoft's Product Terms list Exchange Server SE as available with subscription licenses or licenses with active Software Assurance only. If you do not buy cloud subscription licenses, the server licenses and CALs must carry Software Assurance.
  • CALs. The Standard CAL is the base access license. The Enterprise CAL is an additive license that adds functions such as In-Place Archive and In-Place Holds.
  • Lifecycle. Under the Modern Lifecycle Policy, Exchange SE stays in support while you stay current with Microsoft's published servicing and system requirements and stay licensed. If Microsoft ends support with no successor, it gives at least 12 months' notice.
  • Exchange 2019 path. In-place upgrade is supported only from Exchange 2019 CU14 or CU15. At release, Exchange SE RTM was identical to Exchange 2019 CU15. Earlier Exchange 2019 builds need CU15 first.
  • Exchange 2016 path. Exchange 2016 cannot be upgraded in place. Microsoft requires a legacy upgrade: join an Exchange SE RTM or CU1 server and move mailboxes. Decommission Exchange 2016 before Exchange SE CU3, because Setup in that release blocks coexistence with unsupported versions.

The Windows Server 2016 overlap

Exchange Server 2016 is supported only on Windows Server 2016, 2012 R2, and 2012. Exchange Server SE is supported only on Windows Server 2019, 2022, and 2025. Windows Server 2016 extended support ends January 12, 2027. That makes most Exchange 2016 replacements a new-server project.

  • No in-place operating system upgrade. Microsoft does not support upgrading Windows Server between major versions with Exchange Server installed, so an Exchange 2016 server cannot be lifted to a newer Windows Server and kept.
  • New servers first. Moving from Exchange 2016 to Exchange SE means building Exchange SE on Windows Server 2019 or later, then moving mailboxes to it.
  • Domain controllers count too. Microsoft's matrix still lists Windows Server 2016 domain controllers as supported for Exchange SE, but those servers reach end of support on January 12, 2027. Plan them in the same project.

See the Windows Server 2016 end of support guide, the Windows Server 2016 Decision Snapshot and the Windows Server 2016 replacement.

Hybrid and the last Exchange server

Many organizations moving to Microsoft 365 keep an on-premises Exchange server, either for hybrid coexistence during the move or for recipient management afterward. That server still needs security updates, so it belongs on Exchange SE rather than Exchange 2016 or 2019.

  • Current builds. Microsoft's hybrid prerequisites require the latest cumulative update for your Exchange version, or the release immediately before it.
  • Directory sync. A hybrid deployment uses Microsoft Entra Connect or cloud sync to synchronize Active Directory.
  • Dedicated hybrid app. Free/Busy, MailTips, and photos in hybrid need a dedicated Exchange hybrid application in Entra ID. As of October 31, 2025, EWS access through the old shared service principal is permanently blocked.
  • Source of authority. If Active Directory stays the source of authority through Microsoft Entra Connect, Microsoft says to keep at least one Exchange server. Without one, you cannot change Exchange recipients in Exchange Online.
  • Removing the last server. When every mailbox and public folder is in Exchange Online, the last server only manages recipients, and Microsoft's other listed conditions are met, Microsoft documents shutting it down and using the Management Tools from Exchange 2019 CU12 or later Setup. Microsoft says you can shut it down but must not uninstall it, and to keep it if it also handles SMTP relay.

How to plan the move

  • Inventory every Exchange server: version, cumulative update, Windows Server version, role, and anything else it does, such as SMTP relay for printers, scanners, or applications.
  • Decide where mailboxes will live: Exchange SE on premises or Exchange Online. Write down the reason, such as data location, application dependencies, or cost model.
  • Confirm your licensing. Exchange SE needs subscription licenses or Software Assurance on server licenses and CALs, so check what you own before you design.
  • For Exchange 2019 on CU14 or CU15 and Windows Server 2019 or later, plan the in-place upgrade to Exchange SE. Bring older builds to a supported CU first.
  • For Exchange 2016, build Exchange SE on Windows Server 2019 or later, move mailboxes, and retire Exchange 2016 before you install Exchange SE CU3.
  • If you move to Microsoft 365, choose cutover, minimal hybrid, or full hybrid migration, and decide early whether an Exchange server stays for recipient management.
  • Schedule Windows Server 2016 domain controllers and other servers alongside the Exchange work, so the same sites are not disrupted twice.

See the Infrastructure End-of-Support Assessment and the Exchange Online SMTP AUTH change for scanners and apps.

Frequently asked questions

When did Exchange Server 2016 and 2019 support end?

Extended support for both ended October 14, 2025. Mainstream support for Exchange 2016 ended October 13, 2020, and for Exchange 2019 on January 9, 2024. The dates apply to the Standard and Enterprise editions.

Can we still get security updates for Exchange 2016 or 2019?

Microsoft released the final ESU updates on October 13, 2026 and says no more updates will be released for Exchange 2016 or 2019. Period 2 can still be bought for a limited time, but it only brings servers current with the October 2026 release.

Can Exchange 2016 be upgraded in place to Exchange SE?

No. Microsoft supports in-place upgrade to Exchange SE only from Exchange 2019 CU14 or CU15. Exchange 2016 needs a legacy upgrade: add an Exchange SE server, move mailboxes, and decommission Exchange 2016.

Does Exchange Server SE have an end-of-support date?

Microsoft lists no end date. Exchange SE follows the Modern Lifecycle Policy, which keeps it supported while you stay current and licensed. If Microsoft ends support with no successor, it gives at least 12 months' notice.

Can Exchange Server SE run on Windows Server 2016?

No. Microsoft supports Exchange SE on Windows Server 2019, 2022, and 2025. Windows Server 2016 is supported for Exchange 2016, and its own extended support ends January 12, 2027.

Will Exchange 2016 and 2019 servers stop working?

Microsoft says installations continue to run. It no longer provides technical support, bug fixes, security fixes, or time zone updates for them, and it strongly recommends migrating as soon as possible.

Plan Exchange and Windows Server 2016 as one project

Send us the Exchange servers you run, the Windows Server versions under them, and what else depends on them, such as SMTP relay or hybrid. We will map each one to Exchange SE or Microsoft 365 and a sequence that avoids moving the same workload twice. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.