Send & Receive Issues

Forward a Synchronized Distribution List to a Microsoft 365 Shared Mailbox

Khadija KhanKhadija Khan Nov 14, 2026 868 views

Question details

Route messages sent to an on-premises Active Directory distribution list to a Microsoft 365 shared mailbox.

Forward a Synchronized Distribution List to a Microsoft 365 Shared Mailbox
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
An administrator wants to use a synchronized distribution list with a cloud mail-flow rule that delivers messages to a shared mailbox.
Observed behavior
Messages addressed to the synchronized distribution list should reach the Microsoft 365 shared mailbox.
Before you start

Confirm that the distribution list is synchronized to Microsoft 365, the shared mailbox exists in Exchange Online, and you have permission to manage mail-flow rules. Check the current mail route so you know whether messages pass through Exchange Online.

Solution 1Recommended

Create an Exchange Online mail-flow rule for the distribution list

Use a cloud rule to redirect messages addressed to the synchronized distribution list to the shared mailbox.

1
Verify synchronization

In the Exchange admin center, open Recipients > Groups and confirm that the synchronized distribution list and its email address appear.

2
Verify the shared mailbox

Open Recipients > Mailboxes and confirm that the shared mailbox exists and has the expected email address.

3
Create the rule

Go to Mail flow > Rules, select Add a rule, and choose Create a new rule. Give the rule a descriptive name.

4
Set the condition and action

Under Apply this rule if, select The recipient is and choose the synchronized distribution list. Under Do the following, select Redirect the message to and choose the shared mailbox, then save and enable the rule.

5
Test delivery

Send a test message to the distribution list, check the shared mailbox, and use Mail flow > Message trace in the Exchange admin center to investigate if delivery fails.

Create an Exchange Online mail-flow rule for the distribution list
Redirecting changes delivery: A redirect can prevent the original recipients from receiving the message. Test the rule with the intended recipient combinations and mail routes before relying on it.
Free Microsoft Office alternative

Use WPS Office for everyday document work

WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for easier migration. Exchange Online mail-flow rules and shared mailboxes must still be managed in Microsoft 365.

Work with Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for everyday document tasksReview migration plans and mail-flow documentation in one office suiteGet a free, lightweight alternative for document work
microsoft office alternative - wps office

Frequently Asked Questions

Does the distribution list need to appear in Microsoft 365 first?

Yes. Allow the on-premises list to synchronize, then check Recipients > Groups in the Exchange admin center before selecting it in the rule.

Will a redirect rule also deliver messages to distribution list members?

A redirect can prevent original recipients from receiving the message. Test the rule with the intended recipients and mail routes before deployment.

Do I have to change the MX record to create the rule?

No. You can create the rule separately, but messages must pass through Exchange Online for a cloud mail-flow rule to process them. Change the MX record when the domain is ready for its mail cutover.

How can I check why a message did not reach the shared mailbox?

Open Mail flow > Message trace in the Exchange admin center and search for the test message. Also verify the rule is enabled, the recipients are correct, and the message passed through Exchange Online.

Should I keep the synchronized list after migration?

Review whether an on-premises distribution list, a cloud distribution list, or a Microsoft 365 Group best fits your management and collaboration needs before changing the configuration.