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

Access denied, bad outbound sender (Microsoft 365)

A 550 5.1.8 from Microsoft 365 says "Access denied, bad outbound sender". Microsoft blocked the sending account because it sent too much spam.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.1.8 Access denied, bad outbound sender (Microsoft 365)
All guides

Is your domain affected?

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

550 5.1.8 is a permanent SMTP reply meaning access denied, bad outbound sender (microsoft 365). Microsoft says this typically happens because the account was compromised by phishing or malware and then used to send spam. The block is on your own account, so every message from it bounces.

What 550 5.1.8 means

Microsoft says this typically happens because the account was compromised by phishing or malware and then used to send spam. The block is on your own account, so every message from it bounces.

⚠️
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

The mailbox was compromised

Most common

A stolen password or token let someone send spam from the account.

🔁
#2

A script or app sent bulk mail through the account

Common

Bulk or cold email sent through a normal Microsoft 365 mailbox looks like spam to Microsoft.

⚙️
#3

A mail rule forwarded large volumes

Less common

An inbox rule set up by an attacker forwarded or sent mail automatically.

How to fix 550 5.1.8

  1. 1

    Secure the account first

    Reset the password, sign out all sessions, turn on MFA, and remove unknown inbox rules, forwarding and app consents.

  2. 2

    Remove the account from Restricted entities

    In the Microsoft Defender portal, an admin can release the user from the restricted users list after the account is secure.

  3. 3

    Send bulk mail from a proper service

    Use a sending service and separate domains for campaigns, not a normal Microsoft 365 mailbox.

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