Blog Post

Exchange Team Blog
2 MIN READ

Where is Exchange SE CU1 anyway?

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Aug 13, 2026

We are getting questions from our customers on when they can expect us to release Exchange SE Cumulative Update 1 (CU1). After all, in the past we mentioned that it would be released by the end of the first half of calendar year 2026, later updated to “second half of 2026”. What is the deal? Where is CU1?

Over the last few months, various Microsoft execs made statements explaining how Microsoft is leveraging a variety of AI tools to help find vulnerabilities in our products (examples of such announcements can be found here, here and here).

It should come as no surprise that this is a Microsoft-wide initiative. Many teams, Exchange Server included, are working through reported issues – which includes validation that they are real security issues, reproducing, fixing, testing for regressions / issues after fixes are deployed and releasing updates monthly.

We have been releasing security updates for Exchange Server regularly: May, June, July, August. You can expect this increased pace of security releases to continue. We are prioritizing security above all else.

While all of that is happening, we are also working on CU1; we are regularly rolling our monthly security payload into our internal CU1 build and plan to release Exchange SE CU1 as soon as we get a reasonable stable point and have a month without pressing security payload. We really do not want to try to release a new CU1 and then immediately supersede the new CU with security updates as that would create double the update work for many organization administrators. Even internally, trying to ensure that two major releases (Security Update and a CU) get appropriately tested so we can ensure high quality and nothing falls through the cracks would be very challenging as CU1 must be all inclusive of everything that we released since the RTM.

In short: Exchange SE CU1 is coming; we do not have a date to give you. But we did not forget about it.

Until then, please keep Upgrading your organization to Exchange Server SE | Microsoft Community Hub and if you are already on Exchange Server SE, stay up to date!

The Exchange Server Team

Published Aug 13, 2026
Version 1.0

6 Comments

  • derSchweiger's avatar
    derSchweiger
    Brass Contributor

    Thank you for the transparency and for keeping us updated. As a Cloud Solution Provider supporting several Exchange environments, we greatly appreciate ongoing improvements and look forward to future feature enhancements.

  • RonMR's avatar
    RonMR
    Copper Contributor

    Patching comment in general. I’ve noticed Exchange changed how it shuts down services during patching. It used to disable the service first and then stop it, which prevented anything from restarting mid‑patch. Now it stops the services first and only disables them afterward, which leaves a window where SCM or monitoring tools can restart things before setup is ready. That’s caused patch failures for me more than once.

    I’d really like to see the old behavior come back — disable first, then stop — since it avoids the whole race condition and makes patching way more reliable.

  • greatquux's avatar
    greatquux
    Brass Contributor

    I also greatly appreciate the transparency.  While there are security and sustaining updates (like TLS 1.3 and modern auth) that have to be implemented, for my part, I think it's OK to keep on-prem Exchange as stable and performant as possible, focusing on making sure the core functionality works great (including Search which can still be a pain sometimes when it doesn't work!)   And making it as easy as possible to install updates (CUs and their associated downtime really do suck).  

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      For what it is worth, I personally CANNOT WAIT for October to be over so we are finally out of the business of building / testing all the Exchange 2016/2019 scenarios and updates and can focus on Exchange SE and various improvements we want to do with it.

  • kmaurer1720's avatar
    kmaurer1720
    Copper Contributor

    Appreciate the transparency - thank you for the update!