فا
MSLicenseHub
collaboration · reference
📨

Exchange Server 2019

Exchange Server 2019 — the last cumulative-update version before Exchange Server SE: per-server licensing, CALs, support timeline through October 2025.

EXCHANGE SERVER 2019
On this page

Editions · channels · activation · audit notes · FAQs

Editions covered
4
Edition matrix with feature differences and the right audience.
In-depth sections
5
Channels, activation, audit, modern management & more.
FAQs answered
6
Common questions buyers and IT admins ask before purchase.
Words of reference
0.6k
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

Per-server. Up to 5 mailbox databases.

Edition 2
Enterprise

Per-server. Up to 100 mailbox databases. Same feature set otherwise.

Edition 3
Standard CAL

Per user or device. Core mailbox features.

Edition 4
Enterprise CAL

Add-on to Standard CAL. Adds UM, advanced compliance, per-user journaling.

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.

CapabilityStandardEnterpriseStandard CALEnterprise CAL
Target audienceGeneralEnterpriseGeneralEnterprise
Domain / Entra join
Virtualisation rights
Advanced security
Centralised management
Volume Licensing path
Deep dive

Exchange Server 2019 — what to actually know

Exchange Server 2019 was the long-running on-premises Exchange release that preceded Exchange Server Subscription Edition (SE). It shipped in October 2018 and entered extended support on 14 October 2025 — mainstream support has now ended. Exchange Server SE is functionally a continuation of 2019 with a subscription licensing model and rolling updates; existing 2019 Standard and Enterprise installations can be in-place upgraded to SE without an architecture change. For estates still on 2019, the immediate question is whether to migrate to SE on-prem, move to Exchange Online (as part of Microsoft 365), or operate a hybrid through October 2025's extended support window.

01

Editions: Standard vs Enterprise

Exchange Server 2019 has two editions: Standard, which supports up to five mailbox databases per server, and Enterprise, which raises the cap to 100. Both editions ship the same feature set otherwise — Database Availability Groups (DAGs), client access services, transport rules, anti-malware, and the on-premises management console. Enterprise is the right choice for most production deployments because the five-database cap on Standard is hit quickly once mailbox sizes and tiering policies are factored in. Pricing is per-server.

02

CALs: Standard vs Enterprise

Every user or device with a mailbox or that uses Exchange features needs a Client Access Licence. Standard CALs cover core email functionality. Enterprise CALs are additive to Standard CALs (you need both for any user that uses Enterprise CAL features) and unlock unified messaging, advanced compliance (in-place hold, in-place eDiscovery, Data Loss Prevention), and per-user journaling. Most production deployments on Exchange 2019 carry Standard CALs for the bulk of users and Enterprise CAL add-ons for executives and regulated roles. Service accounts and conference-room mailboxes also count unless explicitly excluded by service-account exception terms.

03

Support timeline and the Server SE bridge

Extended support for Exchange Server 2019 runs through 14 October 2025 with security updates only — no new cumulative updates after CU14, no feature work, no design changes. Exchange Server Subscription Edition (SE) shipped in mid-2025 and is the supported on-premises continuation: it is technically equivalent to a refreshed 2019 with a subscription licensing model layered on top. In-place upgrade from 2019 CU14 to SE is supported and is the recommended path for estates that want to keep mail on-prem. For estates that want to retire on-prem Exchange entirely, the cutover migration to Exchange Online (as part of Microsoft 365 or Office 365) is the alternative path and the one most organisations are choosing.

04

Hybrid Exchange and the migration mechanics

Hybrid Exchange — a configuration where Exchange Online and Exchange Server share an SMTP domain, address book and free/busy lookups — is the staple migration tool. The Hybrid Configuration Wizard automates the trust setup, certificate provisioning and connector configuration. Mailbox moves are non-disruptive to end users: Outlook reconfigures itself, OWA redirects transparently. Once all mailboxes are in Exchange Online, the on-prem Exchange organisation can be decommissioned, with the historical caveat that until 2024 a single on-prem Exchange Management server was still required for Entra ID Connect attribute writeback — a requirement Microsoft has now lifted via the Exchange Modern Hybrid configuration with cloud-based management tools.

05

Operational reality through extended support

Running Exchange 2019 in extended support means receiving security-only updates through October 2025 (already past for most cohorts) — no protocol additions, no Office 365 connector compatibility work, no fixes for cosmetic or performance issues. Security advisories continue to be issued and patches continue to ship for vulnerabilities rated Critical, but anything else is on the customer to mitigate or wait out. For organisations that have not started a migration, the realistic options at this point are: bite the bullet and migrate to Exchange Online, in-place upgrade to Exchange Server SE and adopt the subscription model on-prem, or accept the documented risk of running an unpatched mail server.

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 2019

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

Is Exchange 2019 still supported?+
Extended support ran through 14 October 2025 with security updates only. After that date, Exchange Server SE or Exchange Online are the supported destinations.
Can I upgrade Exchange 2019 to SE in place?+
Yes. The supported path is to bring 2019 to CU14, then in-place upgrade to SE. The architecture is preserved; only the licensing model changes.
Do all users need Enterprise CALs?+
No — only users that actually use Enterprise CAL features (UM, advanced compliance, per-user journaling). Most production estates pair Standard CALs broadly with targeted Enterprise CAL add-ons.
Do I still need an on-prem Exchange for Entra ID Connect attribute writeback?+
Microsoft has lifted that requirement via Modern Hybrid management tools. New Exchange Online migrations can fully decommission on-prem Exchange.
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. Anyone offering a 'cheap OEM key' as a standalone download is, by definition, operating outside Microsoft's distribution terms.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail FPP), verify edition alignment (features used must match the licensed edition), and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Small variances usually resolve with a true-up; large gaps escalate to Software Asset Management engagements and back-billing at list price.
Related

Other products in this category