What the Exchange Online bounce 550 5.4.1 Recipient address rejected: Access denied means, how Directory-Based Edge Blocking and the accepted domain type cause it, and how to fix one recipient or a whole domain in cloud and hybrid setups.
Home › Guides › Exchange Online 550 5.4.1
Last updated 17 November 2026
Microsoft documents this bounce (NDR) as:
550 5.4.1 Recipient address rejected: Access denied
Exchange Online sends it when Directory-Based Edge Blocking (DBEB) blocks an incoming message because the recipient's address is not valid. DBEB checks the recipient at the edge of the service, before anti-malware, anti-spam and mail flow rules run. If the address is not in Microsoft 365 for that domain, the message is rejected and the sender gets this NDR.
The fix belongs to the recipient's admin. If you are the sender, check the address for typos and then let the recipient know. If you are the recipient's admin:
Confirm where mail for the domain goes with the MX Record Lookup and that the domain belongs to the tenant you expect with the M365 Tenant Lookup.
Every domain you add to Microsoft 365 is an accepted domain, and Exchange Online has two types:
| Domain type | Mail to a known recipient | Mail to an address Exchange Online doesn't know | Use it when |
|---|---|---|---|
| Authoritative | Delivered | Rejected. Choosing this type turns on DBEB, so the sender gets 550 5.4.1. | All recipients are in Microsoft 365, or every on-premises recipient also exists in Microsoft 365 (for example as a synced mail user). |
| Internal relay (non-authoritative) | Delivered | Relayed to your own email server. You need a connector from Microsoft 365 to that server. | Some recipients live only on your own servers, or during a migration. |
Microsoft says not to choose Internal relay if all of the domain's recipients are in Microsoft 365. During a migration, its guidance is to set the domain to Internal relay first, add all recipients to Exchange Online (for example by directory synchronization), let them replicate, then switch to Authoritative so that mail to addresses that don't exist is blocked.
In Exchange Online PowerShell you can view and change the type:
Get-AcceptedDomain Get-AcceptedDomain -Identity contoso.com | Format-List Set-AcceptedDomain -Identity contoso.com -DomainType InternalRelay Set-AcceptedDomain -Identity contoso.com -DomainType Authoritative
More cmdlets are in the PowerShell Cheat Sheet.
Every address in the domain bounces. Microsoft's fix is to resync the domain: in the Exchange admin center, Mail flow > Accepted domains, open the domain and switch the type from Authoritative to Internal relay, then back to Authoritative. Also check that the domain really is meant to be authoritative. If some mailboxes still live on another system, Authoritative rejects mail for them unless they also exist in Microsoft 365.
One hybrid recipient with an on-premises mailbox. If you use directory sync to push changes to Microsoft Entra ID, reset that mailbox's SMTP proxy address: change it to a temporary address, then change it back. Allow up to 24 hours for DBEB to fully update.
An on-premises mail-enabled public folder. Check that the folder is synced to Exchange Online. If it isn't there, Microsoft points to the Sync-ModernMailPublicFolder script to copy on-premises mail-enabled public folders to Exchange Online.
An on-premises dynamic distribution group. These can't be synced to Exchange Online in a hybrid setup. Create a mail contact in Exchange Online with the same external email address as the group.
MX points somewhere else. In hybrid setups, Microsoft says DBEB only works if the domain's MX record points to Microsoft 365, so mail reaches Microsoft 365 first. Look up the MX with the MX Record Lookup or DNS Lookup, and after any change confirm it worldwide with the DNS Propagation Checker. Run the Email Deliverability Checker to see MX, SPF and DMARC together.
A real typo or a removed mailbox. Nothing is broken on the server side. The sender should correct the address. If the address used to work, check whether the mailbox was removed or its address changed.
Microsoft's Exchange Online NDR reference lists other codes with similar wording:
| Code | Text in the reference | Meaning |
|---|---|---|
| 5.4.1 | Recipient address rejected: Access denied | The recipient's address doesn't exist (DBEB). This guide. |
| 5.4.1 | Relay Access Denied | The mail server generating the error doesn't accept mail for the recipient's domain. Caused by mail server or DNS misconfiguration. |
| 5.7.504 | [address]: Recipient address rejected: Access denied | The recipient address isn't valid. Verify it and try again. |
Some bounces carry extra diagnostic text after the sentence, such as a bracketed reference code. Microsoft's 5.4.1 article documents only the sentence above, so this guide doesn't try to decode any trailing reference. If you have a copy of the NDR, paste its headers into the Email Header Analyzer to see which server generated it.
Get-AcceptedDomain.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Check where the domain receives mail with the MX Record Lookup, confirm the tenant with the M365 Tenant Lookup, watch DNS changes with the DNS Propagation Checker, read NDR headers in the Email Header Analyzer and keep cmdlets handy with the PowerShell Cheat Sheet. Related guides: Exchange Online 550 5.1.10, Exchange Online 550 5.7.520, Exchange Online 550 5.7.708 and Outlook.com 550 5.7.515.
Exchange Online rejected the message at the edge because the recipient address does not exist in Microsoft 365 for that domain. Directory-Based Edge Blocking generates it when the accepted domain is Authoritative. The recipient organization has to fix it unless the sender simply mistyped the address.
Only by correcting the address. Check the spelling in the bounce and try again. If the address is correct, contact the recipient another way and tell them their Microsoft 365 admin should check the recipient object, the accepted domain type and hybrid sync.
Microsoft suggests resyncing the accepted domain: in the Exchange admin center, under Mail flow, Accepted domains, switch the domain from Authoritative to Internal relay and back to Authoritative. Also confirm the domain should be Authoritative and that recipients hosted elsewhere also exist in Microsoft 365.
Only if some recipients really live on your own mail server, and then you also need a connector to that server. Microsoft says not to use Internal relay when all recipients are in Microsoft 365. During a migration, use Internal relay until all recipients are synced, then switch to Authoritative.
Microsoft says to allow up to 24 hours for Directory-Based Edge Blocking to fully update after you change an on-premises mailbox, such as resetting its SMTP proxy address. Test with a new message, not by resending the bounced one.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.