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!
I needed this last week. Why is it so complicated just to do what it promises on the tin?
Kyle Tate, MSIT commented
I agree yammer should be able to be created from an existing group. Please do this.
Forever everyone else complaining about users creating groups, a quick message. If my users create a yammer group, it DOES NOT create a team, sharepoint, etc because I properly configured my tenant to only only ADMINS that are part of a security group the ability to create groups.
This means only admins can make teams, and it allows users to create their own yammer groups. Any yammer groups created by admin get the full functionality that an O365 group.
Phil Maynard commented
As we're maturing in our use of Office 365 Groups, we have a number of Groups initially set up with Outlook at the primary conversation space that we'd now like to move to Yammer. To fully embrace the Communication options with Office 365 Groups, the ability to switch the preferred communication channel used for a unified Group without re-creating it is essential - especially as we also have a number of email distribution lists that we want to move to Yammer
As others have already commented, given the communication from Microsoft on inner and outer circles it seems natural that we would be able to create a Yammer group from an existing O365 group like we can for Teams.
As SharePoint Online is intended to host our intranet, this will be the starting point of creating anything new so we don't want to send our users off to Yammer which has a completely different look and feel. Rather we would want to create a site design for e.g. a "Community" which will then provision a Yammer group and insert a Yammer webpart on the site.
A. Fahim Ayub commented
Just like Planner, Teams, and Office 365 Groups can be linked, I will Yammer could too. We know Teams and Yammer can work together for better discovery. Why should we recreate the same group and add the same number of members for each group? Unless there is reason, why not to, I'd give it a +1.
Maria Tusak commented
Having many old sites/new sites/ sites created in teams /Sites created in yammer /sites created in sharepoint /sites created via Poweshell
we are currently trying to unify the user experience. Yammer is one of our standards and currently the only thing that forces me to migrate the content of my old sites manualy, as I cannot hit the "connect to a new O365group" button if I am not able to add Yammer later on!
It's important because it is creating copies of SharePoint groups that are already existing and that people are already using.
We need this urgently. We are a very large organization and it creates chaos to have multiple Office 365 groups with the same name. Currently, if I create a new Yammer group it automatically creates a new SharePoint Site, SharePoint Document Library, etc. with the same Name. Unfortunately, this serves me no purpose and becomes incredibly confusing for our users because we already have a functioning SharePoint Site (Group), SharePoint Document Library etc within Office 365 that was created prior to creating the Yammer group.
The confusion is only amplified by the fact that you cannot remove the 'Office 365 Resources' that appear on the Yammer group page. These automatically link to the unused SharePoint Site, SharePoint Document Library, and SharePoint Planner Yammer automatically creates. This is a very sloppy user experience and creates the perception that the admin is not managing the sites properly.
Ideally, there should be one Yammer Group for one Office 365 Group and you should be able to access it through Office 365 (like with other apps that are connected).
Tim Farmer commented
@emma beede This is a tremendous need. We invested heavily in Group Sites and now Yammer adoption is high. We need to link groups instead of recreating sites for Yammer groups which is highly inefficient. Please provide an update.
I found a solution for this, ditch Yammer. We now have two teams group. One for inner loop and other for outer loop + we mail enabled the group so now can also be used as distribution list. Much simpler and easier for users to understand.
We launched Yammer to the entire company. Then the O365 resources appeared on all Yammer groups, our user saw a very added value to use it as .... Teams (the product didn't exist at this time). Now that we want to launch Teams, we need to adapt / carry all the existing content - at least the O365 resources (as for Outlook groups).
We tried to launch a pilot on Yammer and after months now, users don't use it because they don't find their data easily ... For us, this is a specific risk for adoption.
Thanks in advance for taking into account our needs.
Benoit Fournier commented
Any new information? I need this feature.
+1! needs to happen sooner rather than later :)
Office 365 Japan Support Team commented
*English follows Japanese
Yammer グループを作成しても、Office 365 グループと接続されない場合がある
Connecting Yammer group to an Office 365 groups
[（公式）全社共通情報SYS-原価マネ・建設生産（土）WG] のグループ名で Yammer にグループを作成しても、接続された Office 365 グループが作成されない。
[（公式）全社共通情報SYS-原価マネ・建設生産（土）WG] のグループ名で Yammer グループを作成したら、Office 365 グループと接続されるように修正希望
When we create group in Yammer with some particular name and tried to connect to Office 365, connected Office 365 groups is NOT created.
For improvement of usability and manageability, we hope Yammer groups to get connected to an Office 365 groups even when it includes some particular name/characters.
Thank you for your consideration.
Rob Hardman commented
It's incredibly frustrating that this isn't even on the backlog yet. We have established O365 groups with associated Teams, SP Sites, Plans etc. Duplicating an O365 group on Yammer group creation creates nothing but confusion and a needless duplication of resources.
It's actually killed our Yammer deployment! We are forced to retain, at additional cost, Facebook Workplace (which ironically, does allow the connection of a SharePoint library to an existing group.) :\
Long overdue, needs to be a priority, need to have a group add feature
Lulu Zezza commented
I hope you are moving from considering to doing. There should be a way to unify groups across all the systems - in fact what reason is there for them not to be?
Alex Granado commented
Waiting for it ! Please change it from "WE'RE CONSIDERING THIS " to "on our backlog"
We created a sharepoint and then decided to integrate a yammer. Now we have 2 sharepoints. Is there a way to remove the default sahrepoint created with the yammer and instead link the previous sharepoint ?
Wim Deschepper commented
we definitly need this. We have teams in our organization that want to start conversations both within the team (inner circle) with Microsoft Teams and beyond the team (outer circle) with Yammer. Why should they create 2 groups with duplicate resources (2 sharepoint sites, 2 plans, 2 OneNote's)?