Exchange Server Subscription Edition in 2026: Servicing, Security, and an Actionable Upgrade Path

Exchange 2025

Microsoft’s Exchange Server SE reached GA on July 1, 2025. In 2026, the Modern Lifecycle model means only the current CU is supported; security capabilities continue to evolve (TLS 1.3, updated auth patterns). Here’s how to stay compliant and avoid outages.

Why Exchange SE matters

  • GA + Modern Lifecycle: No fixed end date, but you must stay on the latest CU; SE RTM installs as a CU on Exchange 2019 CU14/15 with supported coexistence. 
  • 2026 outlook: CU cadence focuses on platform modernization, including Kerberos‑based server‑to‑server authentication improvements; the legacy N‑1 rule does not apply anymore. 

Licensing & support reality

  • Subscription licensing replaces perpetual; Exchange 2016/2019 support ended Oct 14, 2025 (ESUs only for limited cases). Staying on‑prem requires moving to SE. 
  • Platform: Exchange 2019 CU15 added TLS 1.3 and re‑introduced certificate management; Windows Server 2025 is supported in this trajectory. 

Operations & security

  • Keep CU current to remain supported and secure—especially critical for hybrid orgs.
  • Clean‑up of legacy components (UCMA, legacy IM) simplifies the footprint and reduces attack surface.

Three‑step action plan 

  1. Assess: builds, certificates, transport paths (mTLS), load balancer health, 3rd‑party agents. (Reason: TLS 1.3 & CU pipeline) 
  2. Pilot SE on Windows Server 2025: validate hybrid, adjust probes/monitoring, document rollback. 
  3. Institutionalize CU‑cadence: quarterly windows, smoke tests, regression list. (Modern Lifecycle)
Back