Critical ErrorSMTP Error · Permanent (5.x.x)
550 5.7.708

Microsoft 365: traffic not accepted from this IP

A 550 5.7.708 from Microsoft 365 says "Access denied, traffic not accepted from this IP." Its partner 5.7.705 says "Access denied, tenant has exceeded threshold." Microsoft has limited the sending ability of your Microsoft 365 tenant.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.7.708 Microsoft 365: traffic not accepted from this IP
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

550 5.7.708 is a permanent SMTP reply meaning microsoft 365: traffic not accepted from this ip. Microsoft found that most of the mail from your tenant looks suspicious, so it banned outbound mail from it. This is a block on your tenant, not on one message.

What 550 5.7.708 means

Microsoft found that most of the mail from your tenant looks suspicious, so it banned outbound mail from it. This is a block on your tenant, not on one message.

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

A mailbox in the tenant was compromised

Most common

A stolen password let a spammer send large volumes through your tenant.

🔁
#2

A new tenant sent a lot of mail at once

Common

New Microsoft 365 tenants have low trust. Bulk or cold email from them is quickly limited.

⚙️
#3

An open relay or connector is abused

Less common

An inbound connector or app relay lets outside senders send through you.

How to fix 550 5.7.708

  1. 1

    Stop the abuse

    Reset passwords, turn on MFA, remove bad inbox rules and connectors, and check the outbound spam report.

  2. 2

    Contact Microsoft support

    Microsoft says to make sure any compromise or open relay is fixed, then contact support through your normal channel to lift the block.

  3. 3

    Do not send bulk or cold email from Microsoft 365

    Use a dedicated sending service and separate domains for bulk mail, and watch those domains for problems.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check