فا
MSLicenseHub
collaboration · reference
✉️

Exchange Server Subscription Edition (SE)

Exchange Server SE — the new subscription-licensed on-premises Exchange, replacing the perpetual 2019 line.

EXCHANGE SERVER SUBSCRIPTION EDITION (SE)
On this page

Editions · channels · activation · audit notes · FAQs

Editions covered
4
Edition matrix with feature differences and the right audience.
In-depth sections
7
Channels, activation, audit, modern management & more.
FAQs answered
5
Common questions buyers and IT admins ask before purchase.
Words of reference
0.7k
Plain-English, no vendor agenda, updated to current Product Terms.
Edition matrix

Pick the right edition

Each edition targets a specific scale and feature set. Match the workload, not the price tag.

Edition 1
Standard SE

Up to 5 mailbox databases per server. Same feature set as Enterprise, smaller deployments.

Edition 2
Enterprise SE

Up to 100 mailbox databases per server. The right choice for any production DAG.

Edition 3
Standard CAL

Per user or device. Core mailbox, calendar and contacts.

Edition 4
Enterprise CAL

Additive. Adds DLP, in-place archive, journaling, IRM. Per user or device.

Side-by-side

Edition comparison

Heuristic capability matrix derived from each edition's intended use. For binding commitments, always confirm against the current Product Terms.

CapabilityStandard SEEnterprise SEStandard CALEnterprise CAL
Target audienceEnterpriseEnterpriseGeneralEnterprise
Domain / Entra join
Virtualisation rights
Advanced security
Centralised management
Volume Licensing path
Deep dive

Exchange Server Subscription Edition (SE) — what to actually know

Exchange Server Subscription Edition (SE) is the successor to Exchange Server 2019 and represents Microsoft's pivot to a subscription model for on-premises mail. There will be no Exchange Server 2025 perpetual release; SE is the path forward for every organisation that needs mailboxes outside Exchange Online. The good news for existing 2019 estates: SE installs as an in-place upgrade on the same servers, with the same operating system requirements, the same DAG topologies and the same management tools. What changes is the licensing model and the rhythm of cumulative updates.

01

Why a Subscription Edition exists

Exchange has been on a slow consolidation curve toward Exchange Online for a decade, but Microsoft still has tens of thousands of customers who genuinely cannot move to the cloud — sovereign clouds, classified networks, regulated industries, regions with strict data-residency laws, and organisations whose business model assumes physical control of the mail platform. SE keeps a supported on-prem option for those scenarios while moving them off the perpetual model that has constrained Microsoft's investment in new features. SE will receive ongoing cumulative updates with new features as well as security updates, instead of the 'security only' posture that on-prem Exchange has had for several years.

02

Standard vs Enterprise — same as before

Like 2019 before it, SE ships in Standard and Enterprise editions on the server side. Standard caps mailbox databases at five per server; Enterprise raises that to one hundred and is the right pick for any DAG-based deployment at scale. Both editions ship the same feature set — the difference is purely a database-count limit. Most production deployments above a few hundred mailboxes will use Enterprise simply to keep DAG database distribution flexible.

03

Subscription licensing and the CAL story

Server licences are now sold as a subscription, billed annually, with no perpetual buy-out. CALs follow the same model: Standard CAL covers core email; Enterprise CAL is additive (bought on top of Standard) and unlocks Data Loss Prevention, in-place archive, journaling and information rights management. Every user or device with a mailbox needs the corresponding CAL stack. For organisations already on Microsoft 365 E3 or E5 with the Exchange Online entitlement, the Exchange Server CAL is included via the dual-use rights baked into those SKUs — many customers do not realise that the on-prem Exchange CAL they would otherwise buy is already on their Microsoft 365 invoice.

04

In-place upgrade from Exchange 2019

SE installs as a Cumulative Update on top of an Exchange 2019 CU14 (or later) deployment. The upgrade preserves DAG membership, transport rules, send/receive connectors, certificates and mailbox locations — there is no schema rebuild and no database move. Microsoft strongly recommends running the latest Exchange 2019 CU and the most recent security update before initiating the SE upgrade, and treating the first server in a DAG as a pilot for at least a few days before rolling forward. Coexistence with Exchange 2016 in the same organisation is no longer supported; any 2016 servers must be decommissioned before SE goes live.

05

Hybrid with Exchange Online

The free Hybrid Configuration Wizard continues to configure coexistence between SE and Exchange Online — shared address space, free / busy lookup between cloud and on-prem mailboxes, calendar federation, and TLS-secured mail flow. Microsoft offers free Hybrid Exchange Server keys for organisations whose only on-prem Exchange role is to manage attributes and route mail for a tenant whose mailboxes all live in Exchange Online; the hybrid server itself does not host production mailboxes and so does not consume a paid subscription.

06

Operating system, hardware and security posture

Exchange Server SE runs on Windows Server 2019 or 2022 today, with Windows Server 2025 support arriving in a cumulative update. Recommended hardware is the same as 2019: plenty of RAM (DAG-aware sizing calculators apply), SSDs for the database volumes, and Exchange-aware backups via VSS. The security baseline is more important than ever — Exchange remains a frequent target for attackers, and SE turns on Extended Protection by default, requires TLS 1.2 minimum, and integrates more tightly with the Microsoft Exchange Emergency Mitigation Service that ships out-of-band defensive rules.

07

