Finally, there’s some news on Microsoft Exchange Server vNext (Subscription Edition). See what’s new and how to migrate.
[Update]: This article was last updated on October 7, 2024. There’s more details on the release timeline and licensing.
Exchange Server vNext is the codename for the new Exchange Server version. The official name is Exchange Server Subscription Edition (SE). After its first announcement back in 2020, Microsoft has finally revealed more information about what to expect from the latest and final version of on-premises Exchange. So, if you want to know what’s new, what Exchange Server SE RTM is, when and how to migrate, and more, read on.
When is Exchange Server Subscription Edition (SE) coming?
Exchange Server Subscription Edition (SE) will be released in Q3 2025. But that’s not all.
To be more specific, Exchange Server SE RTM is planned for the early part of the second half of 2025, and Exchange Server SE CU1 is scheduled for later that year. Which is quite a complex way of saying it will be available near the end of 2025.
What is Exchange Server SE RTM?
Exchange Server SE RTM is the first release of the vNext Server. RTM stands for “Release to Manufacturing”. In common English, it’s the first globally available release. It’s quite new, since RTM has code parity with Exchange Server 2019 CU15. Basically, nothing changes between Exchange Server 2019 and Exchange Server SE.
Some of you might point out that it’s quite similar to differences between Exchange Server 2016 and 2019 – there weren’t that many changes when Exchange 2019 was released, either.
Now, there’s the next release planned for the end of 2025 – Exchange Server SE CU1. It will introduce new features in SE. And here’s another extremely important difference between RTM and CU1 – RTM doesn’t support coexistence with Exchange 2013. Understandable. But CU1 doesn’t support coexistence with Exchange 2013, 2016 OR 2019.
In other words, the plan is to install Exchange Server RTM as it is, decommission all the other Exchange editions in less than half a year, and then install CU1. Sounds a bit like testing in production, doesn’t it? To make things even more interesting, there’s no public beta for SE. So, let’s see what we are jumping into and what the new Exchange Server has to offer
What’s new in Exchange Server vNext?
Let’s take a look at all the new things we can expect from the newest Exchange Server.
Subscription Edition
The main difference, and the one most discussed from day one, is included in the official name. To remind you:
Exchange Server Subscription Edition (SE)
It’s no longer a one-time purchase with a strongly suggested upgrade required every few years when the server version reaches end of life. The only way to have the new Exchange Server with a free license is to use it in a hybrid environment. Then, the free hybrid license will be provided by the Hybrid Configuration Wizard.
Licensing changes
If you’re familiar with the Exchange Server’s pricing model, you will know that you had to buy Server licenses and CALs (client access licenses) for every user or device accessing the server. But with the arrival of SE, there’s a slight change in that.
You still need to buy Server licenses and CALs, but now you either need a cloud subscription license for every user (preferably E3 or E5), or, if you’re not going hybrid, your licenses need to have “Software Assurance”. In short, Software Assurance is a licensing addon that increases the price of your licenses in exchange for licenses for version upgrades. There’s more to it, but I’ll let you do more research on the dedicated Microsoft page.
No co-existence
Sysadmins have learnt (sometimes the hard way) that the coexistence of Exchange servers is limited to the last 2 versions. So, you could have Exchange 2013 and 2019 in one environment, but Exchange 2010 and 2019 couldn’t coexist. In other words, migrating from Exchange 2010 to Exchange 2019 required “double-hopping” if using native tools. Or a migration software like CodeTwo Exchange Migration, which makes such shifts not only possible but also much less stressful, thanks to automation of the whole process, reporting & notifications to keep you posted, easy setup and unlimited delta migrations.
No support for Exchange Server 2013
Exchange Server 2013 reached its end of life (or end of extended support) on April 11, 2023. It means that since that date, it’s no longer getting any security updates and is considered out-of-date, not secure and overall archaic.
If you have Exchange 2013 in your environment, you won’t be able to upgrade to Exchange Server 2019 CU15 or to Exchange Server Subscription Edition RTM – the setup will throw an error. And to migrate to Exchange Server SE CU1, you need to be on RTM already.
So, since you’ll have to migrate eventually, now’s the perfect time to move away from Exchange 2013.
In-place upgrade
Now this is wonderful news for Exchange Server admins all over the world. Instead of a complex migration project, you’ll be able to perform an in-place upgrade to Exchange Server SE. The experience is to be similar to installing a Cumulative Update (CU).
However, the catch is that you will be able to perform the in-place upgrade only if you’re already on Exchange 2019 on Windows Server 2022 or Windows Server 2025. A legacy migration from Exchange 2016 to Exchange SE will also be possible.
Modern Lifecycle Policy
In the past, Exchange servers were subject to the Fixed Lifecycle Policy. In other words, they had set support dates:
- Mainstream End Date – when no more Cumulative Updates (CUs) were offered.
- Extended End Date – when Security Updates (SUs) stopped, with a few exceptions.
Exchange Server SE will follow the Modern Lifecycle Policy (described here). The modern policy doesn’t have support dates set in stone. Instead, it follows the following rules:
- Change notification – this policy gives a minimum of 30 days before you are required to take action to avoid significant degradation to the normal use of the product or service.
- Continuity and migration notification – a guarantee that Microsoft will let you know a minimum of 12 months and up to 3 years before they end support for a product. Since Exchange Server SE is supposed to be the last on-premises Exchange, most probably your only migration option at that point would be to move to Exchange Online or try to find an alternative to Microsoft.
Other changes
Other changes that will be introduced in Exchange Server SE include:
- The default authentication protocol will change from NTLMv2 to Kerberos.
- Remote PowerShell (RPS) protocol will be deprecated. It will be supported in CU1, but after that, you will need to switch to the Admin API, which will include a set of REST-based APIs. It’s nothing new for Exchange Online admins, but on-premises PowerShell masters will be required to make significant script updates.
- Outlook Anywhere will be deprecated starting from CU1.
What about new features?
If you look closely at the feature list, you will notice that the pricing shift is the most substantial change.
There are no changes to server roles and no drastic functionality changes. When it comes to new features, I’d expect that Exchange Server SE will get some new(ish) stuff handed down from its “older brother” –Exchange Online.
So, Exchange Server SE serves two most important purposes:
- To support hybrid environments without the need to migrate your mailboxes between on-premises environments.
- To provide an on-premises Exchange solution to the most reluctant to migrate to the cloud.
What options do I have?
If you have any kind of risk management introduced in place in your organization, using outdated infrastructure is out of the question. So, if you do have on-premises Exchange lurking in your environment, here are your options:
- Migrate to Exchange Online before October 14, 2025.
- Migrate to Exchange 2019 as soon as possible, then perform an in-place upgrade.
- Legacy-migrate from Exchange 2016 to Exchange Server SE as soon as it is released.
Why is it so important to plan migration from Exchange 2016 or Exchange 2019 soon? They are reaching their end of life.
Exchange 2016 & 2019 end of life
“The end of life” is a common term for the end of extended support for Microsoft products subject to the Fixed Lifecycle Policy. That’s when they stop getting security updates, and it becomes increasingly difficult to keep them secure.
Both Exchange 2016 and 2019 will reach their demise on the same date: October 14, 2025. Which gives you 3 months tops to upgrade to Exchange Server SE. It’s not a lot of time, is it?
Another push to the cloud
Microsoft has been battling outdated Exchange Servers using various methods. Transport-based enforcement system is one of them. It’s a method responsible for throttling and blocking emails from persistently vulnerable Exchange Servers.
Exchange Server vNext removes the need to upgrade servers to the newer versions and makes the update process much easier. At the same time, it’s no mystery that Exchange Online and all the connected services are the first to receive crucial security and feature updates. And since Exchange Server becomes a subscription-based service, the overall cost of maintaining your on-premises infrastructure will further increase. Which means that there’s even fewer reasons not to shift to the cloud.
See how easy it is to migrate to Exchange Online using CodeTwo migration software:
It will be interesting to see if the Subscription Edition (SE) of Exchange Server will allow on-premises environments to use technical accounts for legacy systems that cannot support OAuth 2.0. This could provide a solution enabling these systems to send emails via Exchange SE while utilizing Exchange Online for delivery.
What is the yearly cost? A lot of people need to know for budget next year
There is no indication on when Microsoft will release the Subscription Edition pricing. We are monitoring this closely and will give an update as soon as Microsoft announces specifics.