Send & Receive Issues

Fix Microsoft 365 Emails to Gmail Failing With Error 550 5.7.350

Steven ParkerSteven Parker Nov 20, 2026 869 views

Question details

An organization needs to identify why Microsoft 365 messages to Gmail addresses are rejected with error 550 5.7.350.

Fix Microsoft 365 Emails to Gmail Failing With Error 550 5.7.350
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
Multiple users send messages from Microsoft 365 mailboxes to Gmail recipients.
Observed behavior
Outbound messages to Gmail fail, but incoming Gmail messages work. The issue persists after signature links were removed and an SPF record was added.
Before you start

Ask an affected sender for the complete non-delivery report, including the diagnostic text, recipient address, and message time. Have an Exchange administrator ready to run a message trace and check the domain's DNS records.

Solution 1Recommended

Trace the rejected message and review mail authentication

Use the full rejection details and an Exchange Online message trace to determine where delivery failed and what to investigate.

1
Collect the complete report

Open the non-delivery report in the sender's mailbox and retain the entire diagnostic message, not just the message headers. Note the sending time and Gmail recipient.

2
Check the scope

From affected mailboxes, send test messages to an internal recipient, a Gmail address, and an address at another external domain. Record which tests fail and whether the problem affects multiple users.

3
Run a message trace

In the Exchange admin center, go to Mail flow > Message trace. Search using the sender, recipient, and relevant time range; open the result and review its delivery events. Request an extended report if available.

4
Review authentication and policies

Compare the rejection text with the sending domain's SPF, DKIM, and DMARC configuration. In the Microsoft Defender portal, review outbound spam policies and any restricted users; also investigate sender reputation if the rejection points to it.

5
Escalate with evidence

If the cause remains unclear, open a Microsoft 365 support request in the admin center and provide the full non-delivery report and trace. If the diagnostic text identifies a Gmail rejection, use the details when seeking help through Google support channels.

Trace the rejected message and review mail authentication
Protect message data: Share reports through a private support channel because they can contain email addresses and other sensitive information. Adding SPF alone does not establish that all authentication or reputation checks pass.
Free Microsoft Office alternative

Prepare Email Content and Attachments With WPS Office

WPS Office is a free, lightweight alternative for preparing documents and attachments in a familiar interface. Its Microsoft Office format support makes moving existing files straightforward, although it cannot fix Microsoft 365 email delivery errors.

Draft and review email content or attachments in WPS WriterOpen and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface to transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Does error 550 5.7.350 mean Gmail caused the rejection?

Not necessarily. Read the complete non-delivery report and the events under Exchange admin center > Mail flow > Message trace to identify the rejecting system and its stated reason.

Why can I receive Gmail messages but not send to Gmail?

Inbound and outbound mail follow different paths and checks. Use Message trace for an affected outbound message, then review the rejection details and the sending domain's authentication and reputation.

Is adding an SPF record enough to fix delivery?

Not always. Check that the existing SPF record authorizes the services sending for your domain, and review DKIM, DMARC, outbound spam policies, and the specific rejection text.

What should I send to Microsoft Support?

Provide the complete non-delivery report and the relevant message trace or extended report through the support request. Include the time, sender, recipient, and results of internal and other external delivery tests.