5.4.14 means a message passed through too many hops without reaching a mailbox: it was going around in a loop. Exchange Online stopped it when the hop count limit was exceeded. The loop is almost always a configuration that sends mail back to where it came from.
Most common causes
- Two routing rules or connectors send the same message back to each other
- Hybrid routing points a domain to the wrong side of the environment
- A forwarding or transport rule recreates a path already traversed
- MX or smart-host changes created a circular route
What to verify next
- Use Email Route Visualizer on the complete headers
- Identify repeating hosts or domains in the Received chain
- Compare connectors, transport rules and smart-host destinations
- Break the circular path before resending the message
Read the Received chain
A loop is visible in the headers as the same hosts appearing repeatedly. The Email Route Visualizer orders the Received lines chronologically and highlights repeating hosts, which shows exactly which two systems are passing the message between them.
Typical pairs: an on-premises server and Exchange Online in a hybrid setup, two connectors pointing at each other, a forwarding rule on a mailbox that forwards back into the same organization, or an MX record pointing at a smart host that points back at the MX.
Configurations that create loops
A domain configured as authoritative on both on-premises and cloud sides with routing set to hand unknown recipients to the other side. A transport rule that redirects to an address handled by the same rule. Mailbox forwarding to a contact whose target is another forwarding mailbox. A recent MX change where the old smart host still relays to the new one.
Most loops appear right after a routing change; the change is the first thing to compare.
- Repeating hosts in the Received chain identify the loop.
- Check routing changes made in the last few days.
- Forwarding chains and connector pairs are the usual culprits.
Break the loop
Correct the side that should be authoritative for the recipient, remove the circular forward, or fix the connector or smart-host target. Then resend a test message and trace its route again to confirm it reaches a mailbox in a bounded number of hops.
Loops generate large volumes quickly; clear any backlog of looping messages after the fix so the queue does not repeat the failure.
Best diagnostic path
Mail Failure Doctor
Classify the complete rejection and preserve provider-specific diagnostic context.
Open analysis → Live analysisEmail Route Visualizer
Turn Received headers into an ordered path to expose loops and unexpected intermediaries.
Open analysis → Live analysisEmail Infrastructure Digital Twin
Map the domain’s public mail infrastructure and provider relationships before remediation.
Open analysis →Known limits
- Hosts in the Received chain are self-reported; a misconfigured relay may not name itself clearly.
- The hop limit is Microsoft’s; the loop may involve systems outside your visibility.
Common questions
Why did this start after a migration?
Routing changed and one side still points at the other for the affected domain or recipient. Compare authoritative settings on both sides.
Is this a DNS problem?
Only when an MX or smart-host record points back at a system that relays to it. Usually it is connector or forwarding configuration.
How do I find the exact pair?
Trace the rejected message with the route visualizer; the two repeating hosts are the loop.
Why the exact message matters
The same status family can be triggered by different conditions, and providers frequently add diagnostic text that narrows the issue. Use the complete rejection text rather than treating the numeric code as a complete diagnosis.
Provider reference
For the provider-defined meaning and current requirements, review Microsoft Exchange Online NDR reference.