Blog Post

Exchange Team Blog
3 MIN READ

Exchange Server 2016 and the End of Mainstream Support

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Aug 10, 2020

UPDATE 2/12/21

The Exchange Sustained Engineering Team continued servicing all customer issues for Exchange 2016 that were opened with Microsoft by the end of Mainstream Support, which was Oct 13, 2020. Some of these cases were being worked on by customers and Microsoft into the new year, with fixes being approved though the end of January. As such, not all fixes will be in the soon-to-be-shipped March update (CU20), as code stabilization and quality targets do not allow us to take changes that late in the shipping cycle. Therefore, we have decided to extend out one more CU and we will be shipping CU21 in June 2021. New cases are not being considered for CU21; this is only to complete our commitment to fix what was approved from the cases that were logged prior to the end of Mainstream Support. Microsoft encourages Exchange Server 2016 customers to adopt CU21 as soon as possible after it’s released in June, 2021 to ensure uninterrupted delivery of any future security related fixes. After June 15, 2021, only CU21 or its successors will receive updates. During the Extended Support phase, only the latest CU is eligible to receive updates once the standard 3 month transition period of the prior CU has lapsed.

----------------------------------------------------------------------------------------------

As hopefully many of you already know Exchange Server 2016 enters the Extended Support phase of its product lifecycle on October 14th 2020. That’s just a few short months away.

During Extended Support, products receive only updates defined as by the Fixed Life Cycle. For Exchange Server 2016, Fixed Life Cycle will include any required product updates due to security and time zone definition changes. With the transition of Exchange Server 2016 to Extended Support, the quarterly release schedule of cumulative updates (CU) will end. The last planned CU for Exchange Server 2016, CU20, will be released in March 2021. This is a change from earlier blog notes because it became clear that CU19 in December 2020, was too close the end of Mainstream Support to process all of the cases that came in by Oct 13th.   

There is one more consideration for this change that we want to address here today, and that is the ongoing use of Exchange Server 2016 for recipient management for hybrid organizations that have moved all their mailboxes to the cloud.

As you probably also know we have historically provided a free license for these ‘management’ servers if their only use is to properly manage Exchange attributes when recipient objects are mastered on-premises. You also know that we never provided this free license type for Exchange Server 2019.

We want to assure you that we are still committed to delivering a solution that will allow these lingering servers to be removed, but it will not arrive before Exchange Server 2016 enters Extended Support.

For this reason, we want to make our recommendation for this scenario clear. Our broad recommendation is to keep Exchange Server 2016 in production use until such point as we release a solution that allows those servers to be removed. As explained earlier, Extended Support still provides security and time zone updates and so keeping them in production and ensuring they are properly patched does not increase your risk profile in any way.

If you can’t move your mailboxes to the cloud and you plan on keeping mailboxes on-premises, then you really should be moving to Exchange Server 2019, and using that for both mailboxes and hybrid connectivity. That way you get full support including non-critical bug fixes and get ongoing product improvements.

When we have a solution available to allow any management-only servers to be removed, it may require an update to Exchange Server 2016, and in that case we may release a future CU or patch. Currently there is no plan to release future updates for Exchange 2016, but we want to assure our customers that if we need to do this to support the removal of these ‘management only’ servers, we will.  

Microsoft encourages Exchange Server 2016 customers to adopt CU20 as soon as possible to ensure uninterrupted delivery of any future security related fixes. After March 16, 2021, only CU20 or its successors will receive updates. During the Extended Support phase, only the latest CU is eligible to receive updates once the standard 3 month transition period of the prior CU has lapsed.  

Updates will continue to be made available via Windows Update and the Microsoft Download Center. Additional lifecycle information for all Microsoft products is available on docs.microsoft.com.

We hope this update was informative and we look forward to hearing your feedback and answering any questions you may still have.

The Exchange Team

Updated Feb 12, 2021
Version 12.0

29 Comments

  • Greg Taylor - EXCHANGE is there some particular reason that Exchange 2019 doesn't get free hybrid keys?  It's a harsh 180 turn to suddenly take that away after having the option 3 Exchange versions in a row previously.  The only thing I've seen said about this in this blog and the comments is that the answer is "No" and that won't change.  Have not yet seen the reason for the decision.

  • Kevin_Davis Hi Kevin, this blog is the place to watch for news. And if you follow me on Twitter (@gregtaylor_msft) I'll usually tweet when we post new articles. RSS is so 1990's.  

  • Kevin_Davis's avatar
    Kevin_Davis
    Brass Contributor

    Greg Taylor - EXCHANGE Thanks for the blog. Is there somewhere I can monitor for updates on this?

     

    We have a number of sites with active directory and Azure AD Connect to sync user passwords with their MS365 business apps identity. A lot of these sites never had Exchange, they used a 3rd party email provider. We now want to add a mailbox to their MS365 account, but as soon as we tell the customer that in order to do so Microsoft expect them to provision a full blown Exchange 2016 server on-premise, with the hardware, installation and ongoing maintenance cost that brings just to manage a few AD user attributes, it becomes a deal breaker. None of them can remove on-premise active directory due to application software requirements, but one or two have reluctantly opted to remove Azure AD Connect - not an ideal 'solution'. 

     

    The sites that did have a few Exchange servers in their estate are quite happy to reduce that to just one for management purposes - but they are coming from a completely different start point than those sites who never had Exchange.

     

    Best,

    Kevin

  • AnthonyNZ's avatar
    AnthonyNZ
    Copper Contributor

    Greg Taylor - EXCHANGE - Thanks for the update and clarification Greg.

     

    Can you give us any insight into the development of the final "solution"?

    How it's tracking, potential timeline, photo's of some poor geezer rocking back and forth under his desk in anguish?

     

    I've not seen any mention of it in over a year, if you can link to a roadmap that would be fantastic.

     

    Last mentioned here:

    https://techcommunity.microsoft.com/t5/exchange-team-blog/faqs-from-exchange-and-outlook-booths-at-2019-microsoft-ignite/ba-p/1053448

     

  • halbp's avatar
    halbp
    Brass Contributor

    Greg Taylor - EXCHANGE yes but why not just allow use of 2019 which will still be in mainstream support, given that it also supports hybrid? I don’t understand why 2016 would be free and 2019 wouldn’t be, it’s a pointless limitation.

  • Jpanski's avatar
    Jpanski
    Brass Contributor

    Greg Taylor - EXCHANGE Thanks Greg.  I read the article to set up relay through 365, option 3, but it's so confusing.  There was also no mention if that scenario would work if our current situation required adding the ms-Exch-SMTP-Accept-Any-Recipient permission for anonymous relay.  If not, I don't know how we'll ever get off the on-premise server.  For now since we need that box anyway it hasn't been an issue but certainly could be once the management server is no longer needed.  Thanks again.

  • Jpanski - in your case I'd say just stick with 2016, keep it up to date with security patches and figure out how to move those apps. 

    halbp - did you read the article? We're not going to do that. You can keep using 2016. 

  • halbp's avatar
    halbp
    Brass Contributor

    The issue with Hybrid is that there is a free license key available for 2016 but not for 2019. You need to update the HCW so we can use 2019 for Hybrid without paying for a license when it is just used for management.

  • Jpanski's avatar
    Jpanski
    Brass Contributor

    Great information. Thank you for the update.

    We have just completed our migration from 2010 to cloud with a 2016 management server. In our case our 2016 management server has just the 8 system mailboxes left and is also used for internal applications to relay mail. In this case would the recommendation be to move to 2019, stay on 2016 or something else? We are not sure when we can move our internal applications to send using 365.

    Thank you.