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.
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.
John Dale commented
Ditto what Thea asked.
Thea DiSalvo commented
The last response I see from MS was over a year ago. Can we get an update, my organization was scheduled to deploy teams to our users this week.
This item should not be on the backlog for over a year. Not only is it tedious to manage (and can be overwhelming depending on how many Teams are in place with group membership), but there is almost always someone who is missing out or should have been included. That can affect their job performance.
Please have this done soon. It is quite tedious to manually check every single Teams to change or switch owners or members.
Is there any update on this? Coming from a fairly large company who is seriously considering switching completely to Teams this is a MUST HAVE. This gets outrageous to try and manage when you have more than 10 Teams.
Matthias Landowski commented
Yes, Please!!! useful!!!
Please go on with this. that helps a lot.
Rafael Bebelacqua commented
Please do add this.