Exchange 2016 Mail Flow is Not Working

After restoring an Exchange 2016 server from a 2025 backup, the server’s configuration may no longer match the current hybrid environment. Hybrid mail flow depends on connectors, certificates, DNS records, and transport settings that must line up with Exchange Online.

Even if port 25 and DNS resolve correctly, the following issues are typical after a rollback:

• The server may be using outdated connectors that no longer match Exchange Online security requirements.
• The TLS certificate used by the Send Connector may be expired or incorrect.
• The Hybrid Configuration wizard must be re-run because the original configuration stored in AD may no longer match the restored server.
• Autodiscover and internal/external URLs may be inconsistent with current hybrid settings.
• Transport Services may be running with stale configuration until the server is re-registered with the hybrid tenant.

The first step is to re-run the Hybrid Configuration Wizard to re-establish connectors, certificates, and transport settings. After that, verify the accepted domains, Send/Receive connectors, TLS certificate assignment, and the server’s Service Connection Point.

Restoring an Exchange server from an old backup often breaks hybrid mail flow because the restored state is no longer trusted by Exchange Online. Reapplying the hybrid config normally fixes the issue.