Send & Receive Issues

How to Fix Missing Bounced Email Notifications in Exchange Online Groups

John WilsonJohn Wilson Nov 2, 2026 868 views

Question details

The user is not receiving nondelivery reports (NDRs) when emails sent to external members of a Microsoft 365 or Exchange Online distribution group fail to deliver.

How to Get Notifications for Bounced Emails Sent Through Exchange Online Groups
Product
Exchange Online
Device & OS
not provided
Scenario
Sending emails to external members of an Exchange Online distribution group and expecting a bounce notification if the delivery fails.
Observed behavior
Emails fail to reach external members, but the original sender does not receive any nondelivery report or bounce notification from the remote system.
Before you start

Ensure you have Exchange Administrator privileges in your Microsoft 365 tenant and access to Exchange Online PowerShell to modify distribution group settings.

Solution 1Recommended

Enable Originator Reporting via Exchange Online PowerShell

Modify the distribution group's settings using PowerShell to ensure nondelivery reports (NDRs) are correctly routed to the original sender or group manager.

If both the 'ReportToManagerEnabled' and 'ReportToOriginatorEnabled' properties of an Exchange distribution group are disabled, the Return-Path header of outgoing emails is left blank. Because of this missing header, remote mail servers cannot send delivery failure reports back to your organization.

1
Connect to Exchange Online

Open PowerShell as an administrator and connect to your Exchange Online tenant by authenticating with your Microsoft 365 administrator credentials.

2
Check Current Group Settings

Run the command 'Get-DistributionGroup -Identity "GroupName" | Format-List ReportToManagerEnabled, ReportToOriginatorEnabled' to verify the current configuration of your distribution group.

3
Enable Reporting to the Originator

Execute the command 'Set-DistributionGroup -Identity "GroupName" -ReportToOriginatorEnabled $true' so that the original sender will receive the bounce notification when an email fails.

4
Enable Reporting to the Manager (Optional)

If you prefer the group manager to handle delivery failures instead, run 'Set-DistributionGroup -Identity "GroupName" -ReportToManagerEnabled $true'.

Enable Originator Reporting via Exchange Online PowerShell
Configuration Complete: Once enabled, remote mail systems will be able to read the Return-Path header and successfully route nondelivery reports back to your designated senders.
Free Microsoft Office alternative

Experience a Seamless Productivity Suite with WPS Office

While Microsoft 365 handles your backend Exchange and email administration, you need a highly efficient, lightweight office suite for your daily document management. WPS Office provides a powerful, free alternative to Microsoft Office desktop apps.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install the Suite: Run the downloaded installer file and follow the simple on-screen prompts to set up the software.
  3. 3. Open and Edit Files Instantly: Launch WPS Office to instantly open, edit, and save your existing Word, Excel, and PowerPoint documents without formatting loss.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx) for smooth collaboration.Lightweight installation with blazing-fast document startup speeds.Familiar user interface ensuring a seamless migration with zero learning curve.Built-in advanced PDF editor, document collaboration, and smart AI tools.
microsoft office alternative - wps office

Frequently Asked Questions

Why do external emails fail without sending a nondelivery report?

When an Exchange Online distribution group has its reporting properties turned off, the outgoing email goes out with a blank Return-Path. Remote email servers rely on this Return-Path to send bounce messages, so without it, the failure notification is simply dropped.

Can I change NDR settings directly from the Microsoft 365 Admin Center?

While basic group management can be handled in the Exchange Admin Center under the Recipients tab, modifying advanced routing and reporting flags like 'ReportToOriginatorEnabled' generally requires using Exchange Online PowerShell for precise configuration.

How long does it take for the new PowerShell settings to take effect?

Changes made via Exchange Online PowerShell may take a short amount of time—typically up to an hour—to fully propagate across all Microsoft 365 servers and update the distribution group's routing behavior.