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.
Wade Baugher commented
This is a vital missing feature. Please promote this issue if possible.
Come on MS, aren't you all about federation? This should have been part of the initial release. Now I have to have two separately managed groups, one on AAD and one in AD.
What is the latest update? When is Microsoft planning to implement this? Any information more than" on the backlog" is appreciated.
Thomas Hansen commented
What is the latest update, when can we expect to have this functionality implemented?
Teams roll out to our organisation are dependent on the option to manage team members using group memberships.
Mats Olsson commented
Can any Admin respond what the status is, no response on 4,5 month. From my perspective, calling this a "feature request" is strange. This is "bread & butter", should have been there from day 1.
Bogdan Manolache commented
I think I have just duplicated this request :(
Joost van der Linden commented
I agree this is a real must have for many larger companies. We need both of them. Flexible and dynamic teams where a projectleader manages the members can be done from the Office 365 Group. And we need more static teams (departments) to be managed centrally from AAD or Active Directory on-prem using security groups.
Anikke Bukowski commented
Can this be given a higher priority please? Being unable to manage the access rights to Teams with AD Groups is a show stopper, full stop. We would completely lose control of access management if we used user-managed office 365 groups.
Peter Braun commented
Can this please be given a higher priority? We need to be able to manage team members via group memberships. Thanks for your hard work guys!
This functionality is really important for us since all our access to systems are managed through security groups. Having to update on two places is waist of everybodys time.
Tina H. commented
When will this feature be released? It is vital to managing our Teams.
Kevin S. commented
We are a hybrid exchange/ad environment and would like to be able to control the memberships of a local Security group that when synced to the cloud can become an Office 365 Group or Team. This would allow our on premises provisioning and user management system to automatically manage these services.
Repeated below for emphasis. This is really essential to basic administration. Manage by groups, NOT by users. This has been basic functionality since NT 3.1 and having to manually keep them in sync is a recipe for disaster.
"How does this get escalated to the top of the backlog? This is basic functionality that should be a requirement for the product to be considered viable. Group nesting should work by default even for synchroniced groups from on premise or Azure AD groups."
Matt Chapman commented
How does this get escalated to the top of the backlog? This is basic functionality that should be a requirement for the product to be considered viable. Group nesting should work by default even for synchroniced groups from on premise or Azure AD groups.
Update on this? How far in the backlog is this?
Lennard Kuijten commented
You can now make the teams membership dynamic.
Create the Team.
Set the membership type to dynamic in Azure AD and create an dynamic membership rule.
Kevin H. commented
this is a must have
This is basic to be able to meet compliance requirements, what is the ETA for implementation
Great this would save so much time, please implement!
This would save so much time, please implement!