Blog Post

Exchange Team Blog
3 MIN READ

T-6 months: Exchange Server 2016 and Exchange Server 2019 End of Support

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Apr 14, 2025

On October 14, 2025, six months from nowExchange Server 2016 and Exchange Server 2019 will reach end of support. It’s critical to plan your upgrade now to remain supported and secure.

After October 14, 2025, Microsoft will no longer provide technical support, meaning that Exchange 2016 and Exchange 2019 users will no longer receive:

  • Bug fixes for issues that may impact the stability and usability of the server.
  • Security fixes for vulnerabilities that may make the server vulnerable to security breaches; and
  • Time zone updates.

Customer installations of Exchange 2016 and Exchange 2019 will of course continue to run after October 14, 2025. However, continuing to use these offerings after the end-of-support date invites potential security risks, so we strongly recommend taking action now.

Our recommendation is for customers to migrate to Exchange Online or prepare their organizations to upgrade to Exchange Server Subscription Edition (SE) when it becomes available in July 2025. One of the ways to make this transition easier is to install Exchange Server 2019 CU15 now. That makes it possible to in-place upgrade from Exchange 2019 to Exchange SE (when available), making the transition significantly faster and easier.

Migrate to Exchange Online or Microsoft 365

We strongly believe that you get the best value and user experience by migrating fully to Exchange Online or Microsoft 365. Migrating to the cloud is the best and simplest option to help you retire your Exchange Server deployment. When you migrate to the Microsoft cloud, you make a single hop away from an on-premises deployment and benefit from new features and technologies, including advanced generative AI technologies that are available in the cloud but not on-premises.

If you’re migrating to the cloud, you might be eligible to use our Microsoft FastTrack service. FastTrack shares best practices and provides tools and resources to make your migration as seamless as possible. Best of all, you’ll have a support engineer helping you, from planning and designing to migrating your last mailbox. For more information about FastTrack, see Microsoft FastTrack.

Prepare to upgrade to Exchange Server SE

In May 2024, we provided an update to the Exchange Server roadmap and details on how to upgrade to Exchange Server SE if you intend to continue to run Exchange Server on-premises.

If you are running Exchange 2019, we recommend that you keep your Exchange servers up to date, and you can upgrade in-place to Exchange Server SE when it becomes available later in 2025.

If you are running Exchange 2016, we recommend that you perform a legacy (a.k.a. side-by-side) upgrade to Exchange 2019 now and then perform an in-place upgrade to Exchange Server SE once it’s released. You do have the option of a legacy upgrade from Exchange 2016 to Exchange Server SE RTM, skipping Exchange 2019 completely. But since there are only a few months between the release of Exchange Server SE and the end of support for Exchange 2016, that might not be enough time, depending on the size of your deployment and other factors (in-place upgrade from Exchange 2016 to Exchange SE will not be available). This is why we recommend that you upgrade to Exchange Server 2019 now, decommission your Exchange 2016 servers, and do an in-place upgrade to Exchange Server SE when it is available.

Note: If you still have Exchange Server 2013 or earlier in your organization, you must first remove it before you can install Exchange Server 2019 CU15 or upgrade to Exchange Server SE.

Exchange Server Technology Adoption Program

If your organization intends to continue running Exchange Server and you want to test and evaluate pre-release builds of Exchange Server SE releases, you can apply to join the Exchange Server Technology Adoption Program (TAP).

Joining the Exchange Server TAP has several advantages, such as the ability to provide input and feedback on future updates, develop a close relationship with the Exchange Server engineering team, receive pre-release information about Exchange Server, and more. TAP members also get support from Microsoft at no additional charge for issues related to the TAP.

All nominations are reviewed and screened prior to acceptance. No customers are allowed access to any pre-release downloads or information until all legal paperwork is properly executed. Nomination does not mean acceptance, as not all nominees will be chosen for the TAP. If you are preliminarily accepted, we will contact you to get the required paperwork started.

Please note that even if you do not join the TAP program, you will still be able to test the code equivalent of Exchange SE in your organizations by installing Exchange 2019 CU15.

Exchange Server Engineering Team

Updated Apr 11, 2025
Version 1.0

10 Comments

  • yksmc's avatar
    yksmc
    Copper Contributor

    We are in a hybrid environment - on-prem AD and all mailboxes in EXO. Currently have E2016 for attribute management only. If both 2016 and 2019 expire in October, what is the best (or supported) path forward in our situation?

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      Use this article to switch to the server-less management paradigm (you'll have to install E2019 management tools on a workstation for example): Manage recipients in Exchange Server 2019 Hybrid environments | Microsoft Learn

      Once you confirm that PowerShell management is working as expected, run the cleanup script as per the article to get rid of E2016 server and you'll just use the E2019 management tools. When Exchange SE releases, update the management tools to Exchange SE management tools as per the above article.

      If you want to keep a running Exchange on-prem for management, you can install E2019 now, decommission E2016 and then in-place upgrade to Exchange SE when available.

       

      • yksmc's avatar
        yksmc
        Copper Contributor

        Thank you for your reply, Nino! After looking into to a bit further and actually installing 2019 Mgmt tools only, I realized we can have a full-fledged ESE without any email traffic. So we're still with 2016 right now and would like to get to ESE before October. What's the best (and supported) way to getting us there?
        Your assistance is greatly appreciated!

  • Satyajit321's avatar
    Satyajit321
    Iron Contributor

    Publishing End of Support without having a working product in GA doesn't help. There should be always a decent amount of overlaps between transitions.

    There should have been a version released around 2021-22, which would have lasted the support till 2027-28. As it didn't happen, Microsoft should revisit thier Extended Support dates for Exchange 2019. The trend of 2-3 yrs of overlap shouldn't cut down to 3 months.

    Justification, its the same code base isn't enough to mitigate the risk it poses to production workloads.

    • BrianHandscomb's avatar
      BrianHandscomb
      Iron Contributor

      The severely shortened lifecycle for 2019 was announced a couple of years ago to substantial dismay. Not helped by the fact originally the what was nicknamed "vNext" is actually substantially late compared to what was originally suggested. There will be just three months from release of SE before all prior versions are out of support, with the major version 2016 and 2019 being "cut off" from support on the same day. Not what anyone expects regarding enterprise class software but Microsoft confirmed a year ago there would be no reprieve even though the Exchange Server 2019 lifecycle doesn't line up with the normal "standard" Microsoft uses. No summer holidays for Exchange admins this year!

      • Nino_Bilic's avatar
        Nino_Bilic
        Icon for Microsoft rankMicrosoft

        I understand the sentiment, but this is incorrect.

        Exchange Server 2019 lifecycle was set at the date of release and it has been listed as "Extended support end date" of "October 2025" since the end of calendar year 2018 when Exchange 2019 was released: Exchange Server 2019 - Microsoft Lifecycle | Microsoft Learn

        Where I am going with this is - it is incorrect that shooter lifecycle (when compared to previous versions) was announced a few years ago. What is probably a more accurate statement is that "many have become aware of shorter lifecycle a few years ago" after "they made assumptions that the lifecycle is the same as previous versions".

    • MailGuy's avatar
      MailGuy
      Copper Contributor

      Exchange Online won't be an option for many customers in Europe. Sure, best option for Microsoft would it be. The demand for on premises services is still high and to be the real owner of the data is even higher. The pressure by cutting support for the existing version and not delievering the successor in a timely manner is just a means of more pressure to convince customers for booking US clouds, nothing else.

      Exchange on prem is the way to go and if there would be no reasonable price tag and lifecycle, reaching out for real alternatives is the next task.