Add security groups to an Office365 group with > 400 members
I like to add a security group to an Offic365 group with more than 400 members (440). It seems to work in the interface, but de users arn't added. I like this to share date with all my 440 collegues.
Thanks for all the feedback on this item. We’ve started initial thinking and investigations on possible designs for this feature.
As an Office 365 Educational client, much of what John S below states I agree with, but from the management of a directory structure in a school district environment. A nesting/hierarchical groups structure is much easier to manage and maintain. I want the functionality that security groups provide, but also of what Office 365 Groups/Teams has to offer. I don't want to have to choose between them or manage each group in duplicate so that I can do everything that we need/want to use groups for.
John Shkolnik commented
His is not the only use case. I have a hierarchical set of on-prem AD groups which are meant to map to O365 groups.
There are two key overarching goals:
1. To onboard and manage personnel with least amount of overhead and widest propagation for both security and email distributions.
a. Management should be bottom up, meaning a team should control its own members.
2. To foster communication and collaboration within our practice.
1. As a product owner, I want a single team member change to grant access to all relevant resources and subscribe to all relevant distribution lists.
a. At my firm, the widest propagation is via US domain. We’ve set up universal domain groups nested similar to a chart I can't seem to attach to this post but have emailed to you guys before.
2. As a product developer, I want to ask every developer working for Partner1 if they’ve encountered a problem I’m dealing with.
a. Because we can’t do dynamic domain groups, we have an “alternate” vertical domain group hierarchy for the topics. As an example, ProductA (BIZ) is simultaneously a member of ProductA and Partner1 (BIZ). Partner1 (BIZ) rolls up to FinTech (BIZ).
b. We’ve created O365 groups to parallel the nested domain groups. The problem is that adding the FinTech QA domain group as a member of the parallel FinTech QA O365 group would expand all the members and break the link to the domain group hierarchy.
3. As a QA tester, I want to have chat channels, shared files, and other shared resources across all Fintech QA.
a. Teams is very isolating. We want our teams socializing, cross-pollinating, and collaborating rather than evolving apart from each other and – almost certainly – reinventing wheels.
4. As an account manager, I expect product teams to collaborate closely when dealing with a client licensing multiple products.
5. As a partner, I want to have chat channels, shared files, and other shared resources across applicable to my entire group as well as a workspace for group-level reporting.
What's the status on this? Really need it
No News ?