Microsoft Exchange Server: What to Do After 2016/2019 Support Ends

Exchange Server 2016 and 2019 reached the end of support on October 14, 2025. Microsoft did not release a product named “Exchange Server 2025”: its supported on-premises successor is Exchange Server Subscription Edition (SE), introduced in July 2025. Those distinctions matter when planning a secure and supportable email environment.

What changed in October 2025?

Microsoft ended regular technical support, feature and bug fixes, and standard security servicing for Exchange Server 2016 and 2019 on October 14, 2025. Running an older server does not mean mail immediately stops flowing. It means the organization carries increased operational and security risk and should plan a supported destination rather than relying on a legacy deployment indefinitely. Check Microsoft’s current servicing guidance for any exceptional updates; do not assume they extend the product lifecycle.

For related Microsoft credential planning, see the Microsoft certification roadmap. Exchange migration work especially benefits from identity, messaging administration, and security fundamentals.

Which migration destination makes sense?

Exchange Online

Moving mailboxes to Exchange Online reduces responsibility for maintaining the Exchange server operating system and patching the mail platform. It does not eliminate the need for strong identity controls, multifactor authentication, access review, retention configuration, and ongoing administration. Assess licensing, data residency, application integrations, compliance obligations, and network connectivity before committing.

Exchange Server Subscription Edition (SE)

Organizations that must retain an on-premises Exchange environment should evaluate Exchange Server SE. It is a separate successor with ongoing servicing and subscription-related licensing requirements, not “Exchange Server 2025” or a perpetual-license refresh of Exchange 2019. Validate the supported Exchange build, Windows Server versions, Active Directory prerequisites, coexistence restrictions, and the documented upgrade or migration path before making changes.

Hybrid Exchange

A hybrid design can allow staged mailbox migration and coexistence where the environment meets Microsoft’s requirements. It also increases the number of identities, mail-flow routes, certificates, connectors, and administrative components that must be monitored. Keep hybrid only where its ongoing business value justifies its complexity.

How to plan the transition

  1. Inventory: Record Exchange builds, servers, mailbox counts and sizes, shared mailboxes, public folders, mail-flow connectors, transport rules, certificates, backup dependencies, and applications sending SMTP mail.
  2. Choose the destination: Compare Exchange Online, Exchange SE, and hybrid against security, operating cost, compliance, user experience, and required integrations.
  3. Validate prerequisites: Check current Microsoft documentation for supported operating systems, Active Directory, deployment topology, licensing, and coexistence. Do not rely on an old generic migration checklist.
  4. Pilot: Test a representative set of users and service accounts. Check Outlook connectivity, mobile devices, delegated access, shared mailboxes, calendar permissions, mail flow, and recovery procedures.
  5. Protect continuity: Establish rollback criteria, verified backups, cutover windows, user communications, and a staffed support plan.
  6. Decommission carefully: After cutover, confirm there are no dependent relays, applications, or hybrid functions before removing legacy servers. Follow the supported decommissioning procedure.

Common mistakes to avoid

Do not confuse a marketing year with a Microsoft product name, assume the latest version supports an in-place upgrade from any older build, or interpret the end-of-support date as a guaranteed date when all functionality ceases. Equally, do not assume that moving to the cloud automatically satisfies regulatory requirements. Each deployment needs documented decisions and validation.

Bottom line

For Exchange Server 2016 or 2019, the practical decision is no longer whether support will end: it ended on October 14, 2025. Choose a supported target, verify Microsoft’s current prerequisites, test application and mailbox dependencies, and execute a controlled migration.

Official documentation: Microsoft’s end-of-support roadmap and Exchange supportability matrix.

  • img