Send & Receive Issues

Fix Exchange Online 550 5.4.1 Access Denied Error Through Barracuda

Rana GarciaRana Garcia Oct 29, 2026 868 views

Question details

IT administrators are experiencing rejected inbound messages with a 550 5.4.1 Access denied non-delivery report (NDR) when routing emails through Barracuda to Exchange Online.

How to Fix Exchange Online 550 5.4.1 Access Denied Through Barracuda
Product
Exchange Online
Device & OS
not provided
Scenario
Routing inbound messages via a third-party filtering service (Barracuda) after removing an on-premises Exchange server.
Observed behavior
Exchange Online rejects the inbound messages with a 550 5.4.1 Access denied error due to connector misconfigurations, TLS issues, or missing recipient records.
Before you start

Ensure you have administrative access to both the Exchange Admin Center (EAC) and the Barracuda Email Security Gateway console to verify IP ranges and mail flow connector settings.

Solution 1Recommended

Reconfigure Exchange Online Inbound Connectors

Ensure that Exchange Online correctly identifies incoming traffic from Barracuda by validating the partner organization connector settings and IP addresses.

When using a third-party spam filtering service like Barracuda, Office 365 requires an inbound connector to trust the incoming mail flow. If the IP addresses or TLS settings are incorrect, Exchange will drop the connection.

1
Access Exchange Admin Center

Sign in to the Microsoft 365 Admin Center with administrator credentials and open the Exchange Admin Center.

2
Navigate to Connectors

Go to the 'Mail flow' section in the left navigation menu and select 'Connectors'.

3
Edit the Inbound Connector

Select the inbound connector created for your partner organization (Barracuda) and click 'Edit'.

4
Verify IP Addresses

Ensure that the IP addresses listed in the connector exactly match Barracuda's official public IP ranges for your region.

5
Check TLS Requirements

Verify the TLS settings to ensure they meet the security requirements for the incoming connection and save your changes.

Reconfigure Exchange Online Inbound Connectors
Configuration Updated: Connector updates in Exchange Online may take up to an hour to fully propagate across all Microsoft 365 servers.
Free Microsoft Office alternative

Looking for a Reliable and Free Alternative to Microsoft Office?

Managing complex Exchange environments and Office 365 licensing can be challenging and costly. If your team needs a robust, lightweight, and cost-effective productivity suite, WPS Office provides excellent capabilities without the high subscription fees.

  1. 1. Visit the WPS Website: Go to the official WPS Office website to find the latest version for your operating system.
  2. 2. Download the Installer: Click the 'Free Download' button to get the lightweight installation file.
  3. 3. Install and Launch: Run the installer, follow the simple on-screen instructions, and start using your new productivity suite immediately.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation that runs smoothly across Windows, Mac, Linux, iOS, and Android.Includes powerful built-in PDF editing tools for seamless document management.Familiar user interface ensuring easy adoption for your entire organization.
microsoft office alternative - wps office

Frequently Asked Questions

What does the 550 5.4.1 Access Denied error mean in Exchange Online?

This error typically means that the destination email server (Exchange Online) rejected the message because it does not recognize the recipient domain as valid, or the inbound connector configuration is blocking the IP address of the sending service (like Barracuda).

Why does this error occur after removing my on-premises Exchange server?

Removing an on-premises Exchange server changes how mail is routed. If your Office 365 accepted domain is still configured as 'Internal Relay' instead of 'Authoritative,' Exchange Online may fail to resolve the recipient addresses, resulting in an access denied error.

Where can I find the correct IP ranges for Barracuda email filtering?

You can find the required public IP address ranges on the official Barracuda Networks support documentation. These ranges must be explicitly added to your inbound connector in the Exchange Admin Center to allow mail flow.

How do I run a message trace to investigate this issue?

In the Exchange Admin Center, navigate to Mail flow > Message trace. Enter the sender and recipient details, run the trace, and review the detailed delivery status to pinpoint exactly where the connection is being dropped.