Feedback by UserVoice

How can we improve Office 365 Groups?

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

2,260 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    108 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        My scenario is I want emails sent to channels. Via email address. - so a DL with the O365 group nested and Channel Email. So then they can discuss the email as a team in Channel in Teams and reply from the group mailbox.

      • Richard commented  ·   ·  Flag as inappropriate

        Crazy that we cant do this already - Nested groups makes management SO MUCH EASIER! As one example, we should be able to add a GROUP as a member of a TEAM in MS Teams, so that all we have to do is add a new employee to their one primary group and they then get all permissions and abilities as needed, including get auto-added to a given TEAM

      • Anonymous commented  ·   ·  Flag as inappropriate

        Yes, please. Nested groups are a very efficient way of managing groups when a hierarchy exists, such as organizational structure. Thank you

      • Anikke commented  ·   ·  Flag as inappropriate

        What @Matt Shafer said. Absolutely, and completely obvious. O365 groups also shouldn't need an owner. If they are populated by a script or nested, an owner is inappropriate.

      • Matt Shafer commented  ·   ·  Flag as inappropriate

        I still don't understand why you need to know more. This is a very simple concept. Office 365 groups are an evolution of Distribution lists. All Office365 functions are tied to this concept, and in some scenarios, the DL portion of the O365 group needs to be nested.

        Real-world use case:
        All staff list. Since all staff will be in a department group (generally office365 so it has Teams, yammer, etc...) we then nest those department groups under an "All Staff" group. The recent addition of company wide teams makes this even more needed to control that membership.

      • Caleb commented  ·   ·  Flag as inappropriate

        tell you more...? what more do you need to know after 4 years and this being the top requested idea for O365 groups?

      • Jenna Bonner commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        Nesting groups will allow O365 group owners to work smarter, not harder. This will definitely impact efficiency within teams and inter-working groups.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The ability to nest groups is critical - and seems quite easy to add, please just do it!

      • Gavin Bollard commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        Just do it - it is a pain in the projects, that it is not possible ot nest AD Groups in Universal groups.

      ← Previous 1 3 4 5 6

      Feedback and Knowledge Base