Send & Receive Issues

How to Find Messages Blocked by Directory-Based Edge Blocking in Exchange Online

Amos GikundaAmos Gikunda Nov 3, 2026 871 views

Question details

The user needs to locate logs or message traces for emails that were blocked by Directory-Based Edge Blocking (DBEB).

How to Find Messages Blocked by Directory-Based Edge Blocking in Exchange Online
Product
Exchange Online
Device & OS
not provided
Scenario
Sending messages to a mail-enabled public folder, which get rejected before reaching the Exchange Online service.
Observed behavior
Senders receive a '550 5.4.1 Access Denied' NDR, but the blocked messages do not appear in the Exchange Online message trace.
Before you start

Ensure you have Microsoft 365 Exchange administrator privileges and have requested the complete Non-Delivery Report (NDR) from the original sender.

Solution 1Recommended

Investigate DBEB Rejections Using NDRs and Domain Settings

Because Directory-Based Edge Blocking rejects messages at the network edge, standard message traces cannot be used. You must rely on the NDR codes and verify your accepted domains configuration.

Directory-Based Edge Blocking (DBEB) is designed to reject messages for invalid recipients before they enter the Exchange Online network. Because of this early rejection, these events bypass the transport pipeline and are not logged in the standard message trace accessible to tenant admins.

1
Collect the Non-Delivery Report (NDR)

Ask the sender to provide the complete bounce message. Look for the specific error code '550 5.4.1 Access Denied', which confirms DBEB intercepted the email.

2
Verify Recipient Existence in Exchange Admin Center

Log in to the Exchange Admin Center and verify that the mail-enabled public folder or recipient address actually exists, is spelled correctly, and is properly synced to Entra ID (Azure AD).

3
Check Accepted Domains Configuration

Navigate to Exchange admin center > Mail flow > Accepted domains. Ensure the domain type is configured correctly. If it is set to 'Authoritative', DBEB is enforced. If routing unknown recipients to an on-premises server is required, consider changing it to 'Internal Relay'.

Consult Microsoft Support: If the recipient exists but messages are still blocked without a trace, you may need to escalate the issue to Microsoft Support or the Microsoft 365 community, as tenant admins cannot retrieve complete edge-level server logs.
Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While server-side email routing issues require Microsoft 365 administration, your daily document management needs a reliable, hassle-free suite. WPS Office is a lightweight, highly compatible alternative to Microsoft Office for creating documents, spreadsheets, and presentations.

Seamless compatibility with Microsoft Word, Excel, and PowerPoint formatsLightweight application that runs smoothly on almost any deviceFamiliar, intuitive user interface for a zero-learning-curve transitionCompletely free basic version with powerful built-in PDF editing tools
microsoft office alternative - wps office

Frequently Asked Questions

Why does a 550 5.4.1 error happen with mail-enabled public folders?

This error typically occurs when Directory-Based Edge Blocking (DBEB) determines the recipient doesn't exist in the directory at the network edge. This is often caused by synchronization delays or configuration issues with mail-enabled public folders.

Will an Exchange Online message trace ever show DBEB rejected emails?

No. Because DBEB rejects the message at the service edge before it fully enters the Exchange Online transport pipeline, no standard message trace record is generated for the tenant.

Can I disable Directory-Based Edge Blocking in Exchange Online?

DBEB is enabled by default for all domains set as 'Authoritative'. Changing the domain type to 'Internal Relay' bypasses DBEB, but you should only do this if you actually need to route emails for unknown recipients to a third-party or on-premises server.