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
Hi, As announced at Ignite Sep 2020, we will be making this functionality available as an open source tool by the end of the year. It can be used to pull in 1 or more security groups (nested or not) to drive the membership of a M365 Group. The membership will be pulled in as a flat list and kept in sync with the security group membership. However, if you have a pressing need for it before then, please reach out to GMMSupport@service.microsoft.com for a download of the tool. There is no support provided for the tool from Microsoft, other than answering any question around how we use it here. Link to the tool demo at Ignite: Making IT more efficient with improvements to Microsoft 365 Groups – https://aka.ms/Admin1011
Sam Kear commented
Why am I even here voting for a feature that should be just built in?
tell you more...? what more do you need to know after 4 years and this being the top requested idea for O365 groups?
Is the sub-group feature already available? That is, the possibility to have under one umbrella different projects/ independent groups?
Diane Cochran commented
Nesting is a necessity.
Please add this necessary legacy functionality.
Jenna Bonner commented
Nesting groups is an administrative necessity to manage communications to end users for all companies, but especially a large Global company. From an applications perspective, this is the easiest way to communicate health and alerting to various groups who are impacted.
Andrew Reggans commented
Nesting groups will allow O365 group owners to work smarter, not harder. This will definitely impact efficiency within teams and inter-working groups.
Eric Harding commented
This would greatly help our users and administrators!
James Read commented
We need to be able to net groups for Office 365 groups.
The ability to nest groups is critical - and seems quite easy to add, please just do it!
Jeff MacPhail commented
at least let us nest Office 365 Groups into Distribution Lists!!!
This would also be useful to have different permissions in the subgroup that may be doing PowerBI work vs. general collaboration permissions in the Teams/Sharepoint. I don't want members of the larger project having access to publish half-baked PowerBI Reports/Apps to a premium workspace. However, I do want the PowerBI workspace to be linked to the broader project/team that the group represents.
Gavin Bollard commented
Even if you don't allow "nesting" as such, it would be good to be able to flag various "attributes" of group membership, for example "READER" versus "MEMBER" this would probably give us the same functionality -- ie: if we had a 365 group that worked in SharePoint/Teams but could say "Today we want to be able to Email/calendar this group, but only the MEMBERS and OWNERS, not the READERS. Similarly, being able to say within this SharePoint site, give the "READERS" read-only level access and the Members Editor level
Jerry Nguyen commented
Make this work please! This will lead many to go back to Distributions from Groups. Surprisingly Microsoft never thought of this before they implemented the Groups? Yes, I understand the identity crisis from Groups nesting but make it simple and remove the nested identities from any sub groups and add the sub groups' members email addresses as email distributions only. Can't be that hard.
Been said by many here, so this is to throw some more weight: Microsoft, the new functionality you're rolling out which requires O365 groups, and those groups not supporting nesting, is an administrative nightmare.
We have been trying to simplify our permissions and distributions into a root set of role based groups, but this is breaking those efforts. We want to be able to get most users 90% of what they need in terms of access and information distribution by adding them to a single core representative role group. What we find with O365 groups is we're facing going back to the days of having out of control group membership and no handle to what a user should and shouldn't have. New user? Make them look like Bob. Changed role? What should they keep or have added?
Daniel Schnyder commented
Just do it - it is a pain in the projects, that it is not possible ot nest AD Groups in Universal groups.
An example would be 4 divisions within one department. Maintaining a list of users in one place would be helpful.
Tam Vuong commented
I just upgrade our com site to a Hub and find out that I cannot nested groups for anything. Instead of having one Officers group and one Staff group, I now have to maintain one Officers group, one Staff group, one Officers + Staff, and the same 3 security groups. I am struggling.
Geoff Hallford commented
At this point, even if you rolled-out that only the email functionality of nesting was done, that is good enough. Forget about permissions for other things like Teams, Power BI workspaces, etc. Just make the email nesting work please.