How to Fix Microsoft 365 Error 550 5.1.351 for External Emails
Question details
External senders are unable to deliver messages to users in a Microsoft 365 organization, resulting in a specific bounce-back error code.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Receiving external emails in a cloud-only Azure AD and Microsoft 365 environment.
- Observed behavior
- External senders receive a Non-Delivery Report (NDR) containing error 550 5.1.351, which indicates that the recipient is unknown or the mailbox is unavailable.
Ensure you have global administrator or Exchange administrator privileges in the Microsoft 365 Admin Center, and ask the external sender to provide a complete copy of the Non-Delivery Report (NDR) for analysis.
Verify Custom Domain and DNS Configuration
Ensure your custom domain is properly set up in Microsoft 365 and that the MX records are correctly pointing to Exchange Online.
External email delivery relies heavily on public DNS records. If your domain's MX (Mail Exchanger) records are missing, incorrect, or pointing to a previous hosting provider, external servers will not know where to deliver the mail, resulting in the 550 5.1.351 error.
Go to admin.microsoft.com and sign in with your global administrator credentials.
On the left navigation pane, go to Settings, then click on Domains.
Locate the affected custom domain. Ensure its status reads 'Healthy'. If the status is 'Incomplete setup', click on the domain to complete the necessary verification steps.
Click on your domain and navigate to the DNS records tab. Confirm that the MX record points exactly to the Microsoft 365 value provided (typically formatted as <yourdomain>.mail.protection.outlook.com).
If you recently updated the DNS records or created a new Microsoft 365 tenant, allow up to 72 hours for the DNS changes to fully propagate across the internet.
Analyze the Non-Delivery Report and Internal Mail Routing
Review the full bounce message and test internal communications to isolate whether the issue is tenant-wide or specific to a single user's mailbox provisioning.
Looking for a Reliable Office Suite? Try WPS Office
Since email server routing issues like Error 550 5.1.351 require administrative configuration within Microsoft 365 Exchange, WPS Office cannot directly resolve server-side email failures. However, if you are looking for a free, lightweight, and highly compatible alternative to desktop applications like Word, Excel, and PowerPoint, WPS Office is an excellent choice. It offers seamless format compatibility and a familiar user interface without the heavy subscription costs.
- 1. Visit the website: Go to the official WPS Office website to access the latest version.
- 2. Download the software: Click the 'Free Download' button to get the installer for your operating system.
- 3. Install and start: Run the installer, follow the simple on-screen instructions, and start working on your documents immediately.
Frequently Asked Questions
Why does Error 550 5.1.351 only affect external emails?
Internal emails route directly through Exchange Online without querying public DNS MX records. External emails, however, rely on public DNS settings to locate your mail server. If the DNS configuration is incomplete or incorrect, external senders will face delivery failures while internal communication remains unaffected.
How long does it take to receive external emails after fixing the domain in Microsoft 365?
If the delivery issue was caused by incorrect or missing DNS MX records, it can take anywhere from a few minutes up to 72 hours for the updated DNS settings to propagate across the global internet.
What does 'recipient unknown' mean if the user definitely exists in my Microsoft 365 Admin Center?
Even if the user exists in your active users list, external servers might be attempting to route the message to your previous email host due to outdated MX records. Alternatively, the user's mailbox might not be fully provisioned yet, or they might be missing a valid Exchange Online license.
Do I need on-premises hardware to resolve this email routing issue?
No. Since your environment uses Azure AD and Microsoft 365 natively without an on-premises Exchange server, all troubleshooting and configuration changes (such as licensing and domain verification) are done directly within the cloud-based Microsoft 365 Admin Center.
