We have a business requirement to ensure that only management approved users can be added to certain "secret" Yammer groups. Is there a way to prevent a Yammer group owner from accidentally adding a non-approved user to a group?
Here is an example.
I created a Yammer group called ProjectCondor. Only the following people approved by management are allowed to have access to this ProjectCondor Yammer group: Aaron, Brett, & Bart. The Yammer group owner, Aaron, attempts to add Sue to the Yammer group. Since Sue has not been approved by management, a mechanism should prevent Aaron from adding Sue to the Yammer group.
The mechanism in this case would ideally be an AAD group because we already have an internal approval process for AAD group membership requests. On about to add a member to a Yammer group, Yammer checks whether there is an associated AAD group tied to the Yammer group. If there is, it checks whether the person being added to the Yammer group is listed in the AAD group.
A tool then to control membership to the ProjectCondor Yammer group against an AAD group would be ideal where the business owner only needs to manage their AAD group such that new and removed AAD group members are subsequently added and removed from the Yammer group automatically.
Could Flow be used to get management approval for Yammer group membership?
Today, each Yammer group owner would have to manually check the AAD group before adding a member and routinely review AAD group membership to ensure members are promptly removed from the Yammer group.
After reading what I wrote, I know it sounds convoluted, but when attempting to use O365 for sensitive information and protect us from ourselves, it is not always straight forward. I see a similar use case existing for other O365 workloads. In fact, imagine using AAD dynamic groups to drive a division or department's Yammer group or SharePoint site.