Blog Post

Exchange Team Blog
2 MIN READ

Exchange Server: The Road Ahead

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Nov 13, 2013

We’re approaching the one-year anniversary of the release of Exchange Server 2013. This is traditionally the time when people start asking questions like:

When is Service Pack 1 coming?
What’s the timeline for the next Exchange Server release?
What are you cooking up for the next version of Exchange?

This time around, we’re also hearing a few customers ask:

Will there be another version of Exchange Server?

We hope the answer to that question is obvious, but we wanted to go on record to make sure no one is confused. Here are the facts:

  • The Exchange engineering team is hard at work developing the next version of Exchange.
  • We expect the next on-premises version to be released according to our traditional release cadence (2-3 years after the previous version).
  • Microsoft has no plans to stop delivering on-premises releases of Exchange.

It’s true that customers are shifting their Exchange deployments from on-premises to the cloud, and it’s true that we are investing heavily in Office 365. We’re fans of Office 365 because we’ve seen that when customers run email in our cloud, they save money, they get larger mailboxes, and they get faster access to our latest innovations. IT admins spend less time maintaining servers and more time lighting up features that make users happy. Running Office 365 also brings us real-world experience that helps us build a better on-premises product.

While we are enthusiastic about the cloud, we also understand that our customers will transition to the cloud at their own pace. Many customers will remain on-premises or in hybrid deployments for the foreseeable future, and we want to keep delivering our newest and best features to them. Fortunately, our development process allows us to do that. We have a single code base that serves both cloud and on-premises customers, so we can deliver innovation to both groups.

Our development strategy continues to focus on Office 365 as the initial platform where we roll out new features. This approach allows us to introduce and test new features at scale before including relevant functionality into on-premises updates. The benefits of the strategy can be seen in Exchange 2013, where features such as Managed Availability are directly based on work done to automate and improve our datacenter operations. If you want clues about what’s coming in the next version of Exchange Server, keep an eye on what’s happening in Office 365.

It’s an exciting time for messaging and collaboration. Today’s technology trends— cloud, mobile devices, social computing, machine learning—all have the opportunity to make email more useful and powerful. We’ve got some great stuff cooking, and we’re committed to bringing innovation to all of our customers, whether they choose to deploy Exchange in the cloud or on-premises. The Exchange product team and our customers have a 17+ year history of successfully navigating changes in IT architecture and management together. We look forward to continuing that tradition with you.

Perry Clarke
Corporate Vice President
Microsoft Exchange

Updated Jul 01, 2019
Version 2.0

121 Comments

  • Need more clear road map for CUs. It was stated one every quarter, but it seems it already slipped the date. There are issues in CU1, CU2 and no interim fixes are offered. I have few large customers waiting CU3 to fix some of the production issues.

    when is CU3 coming? or SP1? I noticed cloud servers had been updates some time ago...

  • The question I hear most is: what happened to the quality of the products and updates Microsoft (and specifically the Exchange team) releases. Well, the answer is that the focus shifted from on-premises products to cloud services. And I blame nobody expect for the upper management who decided that the company needs to become a Devices and Services company.

    And what good does this strategy bring us then? Managed availability is pretty much useless for on-premises deployments without SCOM because of the lack of user interface and reporting capabilities. What does it mean if 30% of the components report Unhealthy on a fresh out-of-the-box Exchange 2013 install? The other example I often hear is EAC which I'm told is what I should prefer over EMC because it's webbased. EAC is there because Microsoft needed it for Exchange Online, no on-premises customer asked to take away the previous interface with more features. Why do we see so many errors and warning in the event logs of our CU2 servers, why are there no real answers in the Forums except for 'me too, I see this too on all my Exchange 2013 servers'?

    So yes, I agree that the development strategy continues focusses on Office 365. But please be honest and don't tell us that this brings only benefits. Let me wrap up my rant with another question: Many customers are looking for guidance to configure Server 2012 R2 WAP for the publishing of Exchange. Can we expect a whitepaper similar to the excellent TMG and UAG ones?

  • It would be nice to see a more defined roadmap as David said - this will allow enterprise to plan their strategies as well....so Exchange 2016?

  • sounds good except one line:)

    "It’s true that customers are shifting their Exchange deployments from on-premises to the cloud"

    not exactly accurate when you consider all exchange base install compared to office 365(companies that migrated without everyone else... and DIDNT migrate back to on-premises)

    im an exchange fan, don't get me wrong, but from hearing what the majority of my customers say, they aren't going to cloud any time soon(from different reasons)

  • This is great news but you didn't answer one of the very questions that you brought up?

    When is Service Pack 1 coming?  

    For that matter, you initially promised quarterly releases for cumulative updates to correct many of the bugs present in Exchange 2013.  After the last snafu, you have not only passed that schedule but have gone dark as to when we can expect the next cu release.  Will you return to quarterly CU releases or will they be released as before (infrequently)?

    There are some very clear issues with on-premises Exchange 2013 such as the issue with transparent OWA rendering to existing E2K10 users.  This is an example of an issue that doesn't affect the cloud but on-premises users.  It is ok that MS is focusing on the cloud but this seems to be not in conjunction but to the exclusion of on-premises users.  The trickle down effect only seems to apply when the cloud and on-premises share the same issues or features.  In fact, when CU2 was released there weren't even any accompanying notes as to what was even being fixed.  

    So your post is well-intentioned and a good direction but doesn't even scratch the surface of the pain the on-premises users are facing when promoting your product.

  • I, for one, will be recommending to my company (10K seat or so) to remain on Exchange 2010 based on current issues and the feedback provided here on this blog posting.
  • Team must be on holidays, celebrating a year of not creating anything that works, and still turning a profit off licenses.

    Here's an IT phrase for 2014: Post-Microsoft Solution

  • It seems the Exchange team has simply abandoned this blog and/or posts
  • From what I'm gathering of this post, the road ahead for Exchange appears to be disaster.