End of Mainstream Support for Exchange 2016

Exchange 2016 end of mainstream support

Exchange 2016 & Exchange 2019 are near the end of their Extended Support period (end of life). Learn more…

More about the Exchange support cycle

Exchange Server 2016, like (almost) every other on-premises Exchange Server, has a Fixed Lifecycle Policy. In short, it means that it has three support periods:

  • Mainstream Support – when a product is fully supported. During this period, Exchange Server receives regular bug fixes, security updates and new features. That is also the timeframe during which you can request to change the product’s design, request features, report bugs and contact support. Mainstream Support lasts for 5 years after a certain Exchange Server version is released.
  • Extended Support – in this stage, Exchange Server will not get Cumulative Updates but will continue to receive security updates.
  • Beyond the End of Support – that’s when a certain Exchange Server edition becomes unsupported. Although some companies continue to use Exchange Server after the Extended Support period ends, it is not recommended. You shouldn’t expect bug fixes or security updates and if you encounter any problems – you can rely on your own expertise and some technical forums.

Exchange 2016 enters the Extended Support period on October 13, 2020. Five years after this date, it will reach its end of life. What’s interesting, the next Exchange version, Exchange 2019, will reach its end of support at the exactly the same day (October 14, 2025). It makes many companies wonder: what’s the point of migrating to Exchange Server 2019? Especially since when it comes to rolling out new features, the focus is on providing them for Exchange Online, not the on-premises editions. See what’s new in Exchange 2019 for more details.

What next?

Your next steps depend on your long-term plans. The main question is: are you planning to migrate to Exchange Online or stay on-prem for the foreseeable future?

If you are going to migrate to Microsoft 365

If Microsoft 365 and Exchange Online is where you see yourself (your company mailboxes, that is) in the nearest future, you can perform a migration to Microsoft 365. You have a few migration options:

  1. Hybrid migration – in this case, the on-premises Exchange is used for recipient management. Since Extended Support period includes security fixes, for the time being, Exchange 2016 can be used in a hybrid environment for recipient management purposes.
  2. Cutover migration – in which you move mailboxes straight to Exchange Online. It lets you minimize your on-prem infrastructure.

For more information on how to migrate to Microsoft 365 and make this process easier, refer to this article.

If you are going to stay on-premises

If you intend to stay on-premises (for example, for security or compliance reasons) you need to keep in mind that the Extended Support period for Exchange 2016 and Exchange 2019 ends on October 14, 2025. Keeping an unsupported Exchange is not a good idea from the perspective of risk management. At Microsoft Ignite 2020, the Exchange team announced that Exchange 2019 will not be the last on-premises Exchange version. Read on to learn more about Exchange Server vNext and what we know about migration to this yet to be published version.

The last on-premises Exchange version

Microsoft Exchange Server vNext is the codename for what is announced to be the last Exchange Server ever: Exchange Server Subscription Edition (SE). It’s clear that this Exchange is going to be unlike any other.

Learn more about Exchange Server SE

In short:

  • Exchange Server vNext will be subscription-based. That’s a first for on-premises Exchange versions. The upside is that, at the moment, there are no plans to stop supporting it. Updates & support will be provided for all active subscribers. The downside – the ongoing cost, which was one of the reasons why some companies refrained from migrating to Microsoft 365.
  • The planned release date for Exchange vNext was initially the second half of 2021. It’s been moved to near the end of 2025.
  • At first, there was an announcement for two unique features concerning migration. First – coexistence with Exchange 2013 was to be supported. Which means that native double-hop migration would be required only for Exchange 2010 and older versions. Second – for two years after the release, admins will be able to perform an in-place upgrade. In other words, migration from Exchange 2019 should be as easy as applying a CU. In 2025 there was a change of plans – no coexistence is supported with previous server versions and to perform an in-place update to Exchange Server SE, you need to meet some requirements.
Tools for Exchange Server

Recommended articles

How to migrate from Exchange Server 2016/2019 to Microsoft 365

How to migrate from Exchange Server 2016/2019 to Microsoft 365

Migrating Exchange data to the cloud is not rocket science – explore your options and launch the migration stress-free. As you may already know, Exchange Server 2016 and 2019 have reached end of life and are no longer officially supported by Microsoft. If your organization still uses either of these platforms to manage email, contacts, calendars, and tasks, keep in mind that: Your environment may become vulnerable to newly discovered security threats – Microsoft will no longer provide security updates for Exchange 2016 and 2019 (unless you’ve enrolled in the Extended Security Update program, which ends in October 2026). Your emails may get blocked – Microsoft has started to throttle and block emails sent from unsupported Exchange Server versions to Exchange Online (as I covered in this article). That said, migrating to a supported platform is now the only viable long-term option for keeping your organization’s email environment secure, supported, and fully operational. If your organization wants or needs to keep things on‑premises (and continue using Microsoft’s solutions for that), upgrading to Exchange Server Subscription Edition (SE) is the only path forward. But given Microsoft’s clear preference for its cloud services – evident in the faster rollout of new features and the many security capabilities available exclusively in Microsoft 365 (Office 365) – now is a great time to leave your on‑prem environment behind and migrate to Exchange Online as part of Microsoft 365. While switching over to a new platform might seem like a rough ride, I’ll show you some easy ways to follow when migrating mailboxes from Exchange Server 2016/2019 to Microsoft 365. How to prepare for email migration to Microsoft 365 Before you start the migration process, you need to make sure your environment is ready for the move. For this purpose, you can use this guide in the Microsoft 365 admin center – it will help you connect your organization to Microsoft 365 and integrate your existing user accounts with Microsoft Entra ID. Microsoft also recommends completing the steps below: Set up an SPF record to determine valid email sources for your organization’s Microsoft 365 domain. Set up the Exchange Online Protection service as a means of protection against spam and malware. If you’re behind on updates, make sure to install the latest Cumulative Update (CU). And here is my quick, less obvious Microsoft 365 migration checklist: Verify if your software will work in Microsoft 365 (especially when it comes to server software). Microsoft 365 migration might be the time you learn that there is crucial legacy software that half the company uses and which is hard to replace. Encourage the whole company to clean up projects. It’s much easier to do this before the migration and start fresh. Gather as much information about your on‑premises environment as possible. For example, you might need to recreate access roles and permissions from scratch in the cloud or set up mail flow rules. Without prior research, it will be much more difficult. Verify if you need to migrate service accounts. There can be a lot of them on‑premises and in most cases, you won’t need them after the move. Review mailbox size limits in Exchange Online before migration to see which licenses you’ll need and whic
New-ComplianceSearch: how to use the newer version of Search-Mailbox

New-ComplianceSearch: how to use the newer version of Search-Mailbox

Microsoft retired the Search-Mailbox cmdlet – now what? Discover how to use New-ComplianceSearch, its key advantages and how to make the switch seamlessly.
How to start remote PowerShell session to Exchange or Microsoft 365

How to start remote PowerShell session to Exchange or Microsoft 365

One of many features of the PowerShell command line tool is its ability to connect with and manage the Exchange Server remotely. The procedure described below applies to the classic on-prem Exchange server and to the Microsoft 365/Exchange Online version.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.