Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 550 5.7.64 TenantAttribution; Relay Access Denied | SMTP transaction log | -> |
| Affected OS build range | Windows 10, Windows 11 | Microsoft documentation | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Exchange\ClientAccess\SmtpClientAuthenticationEnabled | Registry Editor | -> |
| Relevant service URL | https://outlook.office365.com/ECP/ | Exchange admin center | -> |
| Log line signature | SMTP transaction log with 550 error code | SMTP submission logs on sending server | -> |
Log Files to Check
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Smtp\Smtp.logC:\ProgramData\Microsoft\ExchangeServer\V15\Logs\MessageTracking
What This Error Actually Means
The error code "550 5.7.64 TenantAttribution; Relay Access Denied" is raised by Exchange Online when an email submission attempt fails due to the sending server or connector lacking proper authorization to relay mail for a recipient domain within your organization's tenant. This error specifically indicates that the sender's IP address, TLS certificate subject, or other identifying attributes do not match those configured in the inbound connectors of your Exchange Online environment. The component responsible for this check is part of the Microsoft 365 Defender and Exchange Online Protection (EOP) services, which enforce strict security policies to prevent unauthorized relay access.
Affected Versions and Scope
This error affects all versions of Windows 10 and Windows 11 when attempting to send emails through an on-premises mail server or application that is configured to use Exchange Online as a smart host. It does not affect users directly accessing their Office 365 mailbox via Outlook Web Access (OWA) or other native clients, since these methods typically do not involve relaying through an external SMTP submission process.
Where To Look First: Logs and Event IDs
To diagnose this issue, start by checking the following logs:
-
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Smtp\Smtp.log: This file contains detailed transaction records for SMTP messages processed on your Exchange server. Look for entries containing the exact error string "
550 5.7.64 TenantAttribution; Relay Access Denied".
-
C:\ProgramData\Microsoft\ExchangeServer\V15\Logs\MessageTracking: This directory holds message tracking logs that provide a comprehensive view of email traffic, including failed delivery attempts. Search for entries with the same error code.
Additionally, review Event IDs 9603 and 9604 in the Windows Event Viewer under
Applications and Services Logs > Microsoft > Exchange > Message Tracking. These events indicate SMTP transaction failures that may be related to your issue.
Root Causes
Incorrect or Missing Inbound Connector Configuration
This occurs when an on-premises mail server is configured to route outbound email through the MX record of Exchange Online without properly setting up an inbound connector in EOP. To differentiate this from other causes, check if the sending IP address or TLS certificate subject does not match any allowed entries in your inbound connectors.
SMTP AUTH Disabled for Sending Account
If the application uses SMTP authentication but the account has it disabled, you will see this error. Verify that
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Exchange\ClientAccess\SmtpClientAuthenticationEnabled is set to 1 (enabled) or check if the mailbox's SMTP AUTH settings are correctly configured.
Mismatch Between Sending IP and Inbound Connector Rules
When the sending IP address changes and no longer matches the allowed list in your inbound connector, this error will occur. Review the
Exchange admin center > Mail flow > Connectors to ensure that all current IP addresses are listed.
Fix Procedure
- Identify Sending Path: Use
Get-MessageTrace -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date) in Exchange Admin Center to find the message trace for the failing email. Note down the 'Source IP' and 'Connector Id'. This helps determine if mail arrived via an expected inbound connector.
- Check Inbound Connector: Navigate to
Exchange admin center > Mail flow > Connectors, select your inbound connector, and verify that 'Identify the sending server' lists the correct IP address. If it has changed, add the new IP to the connector.
Enable SMTP AUTH if Needed:
Use PowerShell: Set-CASMailbox -Identity [email protected] -SmtpClientAuthenticationEnabled $true. This ensures that the sending account can authenticate properly. Alternatively, check the mailbox's settings in EAC.
- Configure Application Relay Correctly: Ensure your application is configured to submit emails via smtp.office365.com on port 587 with STARTTLS and authenticated credentials instead of unauthenticated submission on port 25.
Error Code Variants
| Code | Description |
| 550 5.7.64 TenantAttribution; Relay Access Denied | Unauthorized relay attempt from an untrusted IP or certificate. |
| 550 5.1.23 Mailbox unavailable | Email recipient mailbox does not exist in the tenant. |
| 554 5.7.1 Sender rejected by policy | Sending IP or domain violates sender policy rules. |
Verification
After applying fixes, verify that the error no longer appears in your SMTP transaction logs and message tracking records. Additionally, confirm through EAC > Mail flow > Connectors that all necessary configurations have been updated correctly.
Prevention
To prevent recurrence of this issue, ensure strict management of inbound connectors to only allow trusted IP addresses or TLS certificate subjects. Regularly review and update these settings as your network environment evolves. Implement a baseline policy requiring SMTP authentication for all outbound email submissions from on-premises servers or applications.
A quick diagnostic shortcut is to use the Get-MessageTrace cmdlet with specific filters to isolate recent failed delivery attempts, which can provide immediate insights into problematic IP addresses or connector configurations.
This guide should help you effectively troubleshoot and resolve issues related to unauthorized relay access in Exchange Online environments.