Enable Transport Rule action for Distribution Group
In Exchange Online or EOP, We cannot create a transport rule with the action set to Distribution Group.
It errors as follows :
The transport rule can't be created because email@example.com, the recipient to be added by a rule action, is a distribution group. Transport rules can't add distribution groups to messages. To resolve this error, remove this recipient and specify a different one.
Since there are workarounds to resolve, Can this be fixed directly without any error.
We are mid migration to a new company with differnt emails; in the interim we have a forward and deliver transport rule in place so the current mailbox will send an auto reply to advise of the change of address. however to make it simpler for users, any email arriving in their old inbox is being marked as read and put in deleted items folder. This works great - unless the email is sent to a group they are a member of - in this case the rule doesn't wrok and it stays in the inbox unread. There appears no way to make this work in current setup - Please can MS do something to resolve this? seems craxzy this won't work!
Vinicius Aires commented
De que adianta ter as regras de transporte se tenho uma brecha de segurança quando o e-mail é enviado para um grupo?
This is crazy stupid. Not even transport rules to action for O365 Groups. Terrible fail.
We are actually performing a migration from on-premise 2010 Exch. and this issue puts a halt in the project to create the transport rule
Is there anyway to get round this issue? I want to setup a transport rule to forward mail.
I was wondering if anyone else has run into an issue that although you can have 300 Transport Rules .. you can only direct mail to 100 recipients with all the rules combined.
why is this limitation?
Sara Moore commented
Auto transport city, the best leading transportation platform for shippers and carriers. A single platform where you can easily transport and ship your car easily within the secure payment and 24/7 support assistance.
in a roundabout way, I tried to do the above to fix an office 365 group to have an alias that can be emailed externally. In the end, I found a way to do it via PowerShell. should be in the GUI. https://stackoverflow.com/questions/49057054/adding-an-alias-to-a-microsoft-o365-group
seriously? c'mon and fix this already!
Paul Youngberg commented
Any update MSFT?
This is absolutely stupid MS. For crying out loud you can do it on prem why not in 365? Now I have to have loads of shared mailboxes holding sensitive data just to work around a stupid limitation?
Not sure if anyone still needs assistance with this, but you can work around it by explicitly stating the initial recipient or subject via headers within the rule configuration.
So the rule looks for To:Your@EmailHere within the email header for example and applies the rule to anything thats sent to that address, even if it's a D/L. :)
Ryan Pizzi commented
There are many reasons for us to want to send notices or bcc things to a distribution group and seems like an arbitrary limitation to have baked in to Exchange.
Reviving this topic -- why is this limitation imposed? Any updates?
Stefan Fritsch commented
I tried to use redirection in a Shared Mailbox and it doesn't accept groups as recipient.
So what are the workarounds?
And why do we have to jump through these loops, Microsoft?
Kingson Jebaraj commented
Sorry for delay in response I am not being notified if comment made to this, Yes, as Timothy mentioned I have tried using Shared Mailbox and enabled redirection.
I guess you have to create a shared mailbox and set the redirection to distribution group there.
What are the workaround solutions?
Is there anyway to get round this issue? I want to setup a transport rule to forward mail