Forum Discussion
How to manage O365 Group membership through AD Security Groups and/or nested O365 Groups?
is there a plan to add this feature?
it is a deal braker for us, so i will really like to see it.
Microsoftthis is something we are investigating and hence do not have any further details nor timeline to share at this stage, FYI Mike McLean (OFFICE)
I wanted to add my voice to those requesting this feature. Ideally we would have one group that is leveraged across these different contexts. In particular our on-prem AD group that gets synced up as a Security Group. I'd like to either "add" O365 Groups to that group (the way you can add Teams to an O365 Group in concept) or else be able to create an O365 Group and then add then add the security group to that. I prefer the former, but the latter would work for me as well.
Please provide nesting (andI do not mean "add members") of security groups as a member of Office 365 Groups as soon as possible, and especially these synced from an on-premises AD.
Without, Office 365 Groups as well as MS Teams are not production ready even in an SMB environment, not to speak of "enterprise ready".
Please don't misunderstand me, I like the idea of Office 365 Groups and MS Teams due to their simplicity, but we can't stand an administration overhead and permissions auditing nightmare caused by a 1970s group membership concept.
Thank you very much!
- We really need security groups to define members of O365 groups.... reason is simple logic: I would assume everyone would agree that there are a smaller number of expected security groups in comparison to the expected number of Office 365 groups...especially if we are going to be making O365 groups for small tasks/projects with the same list of members over and over again. O365 groups without relying on pre-set groups of individuals (security groups) is simply unusable at scale. For example - if you have 50 O365 groups for 50 different little projects and you hire more team member that will access these projects...you are stuck editing 50 groups instead of tossing that new person into one security group. The only way this works is powershell scripting - but it looks like you are at least partially adding O365 groups to prevent scripting (auto-creation of resources.) Right now it seems like O365 groups are in Chaos Mode...
I would like to add my voice to the mix. We need the ability to add an active directory domain security group as a member of an Office 365 group. When we onboard new employees we copy the AD account of an existing user in the same role so the new employee automatically gets added to the same groups as his coworkers in that role. We can't easily identify and add the new employee to all of the Office 365 groups that he may need to be a member of. I would be fine with doing this using PowerShell (add the object ID of the security group to the Office 365 group or some such) if that's what would be needed. By the way, we are a gold partner so if this is being discussed in a forum or in preview under NDA sign me up.
Hey all... we've just added a solution in our product that allows you to associate an O365 Group with one or more AD Security groups and have membership synced daily. PM me if you want more info on the apporach we used as I don't want to market all over this thread.
Hi - Can you kindly elaborate.
Regards,
Chiranjib
I noticed today that it is possible to add an Office 365 group into a SharePoint group - but would that expand the group members at that time?
If so, that would mean that if a new user was added to the 365 group later, they would not get permissions in SharePoint.
Is my understanding correct?
- Just to add - I've done some testing, and what I've seen is this:
Create 365 group - add a single user 'Rob'.
Add that 365 group to the 'Members' group of a different SharePoint site.
Check permissions for 'Rob' on that SharePoint site - shows as having permissions via 'Members' group.
Add user 'Mandy' to same 365 group
Check permissions for 'Mandy' on the SharePoint site - shows as having permissions via 'Members' group
Remove 'Mandy' from 365 group
Check permissions for 'Mandy' on the SharePoint site - shows as having no permissions.
Therefore, use of 365 Groups to control access to SharePoint sites works as expected, and it respects group membership changes.- AFAIK, adding Groups to SPO sites has been there for a while
Any news on this highly requested feature, cfiessinger?
- cfiessinger
we don't have any update to share at this stage. FYI Mike McLean (OFFICE)
Just wanted to add our request for this.
Not being able to use our existing AD groups to maintain SPO membership for site is terrible.
60,000 users that have existing AD security groups for business units already, is not something I want to have to replicate or update in 2 locations.
Cheers
