Exchange Connection Problems

Fix Exchange Online Connector Validation for an On-Premises Edge Server

John WilsonJohn Wilson Nov 20, 2026 869 views

Question details

Resolve a test recipient error when validating an Exchange Online connector to an on-premises Edge server.

Fix Exchange Online Connector Validation for an On-Premises Edge Server
Product
Microsoft Exchange Online and Exchange Server Edge Transport
Device & OS
not provided
Scenario
Validate outbound mail flow from Exchange Online to an on-premises Edge server for domains without public MX records.
Observed behavior
The connector reaches the Edge server over TLS, but validation fails because the test recipient cannot be resolved.
Before you start

Identify a working test mailbox hosted in the on-premises environment and the connector's configured smart host or MX routing method. Have access to the Exchange admin center and the Edge server's mail-flow logs.

Solution 1Recommended

Check the Test Recipient and Edge Server Mail Flow

Use the validation error and server logs to determine why the recipient cannot be resolved after the TLS connection succeeds.

1
Review the validation result

In the Exchange admin center, open Mail flow > Connectors, select the outbound connector, and review the validation result and detailed error for the test message.

2
Verify the test address

Check the recipient in the on-premises Exchange admin center or directory. Confirm that the address is correct, the mailbox can receive mail, and the domain is configured for the intended mail-flow route.

3
Check the Edge server

On the Edge server, verify that Exchange Edge Transport or the intended SMTP service is running. Review SMTP protocol and message-tracking logs for the validation attempt and any recipient rejection.

4
Check recipient routing

If the Edge server uses recipient filtering or EdgeSync, review its accepted-domain and recipient configuration. Correct any missing or stale recipient information indicated by the logs.

5
Validate again

Return to Mail flow > Connectors in the Exchange admin center and run validation with the verified on-premises recipient. Use the new error details to investigate any remaining failure.

Check the Test Recipient and Edge Server Mail Flow
TLS success is only one check: A successful TLS connection confirms that the servers can establish a secure connection; it does not confirm that the recipient exists or that the message can be delivered.
Free Microsoft Office alternative

Work With Office Documents in WPS Office

WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files. It does not replace or repair an Exchange Online connector.

Use a free, lightweight office suite with a familiar interfaceOpen and edit Microsoft Word, Excel, and PowerPoint formatsContinue working with office files while an Exchange administrator resolves mail-flow issues
microsoft office alternative - wps office

Frequently Asked Questions

Does a missing public MX record always cause connector validation to fail?

No. An outbound connector that uses a smart host can route through that host without using the recipient domain's MX record. Check the routing method under Mail flow > Connectors in the Exchange admin center.

Which address should I use for connector validation?

Use a known working recipient hosted in the on-premises environment and covered by the intended connector route. Verify the address and mailbox in the on-premises Exchange admin center or directory before testing.

Why can validation fail after TLS succeeds?

TLS confirms the secure connection, but recipient resolution and delivery are separate checks. Review the validation error and the Edge server's SMTP and message-tracking logs for recipient or routing failures.

Can a domain without a public MX record receive Internet mail?

It may not receive mail directly from Internet senders that rely on public MX routing. Review the domain's public DNS and intended inbound mail-flow design before adding or changing an MX record.