Forum Discussion
Solved
Use AD Synced Group for Teams Membership
We have synced a bunch of security groups from our AD envirement into the Azure AD.
As an example we have a group called GG_DEP_IT which contains all the IT members.
This group is used OnPrem to delegate folder permission, application access and more.
Now we wanna built a Teams-Group for our IT-Departmen (and many more) this only works with Microsoft 365 Group.
Until now I've not found a way to add all members or the group "GG_DEP_IT" to an Microsoft 365 group.
Since we manage all the groups on prem, the membership there is correct and clean.
What would be the correct way to create a teams-channels for all department by using the existing groups?
The Dynamic-Groups does not work, since the department is not always correct in the AD-Attribute.
Is there a way to extract the members of each group into a new group for this purpose?
What we would like to avoid is have to take care of two idependent groups manually, since a bunch of automatisation already clean up the onprem groups.
- You can "add" a group as a member of M365 Group/Team, but that's a one-time operation and only the current membership of the group will be added, further changes will not get reflected. That said Microsoft is supposedly working on "nesting" scenarios, so this should be supported in the future.
Until then, using a dynamic membership rule or an automated script/runbook/flow that periodically "copies" the membership is your best option.
This has changed--you can use the code in the below link from MS's page to dynamically populate Teams membership:
- You can "add" a group as a member of M365 Group/Team, but that's a one-time operation and only the current membership of the group will be added, further changes will not get reflected. That said Microsoft is supposedly working on "nesting" scenarios, so this should be supported in the future.
Until then, using a dynamic membership rule or an automated script/runbook/flow that periodically "copies" the membership is your best option.Hi VasilMichev does Microsoft have any update on this? 'Microsoft is supposedly working on "nesting" scenarios, so this should be supported in the future.'
Thanks!Hi VasilMichev and Kyuma90 have you by any chance noticed this behaviour being different on the New Teams? We've noticed instances where classic teams is detecting an AD group (you start typing and it comes up as an option to select), but then new teams does not seem to be detecting the same AD group (you start typing and it says "we couldn't find any matches").
