Exchange Connection Problems

Fix Exchange Hybrid Migration 451 STARTTLS Error

Bushra ParveenBushra Parveen Oct 23, 2026 868 views

Question details

Users migrating to Microsoft 365 in a hybrid environment can send but not receive emails due to 451 4.4.0 and 451 5.7.3 STARTTLS errors.

Fix Exchange Hybrid Migration 451 STARTTLS Error
Product
Microsoft Exchange Server
Device & OS
not provided
Scenario
Migrating mailboxes to Microsoft 365 in an Exchange Hybrid setup.
Observed behavior
Migrated Microsoft 365 mailboxes fail to receive messages, returning 451 4.4.0 or 451 5.7.3 delivery report errors stating that STARTTLS is required.
Before you start

Ensure you have Exchange Administrator privileges for both your on-premises Exchange Server and your Microsoft 365 environment, and have your third-party SSL certificate details readily available.

Solution 1Recommended

Configure On-Premises Receive Connector and TLS Settings

The most common cause of the 451 STARTTLS error is an improperly configured receive connector or a missing TLS certificate on the on-premises Exchange server.

In an Exchange hybrid environment, secure mail flow relies on mutual TLS authentication between the on-premises Exchange server and Exchange Online. If the on-premises receive connector lacks the correct permissions or certificate bindings, inbound mail from Microsoft 365 will be rejected.

1
Open Exchange Admin Center

Log in to your on-premises Exchange Admin Center (EAC) using your administrator credentials.

2
Navigate to Mail Flow

Go to the 'Mail flow' section from the left navigation pane and select the 'Receive connectors' tab.

3
Check Default Frontend Connector

Select your Default Frontend receive connector and click the edit (pencil) icon to view its properties.

4
Enable TLS

Navigate to the 'Security' tab and ensure that 'Transport Layer Security (TLS)' is checked.

5
Verify Permissions

Under Permission groups, ensure that 'Anonymous users' is checked so that Microsoft 365 can successfully route inbound emails through the connector.

Configure On-Premises Receive Connector and TLS Settings
Check Certificates: Make sure the third-party SSL certificate used for hybrid mail flow is valid, unexpired, and properly assigned to SMTP services on your on-premises server.
Free Microsoft Office alternative

Enhance Your Productivity with WPS Office

While troubleshooting complex Microsoft Exchange hybrid environments, you can rely on WPS Office for a lightweight, fast, and free alternative for all your document needs. It offers seamless compatibility with Microsoft Word, Excel, and PowerPoint without the heavy resource usage.

  1. 1. Visit the WPS Website: Navigate to the official WPS Office website to find the correct download version for your OS.
  2. 2. Download the Installer: Click the free download button and save the setup file to your computer.
  3. 3. Install and Launch: Run the installer, follow the simple on-screen instructions, and launch WPS Office to start working immediately.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Lightweight design that won't slow down your operating system.Free and easy-to-use alternative to heavy Office installations.Built-in PDF editor and comprehensive toolkit for professional workflows.
microsoft office alternative - wps office

Frequently Asked Questions

What does the 451 5.7.3 STARTTLS required error mean?

This error indicates that the sending server requires a secure TLS connection to transmit the email, but the receiving server (usually the on-premises Exchange server) is not properly configured to accept or negotiate the TLS connection.

Why can migrated mailboxes send but not receive emails?

In a hybrid setup, outbound mail might bypass the on-premises server entirely depending on your routing choices. However, inbound mail from on-premises to Microsoft 365 relies on specific connectors. If the receive connector fails TLS authentication, inbound delivery stops.

Do I need a third-party certificate for Exchange hybrid mail flow?

Yes, Microsoft recommends using a valid third-party SSL certificate bound to the SMTP service for secure mail flow. Self-signed certificates are often rejected during hybrid mail flow TLS negotiation between your on-premises Exchange server and Exchange Online.