WarningSMTP Error · Permanent (5.x.x)
550 5.7.133

Sender not authenticated for group (Microsoft 365)

A 550 5.7.133 from Microsoft 365 says "Sender not authenticated for group". The address you wrote to is a group that only accepts mail from inside its own organization. 5.7.134 is the same for a single mailbox, and 5.7.12 for any recipient set up that way.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.7.133 Sender not authenticated for group (Microsoft 365)
All guides

Is your domain affected?

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

550 5.7.133 is a permanent SMTP reply meaning sender not authenticated for group (microsoft 365). This is a setting at the recipient's organization, not a problem with your domain. Microsoft says only the recipient organization's email administrator, or the group owner, can change it.

What 550 5.7.133 means

This is a setting at the recipient's organization, not a problem with your domain. Microsoft says only the recipient organization's email administrator, or the group owner, can change it.

⚠️
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 group is internal only

Most common

Distribution lists and Microsoft 365 groups block outside senders by default.

🔁
#2

You wrote to a team address

Common

Addresses such as sales@ or support@ are often groups with this setting.

⚙️
#3

The recipient's organization changed the setting

Less common

An address that worked before now rejects outside mail.

How to fix 550 5.7.133

  1. 1

    Contact the recipient another way

    Ask them to allow external senders for the group, or to give you a direct address.

  2. 2

    For the recipient's admin

    In the Microsoft 365 admin center or Exchange admin center, allow external senders on that group or mailbox.

  3. 3

    Nothing to fix on your domain

    Your SPF, DKIM and DMARC are not the cause of this bounce.

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