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!
Benoit Fournier commented
Any update on that feature? I need to be able to control the creation process by creating the SharePoint site first then connect it to a group using Yammer for conversations. I can do that for M365 Groups or Teams group but not Yammer.
Mike Creel commented
Very anxious to have the ability to Yamm-ify an existing group. Many of our potential communities have existing Groups; being able to maintain membership once, as well as to have a common SharePoint site sitting behind Yammer, Teams and the Group would be very helpful. Consider it a triple play, trifecta, or perhaps the Triple Crown!
Some time ago we created a SharePoint site for specific subject matter within our company. We specified all the members, permissions, etc., and now our company wants to move toward Yammer. We have a lot of content in that SharePoint site, and I want to yammer about topics that are related to that SharePoint site. But if I create a new Yammer group, it will be associated to a different SharePoint site. How should I direct users who will be in the new Yammer group to view site resources in the original SharePoint site?
Marcel Sjardijn commented
Cant believe this simple feature isnt here yet! Please add this soon!
Seriously, You ask for reasons, why this could be useful?
MS is promoting Yammer as part of the whole M365 ecosystem as has happened recently with the announcements about Microsoft Viva. If we can't use existing groups for Yammer then you are once more responsible for the ever growing number of M365 groups which makes it rather tedious to administer the M365 services.
Eric R. commented
We currently use Microsoft365 Groups which our teams use for Sharepoint and Teams. We would like to adopt yammer but I am not duplicating our groups just to have Yammer. We need to be able to launch a yammer community based on our existing groups. You did this for Teams, why not yammer?
Guillermo Bas commented
This would help a lot with 365 groups sprawl as currently you can have 2 groups for the same purpose (e.g. Team communications) which causes two SharePoint sites behind the scenes and a lot of confusion for users to understand which file store they should use in each case.
Comms story is clear and separate and not all Yammer groups will have Teams associated but for sure many of them will as Teams comms are different form Yammer comms and any many cases both are necessary.
Please work on this!
Please prioritize this - existing O365 groups are the basis for targeting any communications in a large organization. Links nicely with Sharepoint audiences & Teams, but not with Yammer -> no logic in this.
Shankar Narayanan Kuppuswamy commented
Please prioritize this
Yes please, we should be able to add Group as Member not just individual users so it will be easy to add or remove a user when the employee joins or leaves the company otherwise we have to do it in different places
UAE Angel Investors
Grégory LASSERRE commented
Agree with the request, Too many groups for same group of people in order to have all features.
Rob Hardman commented
Bump! Feature still not available, lack of feature still causing unnecessary 365 Group sprawlage...
Group bloat is already bad enough. We dont need more duplicate groups with various SP sites. You can do it with Teams, I dont understand why you would not make it happen with Yammer and why you think we need to convince you that this is needed
Brandon Bezaire commented
We have some solid use cases for Yammer internally, but this missing feature is a non-starter.
Nobody wants to manage 100's of duplicate groups.
If Teams can be added after the fact, I see no reason why Yammer can't be added either.
We should have ability to reuse existing O365 Groups to Yammer. Otherwise lot of repeated groups in O365 environment and people are getting confused which one is linked to Yammer and which is linked to SharePoint. A big mess it is to deal wil
Stop considering this and make it happen! With new yammer, integration app in Teams if you dont limit group creation and isnt aware that this isnt working already groups are going to be a mess. we need to be able to add Yammer to a group just as we can add Teams to an existing group. otherwise i have to block yammer completely. but maybe that is the way you are headed?
We were appalled that this wasn't already a feature.
I would urge you to please prioritize this. Our carefully managed 365 groups structure will be overrun by duplicate groups with random number strings and make it a nightmare to moderate.
Please, please, prioritize this. This should have already been a feature long ago when Teams was made. Thank you!
this is needed asap!
We have existing tools and governance for creating SharePoint sites and O365 Groups. For consistency, attaching a Yammer Group in the same manner we attach Teams to O365 Groups after site/group creation would provide consistency of governance & administration. Our SPO site & Teams provisioning scripts have the requisite organisational branding & customisation and creating sites/groups from Yammer in the current method is breaking our governance. We want O365-connected Yammer Groups, but we also want it done consistently!