connect yammer group to existing office 365 group
Upon creation of a yammer group I would like the option to connect it to an existing Office 365 group. Also have the choice of which feed to be used for discussions. Yammer or Outlook. A bonus would be if there's a way of changing it over timer if the usage or demands changes.
This isn’t currently prioritized, but we’re considering it. Feel free to tell us more about why this would be important to you – it’s helpful for us to have context as we discuss it. Thank you!
Randy Slavey commented
We have been using Teams and the SharePoint hub site for some time. I was researching using Yammer in place of the hub site, but if we cannot use existing O365 Groups, there's no need to research further. Having two O365 groups for one team will cause more confusion than it's worth.
Fingers crossed it will be addressed at Ignite next month.
Is there an ETA on this if it’s being considered for implementation?
We have existing Yammer group (non MS Group based) that we would like to keep during the migration of our intranet, therefore we would need the possibility to use those existing Yammer group while creating new MS Group based Yammer groups.
Ian Williams commented
The fact that this is not higher on your list of priorities is mind-numbing. You're pushing this interconnected ecosystem in O365 yet tying a resource to an existing group seems unimportant to you.
If we create a group through Teams and then realize we want the same group to have a Yammer group, we have to create a new, second group...
Since we started our Yammer communities, we did not have them O365 group enabled. Now that we are having more adoption, we would like to make some of the previous Yammer groups O365 groups so that we can make them dynamic. We don't want to delete as to lose the adoption that we currently have in these groups. We also don't want the manual work behind having to add every person in each region to the group.
For us it is a big blocker that we cannot do this. We want to move our existing Yammer communities over to using Office 365 Groups and all of the extra benefits they provide. They already have mature SharePoint sites that we can simply Groupify. We do not want to close the existing vibrant Yammer communities down and create new ones. Why can we not connect the Yammer Group and use the shared Office 365 Group?
This seems like a logical thing to me. When you create a new Planner, you have the option of linking to an existing O365 group. And a single O365 group can have multiple planners. Why not with Yammer as well?
A team has already got an O365 TeamSite and now need a Yammer group. They don't want 2 TeamSites. How do they achieve this?
A team would like to have multiple Yammer groups without having multiple teamsites.
Please bump this up your priority list!
Now that you have added file storage in Sharepoint, as default, to Yammer connected groups you need to consider the businesses using Yammer before O365 Groups and Teams came on the scene. Unconnected Yammer groups can be added to Teams via a tab but the files are not shared between the distinct groups. Being able to connect an unconnected Yammer group from the past to a modern group created by Teams would complete the process and files would be consistently shared among both. This would also help with any migration to Teams if you ever plan to phase out Yammer in the future.
Wayne Tu commented
+1. It is really annoying and confusing to get multiple groups created when a team is on teams/sharepoint/yammer.
This would be enormously helpful - and IMHO would go a long way to helping to integrate the M365 product suite by reducing confusion about which tool to use for what activity and helping to bridge generational divides that arise from habitual tool use (aka help the old folks that still use email to talk to the young folks that live on social media).
Really hopeing we here somthing on this soon. It is really needed.
Anwesh Gangula commented
All the other apps like SharePoint, One-note, Power BI Service etc., are linked to Office 365 groups. This makes it easy to provide/manage access to all of these. So Adding Yammer into this list would make it easy to manage.
It;s pretty obvious why you should want this. Lot's of customer use Groups and Teams, less use Yammer in the way you intend it. Now, we want to help our customers moving towards the Microsoft inner/outer loop vision but we can't because we can't connect a new Yammer group to an existing Office 365 Group or Team.
It's great to see all the services now linked to a single Office 365 group, can't see us using Yammer until this can also be linked. Without this it just feels like duplication and double admin!
A recent status would also be nice.
I don't want to create a duplicated group. I have a managers group that I want to use in Yammer. If I try to create a Managers group on Yammer it will duplicate everything sharepoint, etc. I don't want that. I think the Yammer-office 365 is a great integration but one way street is not a good idea
Benoit Fournier commented
Any update? Last status is more than a yeay old.
We have plenty of 365 groups existing. I would like to increase Yammer usage by intergrate it to SharePoints sites of those groups. It means generate Yammer groups and link them to O365 groups. So we can have a social aspect without leaving SharePoint.
Most large organisations I know prefer to prevent group creation and manage it by request, but for Yammer, staff can simply carry on creating Yammer only groups. I would prefer to use O365 connected groups and deal with requests through an approval process. So having a way of linking all the exisiting Yammer only groups to a O365 groups would be essential too.