فا
MSLicenseHub
collaboration · reference
📨

Exchange Server 2019

Exchange Server 2019 — out of support since 14 October 2025: per-server licensing, CALs, and the upgrade path to Exchange Server SE or Exchange Online.

Before licensing Exchange Server 2019

01Server02Internal access03Edition features
Exchange Server 2019 · licensing decision diagram, not a product screenshot

Check each installed server and the internal user/device access rights. Enterprise CAL features can require an additive CAL rather than replacing Standard. External-user exceptions and Subscription Edition requirements differ by product.

Confirm against official Microsoft sources

Licensing terms and guides · Product lifecycle directory

Record the exact edition, version, quantity, agreement and support date. Obtain written confirmation of delivery, refund and support terms; a perpetual licence is not a lifetime support guarantee.

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
Edition and deployment guidance; verify current rights against official sources.
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 advanced compliance and per-user journaling.

Side-by-side

Edition comparison

Compare the stated edition details. An omitted capability is not evidence that a feature is unavailable; verify the exact release in Microsoft's documentation.

CapabilityStandardEnterpriseStandard CALEnterprise CAL
Edition and licensing notesPer-server. Up to 5 mailbox databases.Per-server. Up to 100 mailbox databases. Same feature set otherwise.Per user or device. Core mailbox features.Add-on to Standard CAL. Adds advanced compliance and per-user journaling.
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; mainstream support ended in January 2024 and extended support ended on 14 October 2025, so it no longer receives security updates. 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 run a hybrid only as a short, risk-accepted migration step.

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 advanced compliance (in-place hold, in-place eDiscovery, Data Loss Prevention) and per-user journaling. Unified Messaging was removed in Exchange Server 2019. 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 ended on 14 October 2025. CU15 was its final cumulative update, and no further security updates are released. 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 or CU15 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 after end of support

Since 14 October 2025, Exchange 2019 receives no security updates, protocol additions, Exchange Online connector compatibility work or bug fixes. New vulnerabilities stay unpatched and must be mitigated by the customer. 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

Confirm that the exact SKU is available in the proposed channel and region. A channel name does not establish entitlement or guarantee a lower price.

Evidence to request

  • Exact product, edition, version and licence quantity.
  • Order, invoice and applicable agreement or subscription record.
  • Ownership in your organisation's account, where applicable.
  • Written reassignment, renewal and support conditions.

OEM is supplied only pre-installed by hardware manufacturers, never sold as a standalone licence.

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
Exact product
Identify

Record the release, edition and servicing channel of Exchange Server 2019; family names alone do not establish support dates.

Phase 2
Official lifecycle
Verify

Look up the exact product in Microsoft's lifecycle directory. Fixed and Modern Lifecycle policies differ; not every release has extended support.

Phase 3
Deployment
Plan

Confirm supported operating systems, application dependencies and upgrade rights before deployment.

Phase 4
End of support
Migrate

A perpetual licence can remain valid after support ends, but it does not guarantee security updates. Check any ESU programme separately.

Purchase preparation

What to include in a Exchange Server 2019 quote request

Product
Exact version, edition and current agreement.
Servers
Number of installed servers and underlying infrastructure.
Access rights
Internal and external users or devices, and required features.
Migration
Support status, upgrade destination and subscription requirements.

These are planning inputs, not a licence calculation. Confirm the final quantity and use rights against the exact version and agreement.

Compare like-for-like quotations
  • Match product, edition, version, quantity and perpetual or subscription terms.
  • Confirm total cost, renewal conditions and the evidence of ownership supplied.
  • Obtain written delivery, refund and support conditions before payment.
Official product licensing guide
Request a quote
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

Check the product-specific server licences and internal user/device CALs.

DON'T

Assume one external-access rule applies to all products: SharePoint has qualifying external-user CAL exceptions; Windows Server access must be checked separately.

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

Illustrative planning scenarios, not customer case studies. Check the exact product rights and deployment requirements.

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

Compare entitlement, deployment and renewal costs; savings depend on your workload and written quotation.

💰
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 warning signs require further verification; activation alone cannot establish licence ownership.

⚠ 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 not an eligible standalone purchase; request documented rights through an appropriate channel.

⚠ 02
Lifetime key with no invoice or Microsoft 365 admin center volume licensing record

Request applicable order and agreement records, such as Microsoft Store purchases, CSP subscription records or volume licensing details in the Microsoft 365 admin center. Activation alone is not proof of entitlement.

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

Activation failures can have several causes, including key eligibility, activation counts, connectivity and hardware changes. Check the error through official Microsoft guidance; it does not by itself prove counterfeiting.

⚠ 04
Seller refuses to put the entitlement in your tenant

For tenant-based subscriptions, confirm your organisation controls the tenant and can read its subscription records. Retail and on-premises entitlements use different records; not every licence is assigned through a tenant.

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.

Microsoft 365 admin center volume licensing

Volume licensing administration — agreements, keys and downloads are now managed in the Microsoft 365 admin center.

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?+
No. Extended support ended on 14 October 2025, so Exchange 2019 receives no security updates. 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 or CU15, 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 (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

✉️
Exchange Server Subscription Edition (SE)

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

Read reference →
📂
SharePoint Server Subscription Edition (SE)

SharePoint Server SE — the current on-premises SharePoint, with rolling feature updates and Server + CAL licensing.

Read reference →
🗂️
SharePoint Server 2019

SharePoint Server 2019 — Standard and Enterprise CALs, per-server licensing, SE upgrade path and end-of-support reality.

Read reference →