Setup Transport rule to distribution group

Question

I would like to bcc all emails send to and from our domain emails into the appropriate Group email account. i.e. All emails sent or received from *@ourdomain.com that come from *@clientdomain.com will be bcc'd to the ClientDomain@ourdomain.com group email that was created in SharePoint/Teams. I have tried to set up a rule in the Exchange admin but I receive an error message about transport rules not being allowed for distribution lists....We use Microsoft Online 365

Answer 1

@Adam L

From this article, we can know that this is an expected behavior:

So, if you want to BBC email to many users, you many need to add those mailboxes into this transport rule one by one.

Here many be a workaround for you(Please note: this workaround only work when there doesn't exist nested group for the target group, it there exist nested group, it will fail):

1. Create a transport rule to BCC emails to one mailbox:
   
   
2. Use command below to add group member into this BCC list: Set-TransportRule BCC -BlindCopyTo (Get-DistributionGroupMember group1).name

You may need to run this command frequently to ensure that the BCC list users are up to date. If this workaround doesn't suitable for you, you may need to add mailboxes one by one so far.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I'm a bit late to the game, but I'm adding this for the benefit of others searching for a solution.

The method I use to reference a distribution group as a recipient is to match on the distribution group's email address in the To header.

In a message header condition, you can specify multiple "words," but reference only one header, so to include the CC header, you'd have to create another rule. Adding another condition to the same rule won't work. In a rule with multiple conditions, Exchange uses AND logic, so the match would have to test positive for both the To and CC headers to trigger the action.

Answer 3

I've run into this same issue and solved it with a different approach. Since our DL's tend to change membership, updating the transport rule didn't seem like a viable option for me so I did the following:

1. I created a shared mailbox and set the ForwardingAddress to my DL. I also set the DeliverToMailboxAndForward to $False since I don't want the email stored in the Shared Mailbox.
2. Next I created my Transport Rule and set it to BCC my newly created Shared Mailbox.

I don't like having extra shared mailboxes, but since they don't require a license, I just named them with "FORWARD" so I would know what they were for. I have about 5 of these accounts for special needs and it has solved my issue.

Answer 4

Thanks mate - sounds like a good solution, I'll check it out.

Answer 5

I had similar problem while attempting to put a DG as recipient into a Transport Rule on Exchange Online and the DG is synced from my on-premise environment.

In my case having Exchange on-premise in hybrid deployment was the solution as I just created a contact on EXO with same email address as my DG and added this contact as recipient to the Transport Rule on EXO.