Please leave us feedback!! We would LOVE to hear from you!!

[rarajase]

Hello!!

Have you had a chance to download and try out the GMM code in this open source?

The GMM tool makes it easy to manage a large group roster by taking advantage of existing security groups and/or smaller groups kept up to date by teams within the larger org. The tool essentially takes security groups or other Microsoft 365 Groups as source group(s), produces an aggregated flat-list membership roster of the destination Microsoft 365 Group based on the source groups and continues to keep the destination group roster in sync with the source groups.

We are standing by to hear from you!! We would LOVE to hear feedback on what worked, what challenges you are facing or any other input you have! Please drop us a note on this discussion forum or send us an email at GMMSupport@service.microsoft.com.

Looking forward to hearing back from you,
Regards,
Group Membership Management team

[sellarsm1]

When an Office 365 group is set to dynamic, the membership management UI is suppressed in Teams. Could a similar flag be introduced for scenarios like this so that Teams owners don't get confused or frustrated when changes they make don't 'stick'?
Alternatively, if there were more multi-value attributes available in AzureAD, a routine like this could simply add tags that could drive membership in a dynamic group.
Thanks, Martin

[rarajase]

Hi, Thank you for your comment Martin! Can you please provide a little more detail around your experience with GMM, your company, use case scenarios? Were you able to successfully deploy and use this tool? We agree closing the membership management in application end points is a feature that would be greatly beneficial. But, not having an attribute in AAD to leverage for this has been slowing this down. The team will continue to explore options, but, one thing we have done is ask group owners update the title to indicate that the membership is being managed by admin and to reach out to group owners with changes.

[sellarsm1]

Hi, to be Frank, I haven’t tried the GMM tool yet, I simply read about it in the O365 CAB forum. In our environment, we have many (>1,000) groups whose membership is managed programmatically based on attributes, hierarchy , etc and we have a mechanism to explicitly include ad hoc members that might not otherwise match the filter. These groups are synced to AzureAD, EXO and SPO and used as distribution lists, security groups or both. As our adoption of Teams expands, I’m confident some Teams owners will want to base their membership on these groups. If we could establish a multi valued attribute (either directly in AAD or as an extension attribute) we could use our existing group management mechanisms and simply have them set tags that could be used in O365 groups dynamic rules to mange the Teams membership). This approach would have the added benefit of suppressing membership management in the Teams UI. Martin

…

________________________________ From: rarajase ***@***.***> Sent: Wednesday, March 17, 2021 11:26:28 AM To: microsoftgraph/group-membership-management ***@***.***> Cc: Sellars, Martin ***@***.***>; Comment ***@***.***> Subject: Re: [microsoftgraph/group-membership-management] Please leave us feedback!! We would LOVE to hear from you!! (#9) [Use CAUTION when opening links/attachments] Hi, Thank you for your comment Martin! Can you please provide a little more detail around your experience with GMM, your company, use case scenarios? Were you able to successfully deploy and use this tool? We agree closing the membership management in application end points is a feature that would be greatly beneficial. But, not having an attribute in AAD to leverage for this has been slowing this down. The team will continue to explore options, but, one thing we have done is ask group owners update the title to indicate that the membership is being managed by admin and to reach out to group owners with changes. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoftgraph%2Fgroup-membership-management%2Fdiscussions%2F9%23discussioncomment-494270&data=04%7C01%7Cmartin.sellars%40bms.com%7Ce2cfb1f595504f93c3e208d8e9590947%7C71e34cb83a564fd5a2594acadab6e4ac%7C0%7C0%7C637515915904402126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BDAhUMeiiqF2diIcjfNbgUAYft9n6%2FlBysfwgRLXCfc%3D&reserved=0>, or unsubscribe<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATIVM6THDVXO7ZLRJONYG23TEDC2JANCNFSM4Y4RPJBA&data=04%7C01%7Cmartin.sellars%40bms.com%7Ce2cfb1f595504f93c3e208d8e9590947%7C71e34cb83a564fd5a2594acadab6e4ac%7C0%7C0%7C637515915904412121%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rj4LZqe3ANDpYupxrjNDK4KmPRjZ6st%2BPsO5IfJu7vk%3D&reserved=0>.

________________________________ This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

[gcmlpfaltaher]

This repo doesn't seem to be maintained by MS, are there plans to update this repo or roadmap plans to introduce this sort of functionality as a feature released by MS?

[DG-RMD]

Would very much love to hear an answer to this, the solution has many caveats to overcome in its current state

[bkinnan2]

Is the repo and code still being actively maintained and updated? It looks like there have been no contributions to it since last year.

If not, is there a new program or offering coming out to fill this gap?

[alrios-ms]

Hi @bkinnan2, it is actively maintained, we are working on a major change for the installation process as per the feedback we got it was a very complex process, we are expecting to update the repo with a new installation process and code very soon.