On-Prem Exchange SE or Microsoft 365: Choosing Where Your Email Lives

Fix it now

Exchange 2016 and 2019 reached end of support on 14 October 2025, so the on-premises choice is now Exchange Server SE – and SE is not a perpetual purchase. It needs an active qualifying entitlement, either Software Assurance on existing Exchange Server licences or a qualifying Microsoft 365 subscription, plus a CAL for every user or device.

1. Answer the operational question first: can somebody apply an Exchange security update within days, every time, including in August? If not, on-premises is the wrong answer regardless of the licensing comparison.
2. Keep it in-house only where a written regulatory or contractual clause demands it, where connectivity genuinely cannot carry the traffic, or where a system you cannot change needs a local Exchange.
3. Count the whole footprint, not the Exchange licence: Windows Server core licences at 8 per processor and 16 per server, Windows Server CALs, Exchange Standard CALs, Outlook, antivirus, backup, a second server for availability, and the person who patches it.
4. Size by databases, not users. Exchange Server SE Standard supports 1 to 5 mailbox databases and Enterprise supports 1 to 100; that cap, not headcount, forces the edition.
5. Do not budget for a free hybrid licence. Microsoft states the free Exchange Server licence issued by the Hybrid Configuration Wizard is not available for Exchange 2019 or later hybrid servers.
6. If the only reason you keep a server is recipient management, look at transferring the Exchange attribute Source of Authority to the cloud before you buy hardware for it.

Exchange 2019 servers can be upgraded in place to Exchange Server SE. Exchange 2016 servers cannot: they join an Exchange SE server and are then migrated, which is a project rather than an upgrade.

If nobody owns Exchange patching with a service level you would write down, the answer is Microsoft 365 and you can stop here. Below is the full footprint, the database limits that force an edition, and the documented route to removing the last server.

Why it happens

Where email lives is not primarily a cost decision, although it is usually presented as one. It is a decision about who patches an internet-facing mail server, who is accountable when it is unavailable at nine on a Monday, and whether anything in your contracts or regulations genuinely requires the data to sit on hardware you own. Answer those three honestly and the licensing arithmetic tends to follow rather than lead.

What changed is the shape of the on-premises option rather than its existence. Exchange 2016 and Exchange 2019 reached end of support on 14 October 2025, and Exchange Server Subscription Edition is the continuing product. It carries the same codebase, so databases, availability groups, transport rules and the administrative tooling behave as an Exchange administrator expects. The licensing moved though: Microsoft requires customers to maintain an active qualifying entitlement to install, run and stay current with Exchange Server SE – either active Software Assurance on existing Exchange Server Standard or Enterprise licences, or a qualifying Microsoft 365 subscription.

The edition question is about databases rather than people, and the figures are published. Exchange Server SE Standard Edition is described for the mailbox needs of small to midsize organisations and supports 1 to 5 mailbox databases. Enterprise Edition supports 1 to 100. On the client side, each accessing user or device needs a Standard CAL, and the Enterprise CAL is sold as an add-on – to enable Enterprise CAL features the user must be licensed with one Standard CAL plus one Enterprise CAL.

Full reference

The two options with the whole footprint on the page

The line most often missing from the comparison

Exchange does not run on nothing. Underneath it sits Windows Server, licensed by physical core with a minimum of 8 core licences per physical processor and 16 per server, plus a Windows Server CAL for every user or device that accesses it. That is a separate purchase from the Exchange server licence and a separate purchase from the Exchange CALs, and it is the line that most often turns a favourable-looking on-premises comparison around. Add Outlook, which comes from a Microsoft 365 seat or a perpetual Office licence and is a separate line whichever platform you choose.

Then add the second server. One Exchange server is a single point of failure for the whole company’s communication, so a serious on-premises design has a database availability group, which doubles the Windows Server licensing and the hardware. Add backup, add filtering, add the hardware refresh cycle, and add the staff time. Put that total against the per-seat figure over the same period, and only then compare.

Upgrading, and what you can and cannot do in place

Exchange 2019 servers can be upgraded directly in place to Exchange Server SE. Exchange 2016 servers cannot: the documented route is that an Exchange 2016 server joins an Exchange SE server, and is then upgraded or migrated. Treat those two as different projects with different budgets, because they are.

There is also the hybrid case that keeps organisations on-premises without anybody deciding to. If mailboxes have moved to Microsoft 365 but Microsoft Entra Connect is still used to manage on-premises Active Directory users, Microsoft’s guidance has been that at least one Exchange server must be retained, and that it should be upgraded to Exchange Server SE.

The documented route to removing the last server

That guidance now has an alternative worth checking before any hardware refresh. Exchange Online allows administrators to manage Exchange attributes for directory-synchronised users whose mailboxes are hosted in the cloud, by transferring the Source of Authority for Exchange-specific attributes to the cloud while identity attributes remain under the control of on-premises Active Directory. It needs Microsoft Entra Connect Sync version 2.5.190.0 or higher, and the role of Exchange Administrator, Hybrid Identity Administrator or Global Administrator.

(Get-ADSyncGlobalSettings).Parameters['Microsoft.Synchronize.ServerConfigurationVersion']
Set-Mailbox -Identity <user> -IsExchangeCloudManaged $true
Set-OrganizationConfig -ExchangeAttributesCloudManagedByDefault

Read the limits before planning around it. Exchange-attribute Source of Authority transfer applies only to user objects with mailboxes in Exchange Online; mail-enabled groups and mail contacts use Group or Contact SOA transfer instead. First name and last name still require on-premises Active Directory. Allow the usual sync cycle plus 24 hours before switching a user’s Exchange attributes to cloud managed.

Do not budget for a free hybrid licence on a current release. Microsoft’s Hybrid Configuration Wizard FAQ states that the HCW can detect and licence Exchange 2010 SP3, Exchange 2013 or Exchange 2016 hybrid servers for free, and that the free Exchange Server licence is not available for Exchange 2019 or later hybrid servers. Microsoft’s Exchange licensing FAQ separately says that servers not hosting mailboxes and used only to connect to Microsoft 365 can be licensed through the wizard, for recipient management only. The two statements are not reconciled on any Microsoft page, so confirm your hybrid entitlement in writing before you assume it costs nothing.

Which to choose, by situation

• Fewer than fifty people with no written residency requirement: Exchange Online inside a Microsoft 365 Business plan.
• Regulated data with a residency clause: read the clause first. Regional data commitments satisfy a great many of them without owning hardware.
• Poor or expensively metered connectivity: on-premises, and budget the second server. One Exchange server is a single point of failure for the whole company.
• No in-house Exchange skills: cloud, or a managed provider. Exchange is not a part-time responsibility, and the patching cadence is the reason.
• Already hybrid with all mailboxes in the cloud: check the Exchange attribute Source of Authority transfer before renewing the last server’s hardware.
• An application that only needs to send mail: an SMTP relay, not an Exchange deployment.

Questions people ask about this