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!
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!
Please add this functionality.
E Horstink commented
For good governance of the Office 365 groups this is essential functionality. It's unbelievable the Yammer Research Team is still considering this.
Yammer Research Team, This is essential for businesses that have a vast SharePoint environment that are also wanting to roll out Yammer functionality. For example, we have a client that has SharePoint Site for specific categories, in order to allow conversations announcements and updates about these categories, they are using Yammer. Without this functionality mentioned above, they either need to recreate a Yammer connected SharePoint site, Create an External Yammer Group with no O365 group, or create a Private Yammer Group with a duplicate group/SharePoint site.
This makes Yammer and O365 Administration much more complicated especially when you already have Security Groups with that same name. It results in three or more groups with the same name to have a SharePoint site, Yammer Group, and Mail enabled Security Group (for Yammer permissions).
Gergely Kurinyecz commented
This is essential because many organizations start using O365 first and later may use Yammer. E.g. when they are getting big enough to make sense to use it.
Our case is the same. We have just started to use (the New) Yammer, and created Communities, but realized that new Sharepoint sites have been created. This is confusing and unnecessary.
Please deliver it as soon as possible :D Thank you!
Youcef Bouzid commented
Of course, it is important. I have groups of scientists that use Teams to meet and they store different files and presentations there. We started using Yammer to collaborate with new visitors in a nonmeeting environment like Yammer, but our documents, presentations are not there and looks like we are using a brand new platform and not Office 365
Kirill Atamanov commented
hi! is it possible to connect a new Yammer group/community to an existing O365 group to have integration btw O365 and Yammer for the same group of participants?
My organisation is launching Yammer after having previously moved to O365 groups and teams. We also now use SharePoint for our intranet sites.
this creates an issue whereby we have Teams, and SharePoint set up as we want them but then Yammer comes along and results in a duplicate team that will never be used but is completely unnecessary and causes confusion.
Paul Sanderson commented
We have Office 365 SharePoint sites that were created prior to roll out of Yammer, by creating a 2nd site will add to the confusion and stop the adoption of Yammer