03-22-2017 09:12 AM
03-22-2017 09:12 AM
Good Afternoon, recently Yammer integrated into Office 365 Groups (long awaited), but even though Yammer is now connected to Office 365 Groups, it feels very disconnected from Microsoft Teams and all the great collaboration features that come with Microsoft teams. Currently there seems to be no way to connect a Microsoft Team to a Office 365 Group created in Yammer (very disappointing). When I asked this question in the Yammer AMA, there wasn't a great answer except for there will be a "connector for Yammer."
My concern is this "connector" will result in 2 Office 365 Groups (one from Teams and one from Yammer), with 2 Modern SharePoint Team Sites and 2 different sets of files. This honestly seems to go against the whole principle of Office 365 Groups with a single definition of the group membership that goes across all the Office 365 Services.
Do you have any plans to have better integration between Microsoft Teams and Yammer and will there be a point where a Microsoft Team can be based on an Office 365 Group that was created in Yammer?
03-22-2017 09:42 AM
Hi Eric - We recommend the group pick the app in which they want to collaborate and use that as their center of gravity and workspace.
03-22-2017 09:43 AM
03-22-2017 09:52 AM
Is this Yammer connector you're referring to available today, or is that coming in a future Microsoft Teams update?
03-22-2017 09:52 AM
03-22-2017 10:10 AM
Hey @Dan Stevenson, the Yammer connector for Teams currently allows you to bring in conversations that have defined keywords, or conversations from specific individuals. It also feeds in announcements from a defined Yammer group.
Why doesn't it also feed in a regular conversation from a defined Yammer group?
03-22-2017 10:30 AM
Thank you for the clarification. To all reading this thread, please vote on this feature request, otherwise I truly believe people will be confused of why they cannot connect a Microsoft team to an Office 365 Group just because it was created in Yammer. https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18692566-create-a-microsoft-te...
03-22-2017 10:38 AM
03-22-2017 10:42 AM
03-22-2017 10:56 AM
How do you set up this connector? Are there directions on https://support.office.com/ ?
03-22-2017 11:46 AM
Hi @Eric Davis.
I recorded this over Periscope just now and archived it to YouTube. (Periscope embeds aren't supported on this platform.)
03-27-2017 01:55 PM
Thank you for the awesome video response Darrell! It was very helpful and it will be helpful to my team as we plan how to integrated Yammer with Microsoft Teams.
03-31-2017 08:55 AM
03-31-2017 09:13 AM
05-19-2017 01:17 PM
I also agree. Those that had Yammer deployed before Teams went GA and have Yammer created 0365 groups really need MS Teams to work with those private groups. Otherwise many of us will now have a confusing amount of 0365 resources per team/department/project/committee. For some of us we have
Microsoft please help guide us on how to move forward.
05-19-2017 01:35 PM
05-30-2017 02:13 PM
05-30-2017 03:12 PM
Hi Paul. The centre is Office 365 Groups.
I assume from your response that you're talking about the Outlook conversation experience when you say "Office 365 Groups." Yammer will soon make use of the shared calendar. But the conversation experience will remain as Yammer.
06-20-2017 03:50 AM - edited 06-20-2017 04:00 AM
Dan Stevenson wrote:
Yammer is focused on enterprise social scenarios - like a CEO Connection forum for everybody in the company. It's also how we rolled out Teams across Microsoft - we created a Yammer group to get feedback from tens of thousands of people.
Teams is focused on team collaboration - high-velocity teams, working together closely. Plus of course the separate private chat capabilities.
The recommended way to use Yammer is in fact to configure a Connector in Teams - look for posts to a particular network, or matching a particular keyword. You then get a nicely-formatted card posted to the channel in Teams, which you can then click to see in Yammer. We use this a lot - people mostly stay in Teams, and then when something relevant pops on one of the enterprise social networks, we can quickly see it.
But @Dan Stevenson wouldn't that mean that we will end up with two sets of resources/tools? One for the Teams backed by O365 Group provisioned with a team site and all. Second for the Yammer Group in-turn backed by another O365 Group provisioned with its own team site and all. And then what happens if same name is intended? Per the scenario you gave, the O365 Group + Teams are private, but Yammer Group is intended to be public, how will this work?
Am unable to wrap my head around it completely yet.
Why so many pathways? Why can't O365 Group be the only center? Provide only ONE interface to create an O365 Group, and that's it. While creating the Group, the user should be able to choose what services/tools/resources are needed and adds those. And user should be able to refine/change those choices later as required.
Right now as it stands, any of the tools/resources/services will create an O365 Group behind it silently. With Yammer now in the mix, there are a zillion team sites and onenotes being spawned all over the place irrespective of whether they are really required or not. And that too in couples (one for Outlook Groups and other for Yammer Groups).
This can be done better. From all the services guide the user to O365 Group creation, but that Group creation should be in control of the user and let user choose the rest of the services. Also, if the user doesn't want to connect a Yammer Group with an O365 Group, let it be. So, I can have my O365 Group provisioned with exactly the services I want and have a public Yammer Group without its own O365 Group and/or team site.
06-22-2017 08:30 AM
Two sets of tools with two different permission profiles:
I tend to agree with you that a group owner should be able to turn off services that they don't want to confuse members with because they won't (shouldn't?) be used for that group.
As for a "zillion team sites, groups" being provisioned. Yes, and my partners at tyGraph have a solution for that :) See our webcast on "tyGraph for Groups." Blog post is here https://www.tygraph.com/yammer-connected-groups-backfill-now-in-progress/
And @Dean Swann can point you to the recording of the webinar.