Send & Receive Issues

Fix Exchange Online Error 550 5.1.8 After an Account Compromise

Phi Hung VoPhi Hung Vo Nov 20, 2026 868 views

Question details

Restore sending for a previously compromised Microsoft 365 account that receives error 550 5.1.8.

Fix Exchange Online Error 550 5.1.8 After an Account Compromise
Product
Microsoft Exchange Online
Device & OS
not provided
Scenario
A Microsoft 365 user needs to send internal and external email after their account was compromised.
Observed behavior
Messages bounce with error 550 5.1.8, but the account is not listed under Restricted Users and message traces show no suspicious activity.
Before you start

Have a Microsoft 365 administrator review the full non-delivery report, including the diagnostic details and time of the failed message. Confirm that the compromised account has been secured before requesting removal of any sending restriction.

Solution 1Recommended

Check Exchange Online restrictions and request a backend review

Use this approach when a sender receives error 550 5.1.8 but does not appear in the restricted entities list.

A sender may still be subject to an Exchange Online Protection policy or a service-side restriction even when the account is not visible in the restricted entities list.

1
Secure the account

In the Microsoft 365 admin center, open Users > Active users, select the affected user, and reset the password and sign out sessions. Review sign-in activity in the Microsoft Entra admin center and enable multifactor authentication if it is not already required.

2
Check restricted entities

In the Microsoft Defender portal, go to Email & collaboration > Review > Restricted entities and look for the sender. If the account is listed and has been secured, select it and follow the available unblock action.

3
Review message traces and policies

In the Exchange admin center, open Mail flow > Message trace and search for the affected sender and failed message times. Check Mail flow > Rules for relevant transport rules, and review outbound spam policies under Email & collaboration > Policies & rules > Threat policies in the Microsoft Defender portal.

4
Contact Microsoft support

If the account is not listed or sending still fails, open the Microsoft 365 admin center and use Help & support to request a review of any backend sending restriction. Provide the affected address, full bounce details, message times, and trace results through the support case.

Check Exchange Online restrictions and request a backend review
Check for spoofing separately: If messages appear to impersonate your domain, review SPF, DKIM, and DMARC and share relevant message headers privately with support. These controls help address spoofing but do not by themselves remove a sender restriction.
Free Microsoft Office alternative

Work on Office Documents With WPS Office

WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to continue working with existing files. It does not remove Exchange Online sending restrictions.

Open and edit Word, Excel, and PowerPoint files, including DOCX, XLSX, and PPTX formatsUse a familiar interface to move between common office tasksWork on documents while an administrator investigates the email sending restrictionUse a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why do I get error 550 5.1.8 if the account is not listed as restricted?

The sender may still be affected by an outbound policy or a service-side restriction. Review the bounce details and policies, then ask Microsoft support to check for a backend restriction.

Where can an administrator check for a blocked sender?

In the Microsoft Defender portal, go to Email & collaboration > Review > Restricted entities. If the sender is listed, secure the account before following the available unblock action.

Will SPF, DKIM, or DMARC unblock the account?

No. These email authentication controls help recipients identify spoofed messages, but they do not directly remove an Exchange Online sending restriction.

What should I send Microsoft support?

Include the affected sender address, the full non-delivery report, the time of failed messages, and relevant message trace results. Share message samples or headers privately through the support case.