Others

Fix Exchange Server 2016 Mail Flow Rule Cannot Redirect to Connector

Chanuka GeekiyanageChanuka Geekiyanage Nov 3, 2026 870 views

Question details

The user needs to configure a mail flow rule in Exchange Server 2016 to redirect messages to a specific connector, but the option is missing from the interface.

Exchange Server 2016 Mail Flow Rule Cannot Redirect to a Connector
Product
Microsoft Exchange Server 2016
Device & OS
not provided
Scenario
Setting up transport rules to route specific emails through a dedicated connector in an on-premises environment.
Observed behavior
The 'redirect the message to the following connector' action, commonly found in Exchange Online, is completely absent in the on-premises Exchange 2016 Admin Center.
Before you start

Verify that you have full Exchange Administrator privileges and are accessing the on-premises Exchange Admin Center (EAC), as hybrid deployments can cause confusion between on-premises and online rule options.

Solution 1Recommended

Use Send Connectors and Address Spaces for Routing

Since native on-premises Exchange Server transport rules cannot redirect mail directly to a connector, you must rely on standard Send Connectors scoped to specific address spaces to handle message routing.

In Exchange Online, transport rules allow direct redirection to connectors. In Exchange Server 2016 on-premises, this architectural feature does not exist. Routing must be handled by the categorization engine matching the recipient domain to a Send Connector.

1
Open Exchange Admin Center

Log in to your on-premises Exchange Admin Center (EAC) and navigate to 'Mail flow' in the left-hand menu.

2
Navigate to Send Connectors

Click on the 'Send connectors' tab at the top of the mail flow page to view your existing routing paths.

3
Create or Modify a Connector

Click the '+' icon to create a new Send Connector, select your delivery type (such as Smart Host), and proceed to the 'Address space' section.

4
Define Address Space

Add the specific target domain(s) to the address space list. Exchange will automatically route emails destined for these domains through this connector instead of relying on a transport rule.

Use Send Connectors and Address Spaces for Routing
Sender-Based Routing Limitation: Native Exchange 2016 Send Connectors are based on recipient domains, not senders. If you need strict sender-based routing, you may require third-party transport agents.
Free Microsoft Office alternative

Streamline Your Business Productivity with WPS Office

While you manage complex IT infrastructure like Exchange Server environments, empower your team with a reliable, lightweight, and cost-effective office suite. WPS Office provides exceptional compatibility with standard enterprise file formats without the heavy overhead.

  1. 1. Download the Installer: Visit the WPS Office website and download the enterprise-ready installer for your operating system.
  2. 2. Deploy to Your Endpoints: Run the installation package. WPS Office installs quickly and requires minimal system resources.
  3. 3. Edit Files Seamlessly: Open existing .docx, .xlsx, and .pptx files natively without worrying about formatting or data loss.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight installation reduces endpoint resource consumption.Familiar tabbed interface minimizes employee training time.Built-in PDF editing tools enhance document workflow.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Exchange Online have the 'redirect to connector' option but Exchange 2016 does not?

Exchange Online utilizes a modernized, cloud-native transport architecture designed to handle complex tenant-to-tenant and third-party filtering routes. Exchange 2016 on-premises retains the legacy routing topology where routing is strictly handled by the Active Directory site links and Send Connector address spaces.

Can I use PowerShell to force a transport rule to use a connector in Exchange 2016?

No. The underlying parameter (RouteMessageOutboundConnector) simply does not exist in the on-premises Exchange 2016 schema. Any attempt to force this via the Exchange Management Shell will result in a command error.

How can I achieve sender-based routing in Exchange 2016 on-premises?

Since native Send Connectors evaluate the recipient's address space rather than the sender, you typically need to deploy a third-party Exchange Transport Agent or set up an isolated Exchange server with its own dedicated Send Connector to achieve sender-based routing.