How to license and manage a Hybrid Exchange environment in 2026

Hybrid Exchange is still common in 2026, but the licensing and management choices have changed. If your organization uses Exchange Online with on-premises Active Directory synchronized to Microsoft Entra ID, you may need either a supported Exchange server for hybrid functions or the Exchange Management Tools for recipient management—not an outdated Exchange 2010, 2013, 2016, or 2019 server.

What changed since the original guidance

The most important change is supportability. Exchange Server 2010 and Exchange Server 2013 are no longer supported, and Exchange Server 2016 and Exchange Server 2019 reached end of support on October 14, 2025. In 2026, organizations that still require an on-premises Exchange footprint should plan around Exchange Server Subscription Edition (Exchange SE) and current Microsoft lifecycle guidance. Unsupported Exchange servers should not be used for production hybrid connectivity, recipient management, SMTP relay, or internet-facing services. They should be removed, isolated, or remediated urgently.

Do you still need an on-premises Exchange server?

Not every Microsoft 365 organization needs to keep a full Exchange server. The right answer depends on what still runs on-premises. If all mailboxes are in Exchange Online and your only requirement is to manage Exchange attributes for synchronized users, you may be able to use the supported Exchange Management Tools instead of maintaining a full Exchange server. If you still need mail flow through on-premises systems, centralized transport, application SMTP relay, on-premises public folders, coexistence during a migration, or other hybrid features, you may still need a supported Exchange hybrid server. The decision should be made before you decommission the last Exchange server, because unsupported attribute edits directly in Active Directory can create long-term support and consistency issues.

Hybrid licensing in 2026: what the free hybrid license is—and is not

The Exchange hybrid license is intended for eligible on-premises Exchange servers used only for hybrid purposes, such as hybrid configuration and recipient management, and not for hosting on-premises production mailboxes. If you host mailboxes, public folders, or production workloads on-premises, you need to license Exchange according to Microsoft’s current licensing terms. The Hybrid Configuration Wizard (HCW) has historically been used to validate the Microsoft 365 tenant and apply a hybrid license where eligible. In 2026, you should use the current HCW and Microsoft licensing terms to confirm whether your server and scenario qualify. Microsoft 365 user subscriptions are commonly purchased under the New Commerce Experience (NCE), but Microsoft 365 user licensing does not automatically make every on-premises Exchange deployment free or compliant.

Current supported paths

For new or ongoing on-premises Exchange requirements, use a supported Exchange version and keep it fully patched. Exchange SE is the current on-premises direction. Organizations still running Exchange 2010, 2013, 2016, or 2019 should not treat those versions as a stable hybrid endpoint in 2026. A practical modernization path is: move remaining mailboxes to Exchange Online where possible, remove unsupported Exchange versions, deploy or transition to a supported Exchange SE-based hybrid server if hybrid services are still required, or move to the supported Exchange Management Tools model if no server-side hybrid workloads remain.

When a full hybrid Exchange server is still appropriate

A supported on-premises Exchange server may still be required when you need full coexistence during a migration, hybrid mail flow, centralized mail transport, on-premises SMTP relay for business applications and devices, on-premises public folder coexistence, or specific compliance or routing requirements. It may also be appropriate during staged modernization projects where identity, mail flow, and applications cannot all be moved to Exchange Online at once. In these cases, the hybrid server should be treated as production infrastructure even if it hosts no user mailboxes.

When Exchange Management Tools may be enough

If all mailboxes are in Exchange Online, there are no on-premises public folders, no on-premises mail transport requirements, and no applications requiring Exchange server services, the Exchange Management Tools may be the better long-term model. This lets administrators manage supported Exchange recipient attributes for users synchronized from on-premises Active Directory to Microsoft Entra ID without keeping a full Exchange server online. This approach must be planned carefully, especially if you have legacy connectors, relay dependencies, third-party archiving, or custom provisioning processes.

How to approach Hybrid Configuration Wizard licensing

Use the latest Hybrid Configuration Wizard from Microsoft, run it with appropriate Exchange and Microsoft 365 administrative permissions, and allow it to detect the appropriate on-premises server. If your server and scenario are eligible, HCW may provide the option to license the server for hybrid use. After applying the license, document the server role, the tenant used for validation, the date, and the business reason the server remains in place. Because HCW screens and admin center navigation change over time, validate the current interface during the project rather than relying on old screenshots or legacy Exchange admin center paths.

Security and operational prerequisites

A hybrid Exchange server must be maintained like any other critical identity-adjacent system. Run a supported Exchange version with the latest required updates, security updates, and configuration guidance. Use trusted certificates with correct subject names, enforce modern TLS, restrict firewall exposure to required services, and keep Hybrid Configuration Wizard components current. Review Extended Protection guidance, OAuth and hybrid modern authentication requirements where applicable, connector security, receive connector restrictions, SMTP relay scope, logging, backup, monitoring, and alerting. Do not leave an unpatched Exchange server online simply because it no longer hosts mailboxes.

Recommended 2026 plan for legacy Exchange environments

If your organization still has Exchange 2010, 2013, 2016, or 2019 in a hybrid or management role, create a remediation plan now. Inventory mailboxes, public folders, connectors, certificates, DNS records, Autodiscover, SMTP relay devices, transport rules, third-party integrations, and identity synchronization. Move remaining mailboxes to Exchange Online where appropriate, replace or modernize relay dependencies, remove unsupported Exchange versions, and choose either a supported Exchange SE hybrid server or the Exchange Management Tools model. This reduces security exposure and simplifies Microsoft 365 operations.

Key takeaways

• Exchange 2010 and 2013 are unsupported, and Exchange 2016 and 2019 are no longer supported after October 14, 2025; do not use them as a 2026 production hybrid endpoint.
• Exchange Server Subscription Edition is the current on-premises Exchange direction for organizations that still need a supported server.
• If all mailboxes are in Exchange Online, you may not need a full Exchange server; supported Exchange Management Tools may be sufficient for recipient management in an on-premises Active Directory and Microsoft Entra ID hybrid identity environment.
• A free hybrid license, where available and eligible, is for hybrid-use servers—not for hosting on-premises production mailboxes or avoiding required Exchange licensing.
• Hybrid Exchange servers must be patched, monitored, secured with current TLS and certificate standards, and reviewed for Extended Protection, connector security, and relay exposure.

Need help deciding whether to keep a hybrid server, move to Exchange Management Tools, or complete your Exchange Online migration? IT Partner can assess your Microsoft 365, Exchange, and Microsoft Entra ID environment and build a supported modernization plan.