EN
FR 
DE 
IT 
PT 
ES 
Exchange Server Subscription Edition: Licensing and Migration Guide
Exchange Server Subscription Edition (Exchange Server SE) is Microsoft’s supported option for companies that still need Exchange on their own servers. It became available on 1 July 2025. This matters most for European businesses that must keep data in a set location, run regulated workloads, use complex hybrid setups or simply want local control of their email.
SE is not just “Exchange 2025” with a one-off licence. Exchange on premises looks and works the same, but the update and licensing rules change. The first RTM release was almost identical to Exchange Server 2019 CU15, so the first step is small on purpose. The bigger change is strategic. Microsoft moved Exchange Server to its Modern Lifecycle Policy. You now need ongoing subscription rights, through licences with active Software Assurance or qualifying cloud subscriptions.
This guide explains what this means for licensing, editions, CALs, migration and older Exchange licences. It is general business and technical information, not legal advice. Always check your agreement, the Microsoft Product Terms and your deployment plan before you buy or migrate.
What is Exchange Server Subscription Edition?
Exchange Server SE replaces Exchange Server 2019 for customers who run Microsoft’s mail server on their own infrastructure or in a suitable hosted environment. It supports classic on-premises setups and hybrid setups connected to Microsoft 365. You still manage servers, databases, mail flow, certificates, backups, high availability and security yourself, instead of handing all of this to Exchange Online.
Microsoft released SE on 1 July 2025. The official Exchange Team announcement explains that SE continues the on-premises product line but changes how it is updated and licensed. So the release matters to IT teams, and also to purchasing, finance, compliance and software asset management.
Modern Lifecycle Policy instead of a fixed end date
Older Exchange versions had a fixed lifecycle, with published end dates for mainstream and extended support. Exchange Server SE follows Microsoft’s Modern Lifecycle Policy instead. In practice, the product as a whole has no single end-of-support date. But you must stay properly licensed and keep your servers on supported updates and settings.
“No fixed end date” does not mean you can leave an installed version untouched forever. Microsoft releases cumulative updates, security updates and hotfixes. Support depends on running supported versions in supported setups. So administrators need a reliable patching process, a test environment, planned maintenance windows and one person who tracks changes to requirements and coexistence rules. Make the official Exchange update guidance part of your regular operations.
Exchange Server SE licensing: Server plus CAL
The core licensing model remains Server plus Client Access Licence. You license each running server instance as required by the applicable terms, then license access by users or devices through CALs or qualifying CAL-equivalent subscription licences. Buying a server licence alone does not normally license employees to access Exchange.
Microsoft’s current Exchange Server Product Terms say that SE server licences must be subscription licences or licences with active Software Assurance. The same rule applies to CALs. In some cases, the Product Terms also count qualifying Exchange Online user subscriptions as base or additional access licences.
Two principal entitlement routes
- Server and CAL licences with active Software Assurance: an organisation may obtain or maintain the relevant Exchange Server and CAL licences with active SA, subject to its volume licensing agreement and Product Terms.
- Subscription and cloud-based rights: subscription server/CAL licences or qualifying Exchange Online and Microsoft 365 user subscription licences may provide the required access rights where Microsoft defines them as CAL equivalents.
The right mix differs a lot between companies. One company may have on-premises mailboxes, hybrid users, service accounts, external users, contractors and several subsidiaries with different agreements. Do not assume that every Microsoft 365 plan gives the same Exchange Server rights. Check each group of users against the current Product Terms and your own licensing documents.
Also, do not describe Exchange Server SE as a perpetual or “used SE” licence. The product is built around an ongoing right to use it. An Exchange 2019 licence bought earlier without active SA does not turn into an SE licence just because the software is similar. Being able to install it and being allowed to use it are separate questions.
Exchange Server SE vs Exchange Server 2019
At RTM, the visible technical difference was intentionally small. Microsoft states in the Exchange Server SE release notes that SE RTM is code-equivalent to Exchange Server 2019 CU15 apart from the licence agreement, product name and build number. This allowed eligible Exchange 2019 CU14 or CU15 installations to use a comparatively direct in-place upgrade path.
| Area | Exchange 2019 | Exchange Server SE |
|---|---|---|
| Lifecycle | Fixed Lifecycle; support ended 14 October 2025 | Modern Lifecycle; continued support depends on current licensing and supported servicing |
| Initial code base | CU15 baseline | RTM nearly identical/code-equivalent to 2019 CU15, with limited identity and licensing changes |
| Licensing direction | Traditional version-specific server/CAL rights were available | Subscription licences or licences with active Software Assurance |
| Support status | Unsupported after 14 October 2025 | Supported on-premises successor when kept current |
| Future development | No longer the strategic on-premises release | Receives ongoing cumulative updates and product changes |
The practical conclusion is that SE RTM was a bridge, not a promise of permanent equivalence. New features and prerequisite changes arrive through later cumulative updates. Microsoft has also stated that Exchange SE CU2 will block coexistence with Exchange 2016 and Exchange 2019. Organisations should not build a long-term plan around leaving older servers in the same Exchange organisation.
Planning a migration to Exchange Server SE
An Exchange migration affects your whole directory. It is an infrastructure project, not a simple application upgrade. A safe plan starts with a list of what you have: Exchange versions and CUs, server roles, Active Directory health, namespaces, certificates, connectors, accepted domains, hybrid settings, third-party gateways, backup tools, monitoring, transport agents, public folders, database availability groups and business applications that send mail through SMTP.
From Exchange Server 2019
Microsoft supports an in-place upgrade from Exchange Server 2019 CU14 or CU15 to Exchange Server SE, if the detailed conditions and target build are met. Before you start, update the prerequisites, check your backups, record your customisations and test the upgrade in a similar environment. Read the current Microsoft upgrade and feature guidance first. Newer SE cumulative updates can enforce stricter coexistence rules, so the supported upgrade paths may get narrower over time.
From Exchange Server 2016
There is no direct in-place upgrade from Exchange 2016 to SE. A legacy migration is required. One supported strategy is to introduce Exchange 2019 CU15, move services and mailboxes, remove Exchange 2016, and then perform the supported in-place transition to SE. Depending on timing and Microsoft’s current guidance, a legacy migration directly to SE may also be appropriate. The key point is that Exchange 2016 binaries themselves are not upgraded in place to SE.
A practical migration sequence
- Confirm licensing first. Validate server, Standard CAL, any Enterprise CAL features and SA or subscription coverage before production deployment.
- Assess supportability. Check Active Directory, .NET, operating system, Outlook clients, hybrid dependencies and third-party products against Microsoft and vendor matrices.
- Bring the source environment current. Install required CUs and security updates, remediate unhealthy replication and remove unsupported legacy servers.
- Back up and document. Capture system state, Exchange configuration, certificates, connectors, virtual directories and recovery procedures. Test restores rather than relying on successful backup jobs alone.
- Pilot the change. Use representative mailboxes, mobile clients, Outlook profiles, shared mailboxes, SMTP applications, archiving and compliance workflows.
- Upgrade or migrate. Follow the supported path for the source version, with rollback and communication plans.
- Decommission cleanly. Remove old Exchange servers through supported procedures; do not simply switch off a server and leave its organisation objects behind.
- Operationalise Modern Lifecycle. Establish recurring CU/SU review, lab validation, maintenance windows and licence renewal controls.
Supported Windows Server versions
Microsoft’s Exchange supportability matrix lists Windows Server 2019, Windows Server 2022 and Windows Server 2025 for Exchange Server SE. Standard and Datacenter editions are supported, and Microsoft recommends Server Core. However, you cannot upgrade Windows Server to a new major version in place while Exchange is installed. Choose the target operating system carefully. Do not plan to upgrade it later underneath Exchange.
On-premises alternatives and older Exchange licences
Exchange SE is not the only option. Some organisations will prefer Exchange Online or Microsoft 365 so they have fewer servers to run. Others may pick another mail platform, a managed hosted service or a hybrid design. The right choice depends on data sovereignty, integration, speed, in-house skills, compliance, business continuity and total cost over several years.
If your organisation must stay on premises and wants a supported Microsoft email platform, Exchange Server SE is the right long-term option. If the cloud is acceptable, compare the full way of working, not just the licence names. Identity, migration, backups, retention, security tools, eDiscovery, network resilience, support and user training all affect cost and risk.
Can used Exchange 2019 or 2016 licences still be considered?
Licendi offers a range of Microsoft Exchange Server licences, including Exchange Server 2019 Standard, Exchange Server 2019 Enterprise and Exchange Server 2019 User CALs. In the European Economic Area, qualifying perpetual software licences may be resold under the exhaustion principle, if the legal conditions are met. A solid transaction needs proof: where the licence came from, the chain of ownership, its scope, proof that the previous owner stopped using it, and matching server and CAL numbers.
But being allowed to resell a licence is not the same as Microsoft support. Exchange Server 2016 and 2019 reached end of support on 14 October 2025. Microsoft no longer provides their normal security updates, bug fixes or technical support. Existing servers may keep running. But email servers that face the Internet without vendor security updates create serious security and compliance risks.
Older perpetual licences still have legitimate uses. They can document an existing setup, cover an isolated legacy workload, or support a controlled test or recovery environment. They can also cover a time-limited migration, if experts have reviewed the design and the risk. But they should not be sold as equal to Exchange SE, as a way to get SE rights, or as the default choice for a new production email system.
Before buying, ask three separate questions: Is the transfer legally valid? Is the planned use covered by the licence terms? Is the software technically supportable and sufficiently secure? A “yes” to one does not answer the other two. Organisations in regulated sectors should involve legal counsel, security leadership and their auditor where appropriate.
Exchange SE Standard vs Enterprise
Exchange Server SE comes in Standard and Enterprise server editions. The main difference between them is database scale, not a different email product. According to Microsoft’s Exchange editions guidance, Standard Edition supports up to five mounted databases per server. Enterprise Edition supports up to 100 mounted databases per server. A recovery database does not count towards these limits.
- Standard Edition generally suits smaller deployments, branch environments and organisations whose mailbox and resilience design fits within five mounted databases per server.
- Enterprise Edition is intended for larger or more segmented deployments that need more mounted databases per server, including designs using multiple active and passive database copies.
Do not choose an edition by mailbox count alone. Database availability groups, recovery goals, maintenance plans, passive copies, storage layout and failure domains can all raise the number of mounted databases you need. Plan the architecture first, then choose the edition.
Also distinguish the server edition from the CAL level. An Enterprise CAL is additive to a Standard CAL and grants specified advanced functionality; it is not the same thing as an Enterprise server licence. A company can require Enterprise CAL functionality even when its database design only needs Standard server edition.
User CAL vs Device CAL
A User CAL licenses one named user to access Exchange from multiple devices. It is usually the simpler fit for mobile and hybrid working: one employee may use a desktop, laptop, smartphone and tablet. A Device CAL licenses one device for access by multiple users and can be economical for shared workstations, factory terminals, reception desks, libraries, clinics or shift-based operations.
| Choose User CAL when | Choose Device CAL when |
|---|---|
| People use several devices | Many people share a small number of devices |
| Remote and mobile access is common | Access is tied to controlled fixed terminals |
| Users access from personal or managed endpoints | Shift workers do not access Exchange elsewhere |
Mixed models can work, but they need accurate records. Count real access, including shared devices, administrators, service use and users covered by subscriptions that count as CALs. For SE, the CALs you choose must also meet the ongoing subscription or active-SA rule.
Frequently asked questions
Is Exchange Server Subscription Edition cloud-only?
No. Exchange Server SE is an on-premises server product and can also participate in hybrid deployments. The “Subscription Edition” name refers primarily to ongoing licensing and servicing, not to moving every mailbox to Microsoft’s cloud.
Is Exchange Server SE a perpetual licence?
No. Microsoft’s Product Terms require subscription licences or licences with active Software Assurance for the SE Server/CAL model. Do not treat SE as a one-off perpetual purchase or as a used perpetual product.
Can Exchange 2019 be upgraded in place to SE?
Microsoft supports an in-place upgrade from Exchange Server 2019 CU14 or CU15 to supported Exchange SE builds. Current prerequisites and coexistence rules apply. Check the latest Microsoft guidance right before you approve the change.
Can Exchange 2016 be upgraded directly in place?
No. Exchange 2016 cannot be upgraded in place to SE. It requires a legacy migration path, commonly through Exchange 2019 CU15 before an SE in-place transition, or another currently supported migration route documented by Microsoft.
When did support end for Exchange 2016 and 2019?
Support for both products ended on 14 October 2025. They may continue running, but Microsoft no longer provides their normal security updates, bug fixes or technical support.
Will SE coexist indefinitely with Exchange 2016 or 2019?
No. Microsoft says Exchange Server SE CU2 Setup will block coexistence with Exchange 2016 and 2019. Migration plans should remove those versions before moving to a build that enforces the block.
Which Windows Server versions support Exchange SE?
Microsoft lists Windows Server 2019, Windows Server 2022 and Windows Server 2025. Always check the current supportability matrix, the required .NET version, the Active Directory requirements and the cumulative update level.
Do I need both a server licence and CALs?
Normally, yes. Exchange uses a Server/CAL model. Each server instance needs the right server licence, and each user or device needs a CAL or a qualifying licence that counts as one. Enterprise CAL features are added on top of the base Standard CAL.
Conclusion: choose a supported Exchange strategy
Exchange Server SE keeps a supported on-premises option alive, but it also means ongoing management. The first code base was very close to Exchange 2019 CU15; the long-term model is not. To succeed with SE, you need a current licence, regular cumulative updates, a supported Windows Server platform and a plan to remove Exchange 2016 and 2019 before future coexistence blocks affect you.
For many European businesses, the choice is not just “server or cloud”. It is a balance of control, compliance, resilience, in-house skills and long-term cost. Used Exchange 2019 or 2016 licences may still be useful in clearly defined and legally documented legacy cases. But they do not replace a supported SE deployment.
