logo
search
Exchange Connection Problems

How to Fix Exchange Online Mail Loops and Error 554 5.4.14

Maira MehtabMaira Mehtab Sep 22, 2026 869 views

Question details

The user needs to resolve an Exchange Online mail loop issue that triggers error 554 5.4.14, particularly when dealing with disabled accounts or former hybrid setups.

Product
Exchange Online
Device & OS
not provided
Scenario
Emails are bouncing back due to a hop-count-exceeded error caused by misconfigured routing rules, obsolete connectors, or forwarding settings.
Observed behavior
Exchange Online reports a possible mail loop and returns error 554 5.4.14 because the messages exceed the maximum allowed hop count.
Before you start

Ensure you have global administrator or Exchange administrator permissions in the Microsoft 365 admin center before modifying mail flow configurations.

Solution 1Recommended

Verify Mail Flow Settings and Clean Up Obsolete Configurations

Identify and eliminate the root causes of the mail loop by checking accepted domains, connectors, and forwarding rules on disabled accounts.

Mail loops often occur when an email is continuously routed between servers without reaching a final destination. In Exchange Online, this is frequently caused by lingering hybrid configurations, incorrect routing domains, or auto-forwarding on accounts that are no longer active.

1
Verify Accepted Domains

Log in to the Exchange admin center, navigate to Mail flow > Accepted domains, and ensure your domains are correctly configured as Authoritative or Internal Relay.

2
Check Mail Flow Rules

Go to Mail flow > Rules and review your current transport rules. Disable any rules that might inadvertently forward or redirect messages back to the original sender or domain.

3
Inspect Connectors

Navigate to Mail flow > Connectors. Look for any obsolete connectors left over from a former hybrid configuration and delete or disable them if they are no longer in use.

4
Audit Disabled Accounts

Check disabled user accounts for active email forwarding settings or unnecessary SMTP proxy addresses. Remove auto-forwarding configurations that route emails to addresses causing a loop.

Microsoft Guidance: For complex scenarios involving former hybrid setups, consult Microsoft's official documentation on hop-count-exceeded mail loops for detailed PowerShell commands and diagnostics.
Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While you manage complex Exchange server configurations, you can simplify your desktop document workflow with WPS Office. It is a powerful, lightweight, and cost-effective alternative to Microsoft Office.

  1. 1. Download the Installer: Visit the official WPS Office website to download the free installer for your operating system.
  2. 2. Install WPS Office: Run the downloaded file and follow the on-screen instructions to complete the installation in minutes.
  3. 3. Open and Create: Launch WPS Office and immediately start creating, editing, and saving your documents with seamless Microsoft format compatibility.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Lightweight installation that consumes minimal system resources.Free to use with an intuitive, tabbed user interface.Includes a comprehensive built-in PDF toolkit for editing and conversion.
microsoft office alternative - wps office

Frequently Asked Questions

What does the Exchange error 554 5.4.14 indicate?

Error 554 5.4.14 indicates a 'hop count exceeded' issue, meaning an email was routed between servers too many times without being delivered, typically signifying a mail loop.

Why would a disabled account cause a mail loop?

If a disabled account still has active forwarding rules or proxy addresses that point to another address which routes back to the disabled account, it traps incoming emails in an infinite loop.

How do former hybrid configurations contribute to hop-count errors?

When migrating from an on-premises Exchange server to Exchange Online, outdated connectors or routing domains can be left behind. These remnants can mistakenly route mail back and forth between the cloud and the non-existent local server.