Exchange Connection Problems

Choose a Smart Host for an Office 365 Mail Flow Connector

Algirdas JasaitisAlgirdas Jasaitis Nov 13, 2026 869 views

Question details

Determine which fully qualified domain name (FQDN) or IP address to use as the smart host when configuring mail flow between an on-premises organization and Office 365.

Choose a Smart Host for an Office 365 Mail Flow Connector
Product
Microsoft 365 Exchange Online and on-premises Exchange Server
Device & OS
not provided
Scenario
Configure a connector that routes email to the intended receiving or relay server.
Observed behavior
The connector needs a smart-host address that identifies the actual destination server, rather than an automatically selected authoritative Microsoft 365 domain.
Before you start

Confirm the mail-flow direction and obtain the receiving server's FQDN or IP address from your email administrator. Have the appropriate Exchange administrator permissions and check the destination's SMTP reachability and required TLS settings.

Solution 1Recommended

Select the smart host that matches your mail-flow direction

Use this approach to identify the correct destination before entering an address in the connector.

A smart host is a server that receives or relays messages for the configured route. An accepted or authoritative domain identifies an email namespace; it does not automatically identify the server that should receive a connector's traffic.

An Exchange Online outbound connector and an on-premises Exchange Send connector are configured in different places. Choose the destination for the direction you actually need.

1
Identify the sending and receiving systems

Review your mail-flow plan and determine whether messages travel from Microsoft 365 to your on-premises server or from on-premises Exchange to Microsoft 365.

2
Obtain the destination address

For Microsoft 365-to-on-premises delivery, ask your administrator for the externally reachable FQDN or public IP address of the receiving email server or gateway. For on-premises-to-Microsoft 365 delivery, use the tenant-specific Exchange Online Protection endpoint specified by Microsoft's connector guidance, not merely your accepted domain name.

3
Configure the appropriate connector

For Microsoft 365-to-on-premises delivery, open the Exchange admin center, select Mail flow > Connectors, and add or edit a connector from Microsoft 365 to your organization's email server. Choose smart-host routing and enter the destination FQDN or IP address. For an on-premises Exchange Send connector, open the on-premises Exchange admin center, go to Mail flow > Send connectors, and configure the intended connector's smart-host routing.

4
Check security and validate delivery

Set the connector's TLS and certificate requirements according to the receiving system and Microsoft's connector guidance. For an Exchange Online connector, run the validation offered by the connector wizard; then send a test message through the intended route and check delivery.

Select the smart host that matches your mail-flow direction
Hybrid configurations require their own routing settings: If this is an Exchange hybrid deployment, follow the Hybrid Configuration Wizard and Microsoft hybrid guidance. Do not replace wizard-managed routing or TLS settings with a guessed smart-host address.
Free Microsoft Office alternative

Use WPS Office for Mail-Flow Documentation and Checklists

WPS Office does not configure or repair Exchange connectors. For documenting server addresses, routing decisions, and test results, it offers a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for an easy transition of your documents.

Create mail-flow setup instructions and connector validation checklists.Work with Microsoft Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) files.Use familiar document, spreadsheet, and presentation tools in a lightweight suite.Open existing Office documentation without rebuilding your workflow.
microsoft office alternative - wps office

Frequently Asked Questions

Should I use my authoritative Microsoft 365 domain as the smart host?

Not automatically. Use the FQDN or IP address of the server intended to receive or relay messages. An authoritative domain defines where recipient addresses belong, but it may not resolve to the required SMTP destination.

Can I enter more than one smart host?

Yes, supported connector configurations allow multiple smart hosts. In the connector's smart-host routing section, add each intended receiving server and verify that every destination meets the route's connectivity and TLS requirements.

Where do I configure mail delivery from Microsoft 365 to my own server?

In the Exchange Online admin center, go to Mail flow > Connectors and create or edit a connector from Microsoft 365 to your organization's email server. Enter your receiving server or gateway in the smart-host routing settings.

Why does connector validation fail after I enter the smart host?

Check that the entered hostname resolves to the intended server, the SMTP endpoint is reachable, and the receiving server accepts the route. Also compare the connector's TLS and certificate settings with the server's configuration, then rerun validation in Mail flow > Connectors.

Can WPS Office fix an Exchange smart-host connection problem?

No. Configure and troubleshoot smart-host routing in Exchange Online or on-premises Exchange. WPS Office can help maintain setup documents and test-result spreadsheets, but it is not an SMTP relay or Exchange administration tool.