Exchange Connection Problems

Fix Exchange Online Error 550 5.4.1 Sending to On-Premises Mailboxes

Huma Ashraf ChHuma Ashraf Ch Nov 3, 2026 870 views

Question details

Cloud users in a hybrid environment receive a '550 5.4.1 Recipient address rejected: Access denied' error when sending messages to on-premises mailboxes.

Fix Exchange Online Error 550 5.4.1 When Sending to On-Premises Mailboxes
Product
Exchange Online
Device & OS
not provided
Scenario
Routing emails from cloud to on-premises mailboxes in a hybrid Exchange setup.
Observed behavior
Emails fail to deliver, returning an NDR (Non-Delivery Report) with error code 550 5.4.1 indicating access is denied.
Before you start

Ensure you have Microsoft 365 Exchange administrator privileges, and keep the complete Non-Delivery Report (NDR) handy to verify whether specific users or all recipients are affected.

Solution 1Recommended

Validate Exchange Online Outbound Connectors

Use this solution to ensure that the connector directing mail from Exchange Online to your on-premises server is properly configured and accessible.

In a hybrid environment, Exchange Online relies on an outbound connector to route emails to your on-premises servers. If the smart host IP or FQDN is incorrect, or if the on-premises firewall blocks the connection, the mail cannot be delivered.

1
Access Exchange Admin Center

Log in to the Microsoft 365 Exchange admin center (EAC) using your administrator credentials.

2
Navigate to Connectors

On the left navigation pane, go to 'Mail flow' and click on 'Connectors'.

3
Inspect the Outbound Connector

Select the connector responsible for routing mail from Office 365 to your organization's email server. Click 'Edit' to review the routing configuration.

4
Verify Routing Information

Check that the fully qualified domain name (FQDN) or IP address of the smart host points correctly to an accessible on-premises Exchange server or your email gateway.

5
Run Connector Validation

Click 'Validate this connector', enter a test email address for an on-premises mailbox, and click 'Validate' to confirm the connection works.

Validate Exchange Online Outbound Connectors
Firewall Requirements: Ensure your on-premises firewall allows inbound SMTP traffic (port 25) from Exchange Online Protection (EOP) IP addresses.
Free Microsoft Office alternative

Stay Productive While Resolving Exchange Issues

IT troubleshooting can take time, but your documentation shouldn't be delayed. WPS Office is a high-performing, free alternative to Microsoft Office that ensures you can continue creating and editing your Word, Excel, and PowerPoint files with zero compatibility issues.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installation package for Windows, Mac, or Linux.
  2. 2. Install WPS Office: Run the installer and follow the simple on-screen instructions to set up the suite on your computer.
  3. 3. Open Your Office Files: Launch WPS Office to directly open and edit your existing Microsoft Word, Excel, and PowerPoint files without formatting loss.
Seamless compatibility with Microsoft Office document formats (.docx, .xlsx, .pptx)Familiar, intuitive interface requiring no learning curveLightweight design that runs smoothly on almost any hardwareBuilt-in PDF editor and cloud sync tools for efficient workflows
microsoft office alternative - wps office

Frequently Asked Questions

What does error code 550 5.4.1 mean in Exchange Online?

The 550 5.4.1 error code means 'Recipient address rejected: Access denied'. It typically occurs when Exchange Online Protection (EOP) does not recognize the recipient's email address and the domain is set to Authoritative, or there is a routing misconfiguration.

Why does this error only affect emails sent to on-premises mailboxes?

This happens because Exchange Online handles cloud mailboxes natively, but it must rely on directory synchronization and outbound connectors to route mail to on-premises servers in a hybrid environment. If those components fail, the on-premises routing breaks.

How can I view the detailed Non-Delivery Report (NDR) in Exchange?

You can view the detailed NDR by asking the sender to forward the bounce-back email, or as an administrator, you can run a Message Trace in the Exchange admin center under 'Mail flow' to view detailed routing logs and the specific error code returned by the server.