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 de...
- 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.
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.
Until then, using a dynamic membership rule or an automated script/runbook/flow that periodically "copies" the membership is your best option.
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").
