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
Trying to drink the Office 365 Groups koolaid but can't. I need to be able to add an Office 365 Group to multiple Office 365 Distribution Groups. Not sure how O365 Groups got out of the barn w/o this feature, let alone last this long w/o it. Perhaps I'm missing a concept that avoids the need.
Ankita Pillai commented
Can we have a provision for creating a subgroup that inherits some properties from its parent O365 group such as either group members or a prefix in the email id for the new group.For example- we have an O365 group which creates the email id email@example.com and we need to extend the group abc then the subgroup can have firstname.lastname@example.org (prefix abc which shows the relation) Sometimes we need to extend the existing O365 group, in that case instead of creating a completely new group with different email id we can make use of this functionality.
It would be nice to be able to nest groups and have that wizard that migrates to an office 365 group accommodate everything under that group.
Dave Kay commented
Being able to add 365 groups to DLs would minimise the number of groups and DLs I need. I'm having to duplicate DLs and 365 groups to give members the 365 functionality and also have an easy DL structure - so much time is wasted in checking memberships of many groups so nesting 365 groups in distribution lists would be a great admin time saving feature - we only have 150 tenants, can't imagine what it is like for the enterprise admins.
please vote for this feature.
We also want it, we have at least one group per project. It could make administrative tasks simpler
Projects -> Frontend Team -> CustomerA -> Dev
Projects -> Frontend Team -> CustomerA -> Contracting
Kyle Beckman commented
Just to add on to what Warren already said, we're in a similar situation. I work for a large public university and we have ~45K accounts in our Office 365 tenant at any given time give or take 5K depending on the time of year as we bring in new students over the Summer. (Feel free to reach our to our Premier TAM or directly to me if you want to discuss in more detail.)
We have an identity management system that is integrated with our HR and student information system (SIS) and automatically populates AD groups based on more criteria that we can count. Here are a couple of specific scenarios that we have:
Class rosters for Office 365 Groups. During registration periods, students can add/remove themselves from classes. This registration period finishes roughly a week or two into the Semester. As students add/remove themselves from classes, we have automation that interacts with the SIS database so groups in AD are automatically populated/updated. If we use an Office 365 Group for a class, we either have to depend on an instructor to update the Group or build additional automation to populate the group. We already have automation building AD groups that are synced into Azure AD. If I can add that security group to the Office 365 Group, students are added/removed as they change their schedules automatically.
Departmental Groups. Our departments have AD groups for their department based on status like faculty, staff, student, affiliate, etc. As users come and go from departments, we currently have automation that interfaces with our HR system to add/remove users from the AD groups. Nesting these AD security groups in the Office 365 group prevents a person from having to remember to add new employees or remove people as they transfer to new departments.
Warren Armitage commented
We are a provider of large scale enterprise systems for schools, 70k students, 11k faculty and 200k parents. We use much of the O365 suite, including Teams, Planner, Yammer, Forms, Sharepoint Online (~1000 sites) in addition to Exchange Online.
For access and identity management purpose we rely on core operational systems such as HR/Payroll, student management as the source for identity and use a broker service to pass these identities and meta data to premise AD, followed by synchronisation with Azure AD. Some 64k premise AD groups are created and maintained dynamically by the source application data. Nesting of Groups is required for example to maintain a whole of school group made up of the constituent class/subject groups. Staff based groups are maintained based on work location, role, organisation hierarchy. Without nested groups we must build a massive code base to maintain a flattened group structure.
O365 applications such as Yammer, O365 Groups, Sharepoint Online, Forms, PowerBI all either don’t support nested groups at all or do so quite inconsistently. Application of permissions in Sharepoint online or support for delegation for resource and equipment mailboxes in Exchange online are further examples.
Every other enterprise customer we have spoken to is affected by this lack of functionality and are all in the process of either buying additional third party tools or software development in response.
Jeremy Caney commented
I assume the goal here would be to allow Office 365 Groups to be placed inside other Office 365 Groups similar to how Distribution Lists can be nested in Exchange. So, for example, if I had a group named "Project ABC" I might want it to include groups "Project ABC Designers" and "Project ABC Developers". Everyone with access to either of the nested groups would automatically have access to the parent group, and notifications sent to the parent group would also be sent to members of the child groups.
Kayne Kreitzer commented
We have a structure set up with all DL's for each of our locations that we manage in the security industry. Each location has three base DL's (Standard, Mgmt, and Admin). Each of these then roll up to a DL for the location itself. Those then role up to Org Unit level and then to the company level. We have been wanting to convert our base DL's in each location to O365 Groups so that employees can take advantage of all the features available, but that would mean a huge headache of adding and managing the employee in the base O365 Group and then to the other DL's. We currently only add the employee to the base DL they belong to and then everything else is nested. Hope this explanation helps! And thank you for all of your hard work!!
Jared Pickerell - Troy Public Schools commented
This would be huge in making the move from my current DL structure to Office 365 Groups.
need to be able to nest on prem ad DL's in o365 groups. this is a must. cannot move forward with o365 groups without this. do we have a status ?
Chris R commented
This would be a big help. otherwise managing group memberships becomes a nightmare.
Surprised that this isn't possible at least in super structure. I understand that groups have independent site collections but this should be overcome.
Ronnie Z. commented
It seems to be possible to nest Office365 Groups or include them into Distribution Lists, BUT only by using PowerShell Commands. Please include this feature directly into the Admin Center.
Even being able to just put a O365 Group into a standard distribution group would be nice.
That way you can have
Area Distribution Group
-Location O365 Group
-Location O365 Group
-Location O365 Group
I would like to be able to view groups in a tree structure so I can collapse the list of groups that I'm not currently interested in. Application for school with lots of different classes and other groups.
This would be great! Currently I am part of 15 groups and have 15 shares mapped.
A nested group would allow me to have one share. They are built on SharePoint teamsites so it shouldn't be an issue whatsoever.
This is really essential for secretaries especially when dealing with groups of more than 10 people. Please work on making this function available.
This feature would definitely improve the product.
this would be awesome to have. I would definitely use this!!