Send & Receive Issues

Fix Microsoft 365 NDR 550 5.7.23 SPF Check Failed Errors

Phi Hung VoPhi Hung Vo Nov 20, 2026 868 views

Question details

Identify and resolve an SPF failure reported in a Microsoft 365 nondelivery report.

Fix Microsoft 365 NDR 550 5.7.23 SPF Check Failed Errors
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
A sender needs to deliver Microsoft 365 email to a domain that uses its own Exchange servers.
Observed behavior
A nondelivery report shows error 550 5.7.23 and indicates that the sending server's IP address is not authorized by the sender domain's SPF record.
Before you start

Keep the nondelivery report available and identify the sender domain and sending IP address reported in it. You will also need access to the domain's DNS settings or help from its DNS administrator.

Solution 1Recommended

Authorize the sending service in the domain's SPF record

Use this method when the sending IP address or service is missing from the sender domain's SPF record.

1
Check the nondelivery report

Open the NDR and note the sending IP address, the affected sender domain, and any SPF diagnostic details. If the message was relayed or forwarded, also review the message headers to identify the server that the recipient checked.

2
Inspect the SPF record

Look up the domain's DNS TXT records using a DNS lookup tool. Find the record beginning with v=spf1 and check whether it authorizes the sending IP address or the service that sent the message.

3
Update the DNS record

In your DNS provider's management console, edit the existing SPF TXT record to include every legitimate sending service. For Microsoft 365, this commonly includes include:spf.protection.outlook.com; add an ip4 mechanism only for an authorized public IPv4 address that needs it.

4
Verify and retest

After DNS changes have propagated, look up the TXT record again and send a new test message to the affected recipient. Confirm there is only one SPF record for the domain and that it does not exceed SPF's 10 DNS-lookup limit.

Authorize the sending service in the domain's SPF record
SPF example: A record might look like v=spf1 ip4:192.0.2.10 include:spf.protection.outlook.com -all. The IP address shown is documentation-only; use your actual authorized public sending IP address and retain any other required sending services.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making it easy to continue working with existing documents. It does not change Microsoft 365 mail delivery or fix SPF records.

Prepare documents and spreadsheets while your mail administrator investigates the SPF errorOpen and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface to make the transition from Microsoft Office easierWork with a lightweight office suite available for free
microsoft office alternative - wps office

Frequently Asked Questions

What does NDR 550 5.7.23 mean in this SPF failure?

It indicates that the recipient rejected the message after an SPF check failed. Review the NDR for the checked domain and sending IP address, then compare them with the domain's SPF TXT record.

Where do I change my domain's SPF record?

Sign in to the DNS provider that hosts your domain and open its DNS management page. Edit the existing TXT record that begins with v=spf1 rather than creating a second SPF record.

Does changing -all to ~all guarantee delivery?

No. The change produces a soft fail rather than a hard fail for unauthorized sources, but the recipient can still reject the message. Use it only as an approved temporary diagnostic step.

Why can SPF fail when the record looks correct?

The recipient may be checking a different IP address because the message passed through a relay or forwarding service. Examine the NDR and message headers, and ask the receiving administrator to check the rejection logs.