Be able to Nest Groups like Distribution Groups
Be able to Nest Groups like Distribution Groups. I decided to convert a lot of our team DGs to O365 groups without realizing I wouldn't be able to nest them
Anonymous
shared this idea
We have announced that Group Owners will be able to leverage existing groups to drive membership in Office 365 Groups.
153 comments
-
brad
commented
I'm not sure if this was "fixed" so would appreciate to know if what I am seeing has existed or is new.
If I go in to Outlook web to create a distribution list, I can search and add the email from an Office 365 group to a distro list. No PowerShell, just basic Outlook for web.
So standard distro list nests and Office 365 group so I can add/remove users easily via the Group. I don't know how responsive it is if I add/remove users to the group and some people in the company have concerns this will not work. Has anyone else tried this?
-
Anonymous
commented
C'mon, we should be able to add O365 groups to mail-enabled security groups or DLs. Blows my mind this is not yet implemented despite numerous requests.
We have an "All Staff" mail-enabled security group, and it's members are O365 groups for each of our physical locations. All users belong dynamically to their respective location/O365 group. We've grown over the years and added several new locations, which now don't get All Staff emails because their location groups don't belong to the "All Staff" group.Yes there is a way to do this with Powershell, but we shouldn't need to do this and I have very little experience with PS.
-
Peter Methven
commented
This is really important to be able to manage groups sensibly and reduce duplicated work and people being missed etc.
-
james
commented
When we bring on a new employee, we would love to be able to just add them to a group such as HR, and that would then join them to all HR-related Teams/Groups.
regards
http://techninjapro.com/ -
Eric Shaw
commented
How can it take you this long to implement such a basic feature????
-
Justin Lee
commented
Here is a workaround:
distribution group > shared mailbox > Office 365 group
Set the shared mailbox to forward to the Office 365 group address, and set it to not keep a copy in the inbox to prevent the shared mailbox from filling up.
Doing this you'll find that the email goes to both the Office 365 group folder and to anyone who subscribes. You'll need one shared mailbox to every one Office 365 group you want to receive mail via distribution group.
With the Powershell command to add the Office 365 group as a member, only people who are subscribed to the group receive the message.
This is not ideal and I hope they enable full functionality for nesting office 365 groups under distribution groups, but this way works if you really need this functionality.
-
Anonymous
commented
We use distribution lists and have recently adopted O365 groups. However, it's critical that for units/teams moving to O365 groups they can be nested within distribution lists for more conventional, top-down communications from management. Hoping this feature comes soon!
-
Alex Janes
commented
I've had to write custom scripts to keep security groups and O365 groups in sync. But, this should just be core functionality. Basics of group management should've been working for this product feature at launch.
-
Dave
commented
June 2019 is the last response indicating "IN THE PLANS"
Many of us have enjoyed and leveraged Nested groups for many years now. This seems like a big step backwards. Please move forward sooner than later.
Until then we have to Avoid using Office 365 groups. The maintenance overhead is too great. -
Manuel Meister
commented
Without this our admin cost is very high. We want multiple groups to have access to one team.
-
Michael Waters
commented
agreed... again... like trying to steer an aircraft carrier to get some of this common sense stuff done.
-
Michael Nelson
commented
This was flagged "in the plans" 8 months ago... that's a lot of planning! Please update with ETA. Thanks
-
Jeff
commented
When we bring on a new employee, we would love to be able to just add them to a group such as HR, and that would then join them to all HR-related Teams/Groups.
-
Elmar Wiedemeijer
commented
While automating the on- and offboarding of our employees I ran into the following conundrum:
Distribution lists: can be nested, cannot be managed through Graph API.
Office 365 groups: can be managed through Graph API, cannot be nested.Can we please have one type of group that can both be nested and is compatible with Graph API?
-
Greg Kostal
commented
Adding or deleting a group within a group is important to have when managing email traffic. Example, 10 families that I coach that have 3-5 emails per family. I'd create 10 groups by family name, and create one master group that has those 10 families. As families come and go, I should be able to add/delete. Can't do that now.
-
Amit Goswami
commented
Your comment is awaiting moderation.
Hello Office Team,
Please add feature, so that we could add one group to the another individual group, it will help us to add people of one group in one go to the another group.
For Example :
Group B = Members are A, B, C
Group C = Members Are D, E, F
Group A = Main (Adding Group B & C), so it will have all the 6 members and if I delete members from any of the group B and C, it will automatically deleted from group A
-
Matthias Fleschütz
commented
is that planned feature also covering https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/32016532-we-very-much-need-o365-to-support-nested-o365-grou ?
-
Nate
commented
FYI
Add-DistributionGroupMember -Identity {Dist List} -Member {O365 Group}
We use this to add O365 groups as members of Distribution lists and Mail-Enabled Security Groups
-
Anonymous
commented
Yes please!
-
James Lloyd
commented
Hey creative folks - what if we create a service account to be the 'sub group' and then have that service account forward mail to the actual sub-group? Since MS can't seem to figure it out. Users couldn't browse the message history, but at least they'd be included and not forgotten because there's a huge chain of groups to update with every staffing change.