Create a Microsoft Team based on a Office 365 Group created in Yammer
Office 365 Groups is supposed to be a single definition for a Group across all Office 365 services. However, Microsoft Teams cannot be based on Office 365 Groups created in Yammer. Please fix this so that Yammer Groups and Microsoft Teams are more tightly integrated. Fragmentation of Office 365 Groups will result otherwise.
Eric Davis
shared this idea
32 comments
-
Anonymous
commented
I am running into this headache now, where a Yammer and a Team were created with the same name, so the one that got created later got a random number added to the sharepoint URL. Now if we want to make a more cohesive community experience between the Team, Yammer, and TWO SharePoints, it's just going to be a mess to manage. Not to mention it's hard-to-impossible to know which group is which when choosing from a "share with" interface.
-
Anonymous
commented
Yammer is perfect for communicating news, incidents, everyday things...
Teams is almost perfect for collaboration in a project.
It would be all perfect if Teams and Yammer were connected to the same Sharepoint site.
Now if I have a Yammer long ago called "ABC" I have a site called "ABC". If I create a Tems "ABC" a different Sharepoint site called "ABCxyz" is created
Can't it be the same? -
Anonymous
commented
We've built hundreds of Yammer connected O365 groups in our organisation. If we then have to circle back around a recreate all of these in order to utilise Teams, this will be a nightmare and a huge piece of work. Please allow us to create Teams from Yammer connected O365 groups!
-
Anonymous
commented
I second this. The administrative overhead this generates is potentially quite large.
-
Christopher Hoard
commented
There are many in the Tech community who are asking for a unified group where all applications can be based on a single Office 365 Group. Best, Christopher Hoard.
-
Marco R.
commented
I believe, in many cases, there are more than one administrator per tenant. Think about someone is taking care of yammer and another person taking care of teams. How much confusion is created for all others, if the "yammer admin" and the "teams admin" by chance choose the same group name when they have to create a new yammer group or a new team. What happens in this case: two office 365 groups are created with the SAME name and no way to distinguish between them but their email address.
In addition, it is amy idea, too, that office 365 groups are supposed to be single definition for groups across all office 365 services.
Please, Microsoft, give us a great solution, soon. Thanks.
-
Singaravelu S
commented
I am still not sure, why MicroSoft Acquired Yammer if there is no concrete plan to tightly integrate it with Office 365. Millions of users are being trained to adopt the technology and suddenly one fine if it is deprecated, who can compensate for the lost man hours.
-
Andre Koldovsky
commented
We need this feature!
-
Anonymous
commented
Please fix this!
-
Alexander Lerner
commented
We have to have some way to transfer everything from yammer into teams or just switch the group functionality from yammer to teams. There is otherwise no way to use teams.
-
Martin Schubert
commented
This would be very helpful.
-
Alexander Lerner
commented
Actually it is a scandal that there are "different" Office 365 Groups. It has to be fixed immediately... Tons of Yammer-Groups with no option to use Teams...
-
Anonymous commented
this is the reason why we are not yet using teams. ALL our O365 groups are created on Yammer. We need the Yammer functionality and this is the only way we can connect a yammer-group to an O365 group.
It is impossible for us to delete and recreate over 300 active O365 groups, but we need Teams!
Please get on this fast or at least present a Powershell workaround for it!!!
-
Wim
commented
we have teams in our organization that need to communicatie both within the team as beyond the team context. We are using Microsoft Teams to have that innercircle conversation and would like to use Yamer for the outer circle conversations but without the extra group (and extra sharepoint site, onenote, plan,...)
-
Wim
commented
the idea behind this is more or less the same as https://yammer.uservoice.com/forums/399627-yammer/suggestions/19538515-connect-yammer-group-to-existing-office-365-group
-
Anonymous
commented
With the existing setup, once you've made a decision to start with Yammer you are stuck with your choice. I would like to see the option to decide to change your communication tool after the fact. If you think how we use SharePoint, you could have quite a lot of re-work down the road to simply switch communication tools. Allow Office 365 Groups to use Yammer or Teams or both if needed. Add the flexibility and make transitions in ways of working easier.
-
Charles Babcock
commented
This is a horrible pain point for us. We need this right now. We need Teams "groups" and Yammer "groups" to not be separate.
-
Anonymous
commented
Yammer single step creation of group, onenote, planner, sharepoint is much more efficient than Teams. Jamming Teams as a replacement for busines skype while this issue still exists is bewildering at best.
-
[Deleted User]
commented
Teams should provide the option of both synchronous and asychronous communication. This would be fairly easy by adding yammer groups to a teams channel tab.
-
Graeme Cuthbertson
commented
Please add this feature.