Forum Discussion
Nesting Groups
Just use Distribution lists if that's all you want, they are entirely just as available as they have ever been, fully support nesting etc.
Alternatively if you read up, TonyRedmond explains that you can nest an Office 365 group within a DL via powershell if you absolutely must.
Why do you want to forward email out of a group? To where?
It's easy to do this. Just add the address you want to receive the forwarded email as a member and make sure that their address is subscribed to the group... That address then receives a copy of every message sent to the group, which is an effective auto-forward.
I understand the limitations once you turn a distribution list into an ACL. But why would any mail platform provider choose to replace distribution lists altogether--it's crazy. There are HUNDREDS of valid use cases for nested distribution lists which have nothing to do with security access to anything.
For example, I'm in a (currently) very small tech company with limited IT needs. However, one of the FIRST things we needed operationally was nested distribution lists, so that the ops team can easily get notifications from different components of the infrastructure with unique addresses, but without having to add the same people to every address. You get a new tool, you create a group address for the tool so you can create an account using it and get its notifications, and simply forward it to the existing Ops team.
What's the proposed solution for this scenario? Just keep using distribution lists or what? I tell you what I'm NOT doing--buying some ridiculous additional tool just to accomplish what every other mail system on the planet does out of the box as basic functionality.
/mike
Mike Mitchell distribution lists still exist and there's no plans to remove them, but also from your description I don't see why you wouldn't be better using an Office 365 group for your ops team anyway and get all the benefits of collaboration as well as email.
- Because:
1) I can't forward other distribution lists to a Office 365 group, as per my use case above, which is my whole point. Even if I wanted to use collaboration, that group type wouldn't solve my problem. But, since you brought it up...
2) There are exactly zero Microsoft collaboration tools we're interested in using. In fact, I'm questioning the decision to use Office 365 itself, based on ridiculous feature decisions like this.Just use Distribution lists if that's all you want, they are entirely just as available as they have ever been, fully support nesting etc.
Alternatively if you read up, TonyRedmond explains that you can nest an Office 365 group within a DL via powershell if you absolutely must.