Fix Office 365 SMTP Error 550 5.7.708 from an AWS IP
Question details
An AWS-hosted application needs to send email through Office 365 without an IP-based SMTP rejection.

- Product
- Microsoft 365 Exchange Online SMTP
- Device & OS
- not provided
- Scenario
- An application hosted on AWS sends email through Office 365.
- Observed behavior
- The SMTP server returns error 550 5.7.708, stating that traffic from the sending IP is not accepted.
Copy the full SMTP error and identify the public IP address used by the application, including any NAT gateway or mail relay. Check that the application's messages are legitimate and that the sending system has not been compromised.
Request a review of the blocked sending IP
Use Microsoft's delisting process when the AWS sending IP is blocked from sending to Microsoft-hosted email.
In the AWS console, check the application's outbound route, NAT gateway, or mail relay to identify the public IP shown in the SMTP error.
Review the application's mail logs and AWS security settings for unexpected volume, compromised credentials, or abusive messages. Stop any unauthorized sending before requesting a review.
Open Microsoft's sender delisting portal at sender.office.com, enter an email address and the affected public IP, and follow the verification and submission instructions.
Allow up to 24 hours for the review, then send a test message from the application and check the SMTP response. A completed request does not guarantee that every Microsoft 365 restriction has been removed.

Contact Microsoft support if the SMTP rejection continues
Use this option if delisting is not applicable or the error persists after the request is completed.
Use WPS Office for documents while Microsoft reviews the SMTP issue
WPS Office is a free, lightweight alternative for everyday document work. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files, though it does not resolve Exchange Online SMTP blocks.

Frequently Asked Questions
What does SMTP error 550 5.7.708 mean?
In this case, Microsoft is rejecting traffic from the application's sending IP. The IP may have been identified as a potential threat, so check its sending activity and request a review.
How do I find the AWS IP to submit for review?
Check the SMTP error and the application's outbound route in the AWS console. If traffic passes through a NAT gateway or mail relay, use the public IP that actually sends the SMTP connection.
How long should I wait after submitting a delisting request?
Allow up to 24 hours for review, then send a test message and check the SMTP response. If the rejection continues, provide the request details to Microsoft support.
What if the IP was already delisted but the error remains?
Collect the full error, sending IP, recent failure time, and delisting details. In the Microsoft 365 admin center, open Help & support and request an investigation.
Can the AWS IP be blocked again?
Yes. If the IP continues to send abusive or unauthorized traffic, it may be blocked again. Review application mail logs and secure any compromised sending credentials.




