Fix Scanner Email Error 550 5.7.51 in Microsoft 365
Question details
A user needs to restore scanner email delivery to internal Microsoft 365 recipients from one office.

- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- A scanner sends email through Exchange Online from multiple offices, but delivery fails from one location.
- Observed behavior
- The affected office receives a 550 5.7.51 TenantInboundAttribution error, while the same scanner configuration works from another office.
Identify the affected office's outbound public IP address and the scanner's SMTP server, port, and authentication settings. Ask an Exchange administrator to review the relevant connector and collect the full SMTP rejection, including its timestamp.
Check the Exchange Online inbound connector
Use this when one office fails while another works, especially if a partner connector identifies senders by IP address or certificate.
From the affected office, check the public IP used for outbound SMTP traffic. Confirm it with the network administrator if the scanner uses a different network route.
In the Exchange admin center, go to Mail flow > Connectors and open the inbound connector used for the scanner's mail flow. Review how it identifies the sending server.
If the connector identifies the sender by IP address, confirm that the affected office's public IP is included in its configured addresses. If it uses a certificate, verify that the sending server presents the expected certificate and that its name matches the connector settings.
Save any authorized changes in the connector, then send a test scan to an internal recipient. Record the result and any complete SMTP error.

Check the sending IP and collect delivery evidence
Use this if the connector settings appear correct or the error continues after an update.
Work with scanned documents in WPS Office
WPS Office is a free, lightweight alternative for working with documents after scanning. Its familiar interface and Microsoft Office format compatibility make migration straightforward. It does not fix Exchange Online connectors or scanner email delivery.

Frequently Asked Questions
Why does the scanner work from one office but not another?
The offices may send through different public IP addresses. In the Exchange admin center, check Mail flow > Connectors to see whether the inbound connector recognizes the affected office's IP or certificate.
How can I get an NDR if the scanner does not produce one?
If the message is rejected during the SMTP session, a separate NDR may not be generated. Check the scanner logs or capture the complete SMTP response from a controlled test and provide it to tenant support.
What if the delist portal says the IP is not blocked?
Review the Exchange Online connector's sender identification and restrictions, then retest. If the rejection continues, open a request through Help & support in the Microsoft 365 admin center and include the full SMTP response.
Why can't I find the failed scan in message trace?
A message rejected during the SMTP conversation may not appear in message trace. Search Mail flow > Message trace using the sender, recipient, and test time, and use the SMTP response as evidence if no result appears.