Roadmap and end-of-support for 2019

Exchange Server 2019 reached end of mainstream support in early 2024 and extended support runs to October 2025. After that date, on-prem mail outside SE has no supported path — running it for production mail flow becomes a documented compliance issue. SE itself will get a defined release cadence (cumulative updates roughly twice a year, security updates as needed) and Microsoft has committed to a multi-year support horizon for it, with the next major version planned for around 2029 on a similar subscription basis.

By channel

Where to buy this product

Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.

Channel fit (typical buyer)
Volume Licensing9
CSP / Microsoft 36510
Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline

Lifecycle phases to plan against

Exchange, SharePoint and Project Server are mature on-prem workloads whose pricing assumes you have already decided not to move to Microsoft 365. Validate that decision honestly before you commit to a multi-year hardware and CAL refresh.

Phase 1
Server release
Launch

Standard and Enterprise server licences via Volume Licensing. Each role (mailbox, edge, web front-end) typically requires its own server licence.

Phase 2
Mainstream support
5 years

Cumulative updates roughly quarterly. Schema and protocol changes only here.

Phase 3
Extended support
Years 5–10

Security-only updates. No new features. Hybrid configuration with the cloud often becomes the only growth path.

Phase 4
End of support
Year 10

Microsoft has been clear: on-prem collaboration is shrinking. Plan a cloud migration before EoL rather than during.

Procurement checklist

Do this, not that

The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.

DO

License every server role + a CAL for every authenticated user or device touching it.

DON'T

Forget the External Connector licence when external partners access the server without per-user CALs.

DO

Run a hybrid for at least one migration window so identities and mail flow cut over cleanly.

DON'T

Try to skip Exchange Online hybrid with a third-party migration tool unless you genuinely understand the autodiscover and free/busy implications.

DO

Pair Enterprise CALs with the security and compliance tooling you actually use (DLP, hold, journaling).

DON'T

Buy Enterprise CALs reflexively when Standard CALs cover the workload — the gap is real money per user.

Typical deployments

How buyers actually use Exchange Server Subscription Edition (SE)

Three reference deployments — find the closest match and adapt rather than starting from zero.

Scenario 1
Regulated on-prem

Industries that legally cannot offload to a public cloud (defence, certain healthcare contexts) — Exchange / SharePoint on-prem with full Enterprise CALs and a strict hybrid identity story.

Scenario 2
Hybrid mid-market

Most mailboxes in Exchange Online, a small Exchange Server kept for legacy line-of-business applications, SharePoint Online for everything new and SharePoint Server only where workflows demand on-prem code.

Scenario 3
Cloud-first SMB

No on-prem collaboration at all — Microsoft 365 Business Premium covers mail, sites, Teams, security and device management as a single subscription.

Cost optimisation

Where the savings actually live

None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.

💰
Cloud is almost always cheaper at TCO

Once you add hardware refresh, storage, backup, antivirus, anti-spam, certificates and the staff time to run an Exchange / SharePoint farm, Microsoft 365 wins on TCO for the vast majority of organisations.

📊
Bridge with hybrid

Hybrid identity + hybrid mail flow lets you migrate users at your own pace and avoid a big-bang cutover.

🎯
Re-evaluate Enterprise CALs annually

Some Enterprise CAL features (e.g. DLP, journaling) overlap with what you may already pay for in M365 — do not stack the bill.

Counterfeit & risk

Red flags when buying second-hand

These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.

01
Standalone OEM key sold below market

OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.

02
Lifetime key with no invoice or VLSC record

Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.

03
Key works once, then 'not genuine' after the next cumulative update

Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.

04
Seller refuses to put the entitlement in your tenant

Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.

Acronyms

Licensing terms used on this page

Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.

CSP

Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.

VLSC

Volume Licensing Service Center — the portal where Volume Licensing keys, agreements and downloads live.

MAK

Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.

KMS

Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.

EA

Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.

SA

Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.

Browse the full glossary →
FAQ

Frequently asked questions

Should we still deploy Exchange 2019 in 2026?+
Only for net-new hybrid installs that are explicitly short-lived, and even then SE is the safer answer. Greenfield on-prem deployments should plan around Exchange Server SE from day one. The in-place upgrade from 2019 to SE is straightforward and there is no perpetual successor to wait for.
Can a single CAL cover both Exchange 2019 and SE?+
No — the new SE subscription CAL replaces the perpetual CAL model. Existing 2019 CALs continue to cover 2019 deployments for the remainder of extended support, but moving to SE requires moving to the SE subscription CAL.
Do hybrid management servers need a paid subscription?+
No. Microsoft provides free Hybrid Edition keys for servers whose only role is hybrid management for an Exchange Online tenant. The moment the server hosts a production mailbox, it requires the standard SE subscription.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel, an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. If someone offers you a standalone OEM key, treat it as a red flag: it almost always means either a leaked volume key, a counterfeit, or a key harvested from decommissioned hardware, none of which Microsoft will honour at audit time.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy of a product to a proof of purchase (Volume Licensing Service Center record, CSP invoice, or sealed Retail packaging with the original key). They also verify edition alignment — for example that every server reporting a Datacenter feature actually carries a Datacenter license — and that CAL counts cover the maximum number of authenticated users or devices during the audit window. Soft enforcement (warnings, true-up invoices) is common for small variances; large gaps escalate to formal Software Asset Management engagements and back-billing at list price.
Related

Other products in this category