Update 6/13/2025: Please see our new blog post for updated timelines of releases as well as additional details on how to get from current versions of Exchange Server to Exchange Server SE: Upgrading ...
Updated Jun 13, 2025
Version 14.0
Blog Post
Nino_Bilic
Microsoft
MicrosoftExchange 2016 is in Extended Support for a while now and there will not be another CU for it. Because we wanted to avoid significant changes from Exchange Server SE RTM, we are introducing the Exchange 2013 block into Exchange Server 2019 CU15. Installation of Security Updates do not check for the builds of all servers in the org, so there is no change there.
We will continue to provide a free Hybrid license as we do today, licensed by HCW.
1. This is up to you, but you are correct; Windows Server 2022 is a requirement for TLS 1.3 support in Exchange Server. In addition, because upgrading the OS under Exchange is not supported, moving to WS 2022 (or WS 2025 when available) will give you the most lifetime.
2. Windows Server 2019 and Windows Server 2022 will also be supported (we allow you to in-place upgrade from Exchange 2019)
3. Migration methods in Exchange SE stay the same as they are in Exchange 2019, except for the capability to in-place upgrade to Exchange SE from Exchange 2019 (which upgrades the databases in-place).
Nico1730 :
As of now, there are no changes to support of Exchange Web Services on-premises.
We are talking about RPS protocol / API here, not the Remote PowerShell (Exchange Management Shell) feature itself. Similarly to what happened in Exchange Online, we are introducing a new API for Exchange Remote PowerShell – moving away from RPS protocol into using Admin API (REST-based API). Exchange Remote PowerShell feature stays.