Forum Discussion
Solved
Nesting Groups
Am I missing something or is it not possible currently to nest O365 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.
This question comes up very commonly for people who are thinking about migrating from distribution groups where nesting is supported and used extensively. Although the two constructs "Groups", one is used to address sets of people and other mail-enabled recipients (like public folders) while the other can be used in the same manner (but only user accounts) but its more important role is as an access mechanism to resources such as the calendar, notebook, document library, Power BI workspace, and so on. Because Office 365 Groups are used as an access mechanism, nesting becomes a lot more difficult than when you simply have to resolve the address list for a message and figure out how to route the various copies. It might be that nesting is supported in the future, but for now it's not to make things simpler all round. Simplicity is good as complexity invariably leads to support issues etc. etc. etc.
We use nested AD groups for file security and for email, so I'm not sure what sort of issues you see arising from nesting groups for the purpose of resource allocation and distribution here.
When you have hundreds or thousands of users to manage, keeping non-hierarchical groups in sync is a real headache.
- Would be nice, permissions aside, to at least be able to have a groups homepage where people can see groups (particularly public ones) automatically organized into a heirarchy based upon a tag used to specify where the group resides. This would require you to allow us to use tags or categorization during group creation. A little metadata please?
