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.
In the past 18 months our school have bought into Teams massively and in addition to remote learning we use it for student homework and a whole host of staff-side applications. This would be such an excellent feature to have. It would really streamline the management of our user's permissions. Trying to do it manually is sooo time consuming! Can it jump up the queue please :)
Radoslav Kissiov commented
First it was scheduled for June 2021 and now delayed for over 1 year.
Is it even being worked on or in the roadmap, in 2022 it will probably be delayed until 2023.
There is alot of manual management without this feature and seems no one is looking into it from MS.
Can we get an update on the current status and why this was delayed so much when there is so much demand for it?
It seems it was reposted as Feature ID: 83113 Microsoft 365 admin center: M365 Groups - Group Driven Membership Management (https://www.microsoft.com/ja-jp/microsoft-365/roadmap?filters=In%20development&searchterms=83113)
Relese schedule for 50002 was June CY2021. 83113 is December CY2022. 18 months delay?
Lukasz Biegus commented
Come on MS, all we are essentially asking for a simple ability to add security groups to Office 365 groups, so that we can do proper role-based access control in Teams too.
Michael Voegtline commented
Can someone from Microsoft please provide an update on this effort?
Steve Colegrove commented
Yes, I was also disappointed to see 50002 disappear. My company is heavily invested in using AD security groups for resource access, which includes Teams memberships since there's data to be accessed within a Team. I've been watching 50002 for over a year because it would greatly simplify our ability to provision access to Teams and M365 Groups. Without this, we have to use a complicated custom PowerShell script which keeps Teams/M365 Group memberships in lockstep with memberships of a companion AD security group.
Feature ID: 50002 on their roadmap is disappeared. I believe that was the feature I need. What happened?
Brian King commented
I think Teams membership is relying on the underlying Microsoft 365 Groups technology, if I understand it right. However, it doesn't change the fact that those of us with AAD security groups have a lot invested in creating & maintaining them, and continue to need them in other areas. It would be a huge time saver if we could use those same groups to control Teams membership.
Konstantins Sablukovs commented
3 years to implement this feature - it is long. There is so much demand for it. Every organisation with AD and AAD needs it. Interesting is there any indication when it will be get in to development?
Alex Janes commented
It feels like this shouldn't be left on the back burner for 3 years. Can we get an update?
Acksios Kim commented
Any update on this?
Auke Bergsma - Motion10 commented
it works in SharePoint for 20 years now so how difficult can it be?
Josef Christen commented
Das ist wirklich eine wichtige Sache.
Peter Thomas commented
Any progress? This is such a shame that it is not available.
Jackson Wages commented
Any update on this? it would be amazingly useful.
It is a good idea to know that this feature is on the roadmap.
It will surely facilitate management of MS Teams.
Thanks in advance
@Anonymous, you said it is on the roadmap. https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=50002
So I guess we have to wait till it is developed. Shouting won't work and doesn't make it go faster ;)
Is there an update?
Robert Winther commented
Such a basic feature to be missing from a product like this? Makes migration to Teams all the more cumbersome.
Shaun Wells commented
No update in 2 years on this, can someone from MS please provide an update.