When granting access a Security group or Distribution list to a Team. Changes to the security groups/DL does not apply.
When granting access a Security group or Distribution list to a Team. Changes to the security groups/DL does not apply. If a user leaves the company or if we have new users, it is a manual process to add or remove them from a Team. Since we can select a Security group or Distribution list, changes to either should be reflected on the Team members.
This feature request is still working its way through the backlog queue.
Please! This would be very useful and from a risk/compliance perspective would give me peace of mind!
This is definitely needed to simplify the management of groups and teams through an enterprise size organisation.
Jason Botts commented
Let's move this from the backlog to the front burner! We need this capability.
Stephan G commented
Most important feature if you want IT guys to like the cloud ;)
We can script all features - but this is a must feature - is it that compute intensive or what is the problem about nested groups?
This seems so evident, please add this functionnality
Matthias Fleschütz commented
Fully agree with @Marc
On the one hand I like ideas of this cloudy, swishy-swooshy, team-self-administration, but it's just one part of the story.
We need it to ensure an enterprise level administration. We managed users with groups synchronized from OnPremise Active Directory and not only Office365 Groups. A lot of medium and big company works in hybrid configuration and manage users and rights with OnPrem security groups, please don't forget that !
This needs to be basic functionality on Teams. Please implement this as soon as possible.
Seriously - is anybody on the Teams team (ahem) working? Between this BASIC FUNCTIONALITY and the absolute GARBAGE .msi, it appears MS is *trying* to make this fail. Get to work on things that matter.
Any updates on this? it would be helpful. Also can we have the ability to add a security group to a MS Team Site via the Teams Admin portal.
How has this been pushed from expected Q4 2019 to Q1 2021?! Makes you doubt that they're actually developing the feature at all when they just casually slap on another year to the release date after the last expected one passes. I was waiting on this to roll out Teams.. but I guess waiting on Microsoft to deliver anything is an exercise in futility.
Phil P commented
Any updates on this feature request?
I see this has now been pushed to Q1 2021!
Come on MS this is ridiculous!
Olivier JEGADEN commented
The following update should allow to drive O365 Group membership via a Security Group:
Would it work for Security Groups synced from local AD to Azure?
Gabe Smith commented
There is a PowerShell workaround for those that need a stop gap solution.
John Mason commented
This is a stupid omission! Lets get this sorted please MS! You have created a solution for team working but ignore the fact people use Groups to setup a team of people to provide them acecss to tools etc :|
Lester Waters commented
How on earth could you not include groups into Teams for membership?!? Shocking omission to say the least.
Glenn Cochran commented
backlog queue must be a very long road to wind through. It is crazy that the integration with the rest of the microsoft infrastructure is so primitive...
Is this feature on the roadmap, is there any indication of when this might be introduced?
Kazuya Darklight commented
This is so obviously necessary, I don't understand how its still on the back burner. I would honestly be surprised if Teams usage didn't spike significantly after this was implemented and word got out.