Exchange Server 2016 · 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.
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.
On this page
Editions covered
—
Edition matrix with feature differences and the right audience.
In-depth sections
3
Channels, activation, audit, modern management & more.
FAQs answered
4
Common questions buyers and IT admins ask before purchase.
Words of reference
0.2k
Edition and deployment guidance; verify current rights against official sources.
Deep dive
Exchange Server 2016 — what to actually know
Exchange Server 2016 shipped in October 2015, consolidating the Client Access and Mailbox roles introduced in 2013 into a single Mailbox role, and bringing MAPI/HTTP as the default protocol for Outlook. It reached end of extended support on 14 October 2025 alongside Exchange 2019 — the entire on-premises Exchange line is now succeeded by Exchange Server Subscription Edition (SE), which is the only on-premises Exchange still receiving security updates.
01
Editions
Standard (up to 5 mailbox databases per server — sufficient for small and mid-size deployments) and Enterprise (up to 100 mailbox databases — required for large estates and for hosting more than five public folder databases). Both editions share the same feature set; the difference is purely the database count limit.
02
Licensing
Server licence (Standard or Enterprise) plus a CAL for every user or device. CALs come in two flavours: Standard CAL (basic mailbox access, ActiveSync, OWA) and Enterprise CAL (adds in-place hold, advanced compliance, data loss prevention, journaling, integrated archiving). Enterprise CAL is additive — you buy a Standard CAL and add an Enterprise CAL on top, you do not buy Enterprise CAL alone.
03
End-of-life and migration
Mainstream support ended October 2020; extended support ended 14 October 2025. After that date, no security patches. Migration paths: Exchange Online (Microsoft 365), Exchange Server Subscription Edition (the new on-premises evergreen line), or a hybrid deployment with mailbox moves to Exchange Online over time. Running Exchange 2016 in production after October 2025 with internet-exposed mail flow is a documented and serious security risk.
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.
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 2016; 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 2016 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.
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 2016
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.
Only with security updates. Mainstream support ended 13 October 2020; extended support (security updates only) continues until 14 October 2025. Plan the upgrade before that date — after it, the only path to patches is a paid Extended Security Updates (ESU) programme where Microsoft offers one.
What replaces Exchange 2016/2019 on-premises?+
Exchange Server Subscription Edition (SE), which shipped in mid-2025. SE is licensed per server + CAL with Software Assurance, follows a Modern Lifecycle (continuous updates rather than five-year versions), and is the only on-premises Exchange currently in support.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel (where the SKU is still sold), 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. For end-of-sale products, second-user (transferred) Volume Licensing through a documented chain of custody is the only legitimate secondary market.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail packaging), verify edition alignment, and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Older products are audited the same way as current ones — being out of mainstream support does not waive the licensing obligation.