We are using groups for a programm organization with several projects and streams. We want to have a central place for all our documents, so we are using only one O365 Group (SharePoint Site). However for the discussions in yammer, we want to have indivdual groups for each project or also cross project topics.
In the new setting, I would get a new O365 group for each new yammer group. (As it happes if I create a new Planner btw)
However this is very confusing for the users, as new groups (and SharePoint Sites) will be popping up for each new communication channel...
I strongly belive that a 1:1 relationship with yammer (light weight) and groups (heavy weight) is the wrong approach!
Hi Erich, Our primary use case was to have the group and the related content have similar membership and permissions model to make the management of the group and the content easier. Thank you for describing your use case. We will take that into account for the next iteration of this feature and see if we can address this in a way that doesn't confuse our users.
At the moment we are using the discussion board app (together with mentions) in Sharepoint classic TeamSites. Since the introduction of Sharepoint Modern TeamSites we no longer have discussion boards with mentions so we are looking at Yammer as a replacement.
Since Yammer groups hold 'conversations' which is more then just discussions how would you approach this through Yammer (having a solid overview of all ongoing / active / non decided / ... discussions is a crucial requirement)