Why Exchange Online Returns 550 5.7.1 Errors
An Exchange Online 550 5.7.1 error means a message was rejected because a mail system would not allow delivery or relay. The code alone doesn't identify the setting responsible. The rest of the nondelivery report, often called a bounce message or NDR, provides the clues.
For a business, the interruption can affect an invoice, a customer reply, or an automated notification. The full diagnostic response helps your IT administrator find the rejecting system and correct the right setting.
Start by saving the bounce message before anyone changes the mail configuration.
Key Takeaways
A 550 5.7.1 response can come from Exchange Online or another mail server. Common causes include recipient restrictions, mail flow rules, relay configuration, and security policies.
Read the complete NDR, use message trace when Exchange Online handled the message, and make a targeted change. Then test the affected route and any relevant exceptions.
What an Exchange Online 550 5.7.1 Error Means
The 550
response indicates a permanent rejection for that delivery attempt. The enhanced status code 5.7.1
points to a security or authorization issue, but it covers more than one cause.
The rejected message won't be delivered through that attempt. Retrying without correcting the cause will often produce another bounce.
Read Beyond the Error Code
Look for the affected recipient and the text following 550 5.7.1
. A response such as Delivery not authorized
suggests a permissions or policy restriction. Unable to relay
points toward how the message reached the receiving server and whether that server would forward it.
The diagnostic section may also name the server that rejected the message. That matters because a recipient's mail system or a third-party gateway can reject a message sent through Microsoft 365.
Identify the Affected Message
Keep the complete NDR, including its diagnostic details. Record the sender, recipient, subject, sending time and time zone, plus the message ID if one appears. For sensitive business mail, share those details through an approved support channel.
If a message had several recipients, look at the status for each one. A rejection for one address doesn't establish that every recipient failed to receive the message.
Step 1: Trace the Message and Locate the Rejection
An administrator can open the Exchange admin center and select Mail flow > Message trace . Search using the sender, recipient, and approximate time. Open the matching result and review its events, rather than relying only on the final status.
Message trace can show whether Exchange Online received, rejected, deferred, or delivered a message. Event details can also identify a rule or policy involved in processing. If a remote server rejected the message, the response may direct the investigation to the recipient's administrator.
A trace only shows what the Exchange Online tenant handled. If a message remains in Outlook's Outbox and never reached the service, it may not appear there. Our guide to Outlook messages stuck in the Outbox covers that separate problem.
Compare one failed attempt with a successful message when possible. Differences in the sender, recipient, application, or route can narrow the investigation before settings change.
Step 2: Review Recipient Restrictions
When the NDR says delivery isn't authorized, start with the recipient's settings. The recipient organization may intentionally limit who can send to a mailbox, group, or public folder.
Check Mailboxes and Distribution Groups
A distribution group can accept messages only from approved senders or require authenticated senders. For example, a company-wide group may be limited to employees to prevent outside parties from sending to it.
The recipient's administrator should review the group's delivery management settings and compare them with the rejected sender. If an outside partner needs access, add the appropriate sender or adjust the restriction to match the business requirement.
Keep sensitive groups restricted where possible. Allowing every external sender can fix one rejection while exposing the group to unwanted mail.
Check Mail-Enabled Public Folders
Mail-enabled public folders don't accept messages from external senders by default. A diagnostic response can include RESOLVER.RST.AuthRequired; authentication required
, which points toward that restriction.
If the folder should receive external mail, the recipient administrator can change its message delivery restrictions in the Exchange admin center. Microsoft also documents granting the Anonymous user CreateItems
permission through Exchange Online PowerShell.
Allow external submissions only when the folder's purpose requires them. Otherwise, direct the sender to an approved address.
Step 3: Check Sender Permissions and Authentication
The sender's identity matters in two different ways: the account or application must be allowed to submit the message, and the receiving system may evaluate the sending domain's authentication records.
Review Shared Mailbox and Application Access
If an employee sends from a shared address, review the permissions for that mailbox. Full Access lets a user open and manage the mailbox. It doesn't automatically grant the right to send as that address.
Send As makes the message appear to come directly from the shared mailbox. Send on Behalf identifies the employee as sending on its behalf. Grant the permission that matches the role, then retry after the permission change has taken effect.
For a scanner, website, or business application, identify its configured submission method and account. An authentication or permission issue can produce a different response code, so use the actual diagnostic text rather than assuming every sign-in problem is a 550 error.
Examine Domain Authentication When the Response Points There
SPF identifies authorized sending servers for a domain. DKIM adds a signature, while DMARC evaluates alignment with the visible From domain and communicates a policy for failures.
These controls can affect whether receiving systems trust mail, but 550 5.7.1
alone doesn't prove an SPF, DKIM, or DMARC failure. If the rejection mentions authentication or spoofing, investigate the named failure and the actual sending service.
Our Microsoft 365 SPF record checklist can help identify approved senders, including billing platforms and website forms. Avoid changing DNS records based only on the numeric error.
Step 4: Inspect Mail Flow Rules and Policies
Mail flow rules, also called transport rules, can reject messages while they move through Exchange Online. A rule might block external messages to a group, match content in a subject line, or apply a restriction to a department.
In the Exchange admin center, select Mail flow > Rules . Compare the rejected message with each relevant rule's conditions, actions, exceptions, priority, and mode. Lower-numbered priorities run earlier, and an earlier rule can stop later rules from processing the message.
Also review any Microsoft Purview data loss prevention policy or security control identified in the trace. These controls can affect the same message independently of a transport rule.
Before editing a live rule, record its configuration and agree on a rollback. Test both the message that should be allowed and any message the rule should continue to block. Our Exchange Online mail flow rules checklist covers rule scope, ordering, and testing in more detail.
Step 5: Investigate Connectors and Relay
An Unable to relay
response means the receiving system won't forward the message to the requested destination under the conditions it received. This can happen when an application or gateway sends to the wrong endpoint, or when the receiving server doesn't recognize the message as eligible for relay.
Follow the Actual Mail Route
Identify the system that submitted the message and the server named in the rejection. For a scanner, that might be an Exchange Online route; for a hybrid deployment, it could involve an on-premises server or security gateway.
Review the relevant inbound or outbound connector, accepted domains, and routing configuration. Where a connector identifies a sending system by IP address or certificate, compare its configured identity with the system that sent the failed message. Correct the mismatched route or connector rather than allowing unrestricted relay.
Handle the Named Allow List Error Narrowly
Microsoft documents a distinct response: Unable To Relay: Blocked by Customer Allow list
. In that case, the external server IP appears on both an incoming connector and the Connection Filtering IP Allow list.
The documented correction is to remove that IP from the IP Allow list. That action applies to this named scenario, not to every relay rejection. Preserve the existing configuration first, then test the affected route after the change.
Step 6: Review Tenant and Security Restrictions
If several unrelated recipients reject mail from one user or application, investigate controls affecting the sending account or tenant. Depending on the diagnostic details, these can include restricted sending, outbound spam controls, or policies that limit where messages may go.
A restricted account may indicate compromise or unwanted bulk mail. Before restoring sending, investigate the cause, secure the account, and remove any unauthorized forwarding or mailbox rules. Releasing an account without addressing suspicious activity can lead to another block.
Tenant restrictions can also be intentional. For example, an organization may limit certain messages to approved external domains. Compare the rejected message with the policy's purpose, and involve the policy owner before creating an exception.
Test the Fix Without Creating More Problems
After changing a setting, send one controlled test using the same sender, recipient, and route as the failed message. Record the result and review the new trace if delivery still fails.
Test an approved exception as well as a message that should remain blocked. For a rule change, use representative content without exposing customer information. If the original message had multiple recipients, confirm which ones received it before resending to everyone.
Keep the original NDR and a record of the change. If the test fails, those details help the administrator reverse the change and continue the investigation without losing the evidence.
Frequently Asked Questions
Does 550 5.7.1 Mean the Recipient's Address Is Wrong?
Not necessarily. It often indicates an authorization or policy rejection, even when the address exists. The full response may identify a restricted group, a relay problem, or another reason the server refused delivery.
Should We Change SPF or Disable a Mail Flow Rule First?
Neither is a reliable first step without supporting evidence. Start with the NDR and message trace. Change an SPF record or rule only when the diagnostic details and message path point to that control.
Who Needs to Fix the Error?
The answer depends on which system rejected the message. Your administrator can address your tenant's rules, permissions, and connectors. A recipient's administrator must change restrictions or policies in the recipient's organization.
Restore Delivery With a Targeted Fix
A 550 5.7.1 error gives you a starting point, but the diagnostic text tells you where to look next. Use it with message trace to separate recipient restrictions, rule decisions, and relay issues.
A targeted change protects the controls your business needs while restoring the affected message path. Save the evidence, test the correction, and keep a rollback available for future changes.

