Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 550 5.7.64 SMTP AUTH rejected | Exchange Online logs | -> Indicates basic auth disabled |
| OS build range | Windows 11 23H2 | System Information | -> Affected OS version |
| Relevant cmdlets | Get-TransportConfig, Set-TransportConfig | Exchange Online PowerShell | -> Used to check and modify transport settings |
| Service endpoint | outlook.office365.com:587 | SMTP server configuration | -> Commonly used for email clients |
| Log line signature | AUTHENTICATION_FAILED | Exchange Online logs | -> Identifies authentication issues |
Log Files to Check
C:\Windows\System32\winevt\Logs\Application.evtxExchange Online transport logs via PowerShell
What This Error Actually Means
The error code550 5.7.64 indicates that an SMTP AUTH request has been rejected by Exchange Online due to the tenant's enforcement of Modern Authentication (OAuth) policies. This specific error occurs when a legacy email client attempts to authenticate using basic authentication (username/password), which is no longer permitted in tenants where Modern Auth has been enforced. The component responsible for raising this error is the Exchange Online transport service, specifically during SMTP AUTH handshake processing.
This error is part of Microsoft's broader initiative to deprecate basic authentication in favor of more secure OAuth-based methods. Tenants that have enabled the "Modern Authentication" policy will block all legacy clients attempting to authenticate using plaintext credentials over SMTP.
Affected Versions and Scope
The error affects any Windows 11 23H2 environment where email clients are configured to useoutlook.office365.com:587 for SMTP submission. It is not limited to a specific OS build but rather depends on the tenant's authentication enforcement settings in Exchange Online.
Tenants that have explicitly disabled basic authentication via Set-TransportConfig -SmtpClientAuthenticationDisabled $true are affected, while those still allowing basic auth ($false) remain unaffected. This error does not impact clients using OAuth or modern authentication methods, nor does it affect on-premises Exchange deployments.
Where To Look First: Logs and Event IDs
To diagnose this issue, examine the following log sources: 1.C:\Windows\System32\winevt\Logs\Application.evtx: Look for events with ID 401 or 403, which indicate authentication failures. The exact log line to search for is:
AUTHENTICATION_FAILED
2. Exchange Online transport logs: Access these via PowerShell using:
Get-MessageTrace -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date)
Focus on entries with the status code 550 5.7.64.
Event ID 401 typically signifies a failed authentication attempt, while Event ID 403 indicates access denied due to policy restrictions.
Root Causes
Modern Auth Enforcement Policy Enabled
The most common cause is the tenant's Modern Authentication enforcement policy being enabled. This can be verified using:Get-TransportConfig | Select-Object SmtpClientAuthenticationDisabled
If SmtpClientAuthenticationDisabled returns $true, basic auth is blocked.
Legacy Email Client Configuration
Clients such as Outlook 2016 or older, or third-party email apps not updated to support OAuth, will trigger this error. These clients attempt to authenticate using plaintext credentials over SMTP, which is now prohibited.Transport Rule Misconfiguration
Sometimes, custom transport rules may inadvertently block legitimate traffic. Check for any enabled rules that might be causing the issue:Get-TransportRule | Where-Object {$_.State -eq "Enabled"}
Fix Procedure
Follow these steps to resolve the error:- Verify current transport settings:
Get-TransportConfig | Select-Object SmtpClientAuthenticationDisabled - If basic auth is disabled, re-enable it temporarily for troubleshooting:
Set-TransportConfig -SmtpClientAuthenticationDisabled $falseWarning: Enabling basic auth may expose credentials in transit. Ensure TLS is enforced. - Update legacy clients to support OAuth or switch to modern authentication methods.
- If re-enabling basic auth is not feasible, ensure all clients use OAuth by:
- Configuring Outlook for Modern Auth: Exchange admin center > Mail flow > Rules
- Updating third-party email apps to their latest versions
- Review and adjust transport rules if necessary:
Get-TransportRule | Where-Object {$_.State -eq "Enabled"} | Format-List - Verify the fix by checking logs for successful authentications.
Error Code Variants
| Error Code | Description |
|---|---|
| 550 5.7.64 | SMTP AUTH rejected due to Modern Auth enforcement |
| 550 5.7.1 | General authentication failure (e.g., invalid credentials) |
| 550 5.2.0 | Invalid recipient domain or routing issue |
To resolve error 550 5.7.64, you can use the Exchange Online PowerShell module to check and update your authentication settings. One useful cmdlet is Get-User, which allows you to retrieve detailed information about a user's account, including their authentication methods. For example:
Get-User -Identity "[email protected]" | Select-Object DisplayName,RecipientType,RecipientTypeDetails,PrimarySmtpAddress,AzureObjectId
To further diagnose the issue, review the Exchange Online service logs located at %ExchangeInstallPath%Logging\Protocol\ECP. These logs can provide insights into why SMTP AUTH is being rejected due to Modern Auth enforcement. Additionally, you may need to adjust settings in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\ClientAccess\OAB if your environment uses Offline Address Book (OAB) services.
Verification
After implementing fixes, verify success by: 1. Checking Application.evtx for events with ID 401 resolved to success. 2. UsingGet-MessageTrace to confirm successful deliveries.
3. Testing SMTP AUTH from a legacy client after configuration updates.
Prevention
To avoid recurrence: 1. Implement monitoring for transport config changes using Azure Activity Logs. 2. Educate users on migrating away from legacy clients. 3. Regularly audit authentication methods in use viaGet-AuthConfig.
4. Establish a process for updating email clients before enforcing Modern Auth.
Get-AcceptedDomain | Select-Object DomainName,DomainType to verify domain configurations that might affect authentication.