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

TenantAttribution; Relay Access Denied (Exchange Online)

A 550 5.7.64 says "TenantAttribution; Relay Access Denied". It happens in hybrid setups where an inbound connector receives mail from your on-premises server.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.7.64 TenantAttribution; Relay Access Denied (Exchange Online)
All guides

Is your domain affected?

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

550 5.7.64 is a permanent SMTP reply meaning tenantattribution; relay access denied (exchange online). Microsoft explains that something changed in your on-premises environment, so the inbound connector's configuration no longer matches and Exchange Online cannot tell which tenant the mail belongs to.

What 550 5.7.64 means

Microsoft explains that something changed in your on-premises environment, so the inbound connector's configuration no longer matches and Exchange Online cannot tell which tenant the mail belongs to.

⚠️
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 on-premises public IP changed

Most common

The connector is set to accept mail from a specific IP, and the server now sends from another one.

🔁
#2

The certificate the connector expects changed

Common

The connector identifies your server by certificate name, and the certificate was renewed with a different name.

⚙️
#3

The connector was edited or removed

Less common

A change in the Exchange admin center broke the match.

How to fix 550 5.7.64

  1. 1

    Compare the connector with the real server

    In the Exchange admin center, check the inbound connector's sender IPs or certificate name against what your server uses now.

  2. 2

    Update and validate the connector

    Correct the IP or certificate setting and use the connector validation in the admin center.

  3. 3

    Check SPF at the same time

    If the public IP changed, your SPF record may also need the new address.

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