Forum Discussion

bart_vermeersch's avatar
bart_vermeersch
Iron Contributor
Jun 09, 2017
Solved

Yammer groups integration

Our existing Yammer groups were transformed to Office 365 groups.   We now notice that some of them appear in other site collection and given limited access.   We have no idea why a yammer (offic...
Office 365 Groups
  • Adrienne Trudeau's avatar
    Adrienne Trudeau
    Jun 16, 2017
    Yes. At Ignite we announced that the second wave of Yammer connected groups would connect existing groups to O365. In March we announced via message center that we would begin connecting existing Yammer groups to O365 in May.
Adrienne Trudeau's avatar
Adrienne Trudeau
Icon for Microsoft rankMicrosoft
Jun 16, 2017
Yes. At Ignite we announced that the second wave of Yammer connected groups would connect existing groups to O365. In March we announced via message center that we would begin connecting existing Yammer groups to O365 in May.
Abhimanyu Singh's avatar
Abhimanyu Singh
Iron Contributor
Jun 20, 2017
Adrienne Trudeau wrote:
Yes. At Ignite we announced that the second wave of Yammer connected groups would connect existing groups to O365. In March we announced via message center that we would begin connecting existing Yammer groups to O365 in May.

Adrienne Trudeau: What if we do NOT want to connect those Yammer Groups to O365 Groups?

 

We have a gazillion Yammer Groups created by users, and we certainly do not want all of those to be spawning endless team sites which come along with the O365 Groups infra. 

 

This mess is becoming a challenge for us. Why can't the resources that come with an O365 Group be allowed to be enabled/disabled as per the requirement? More importantly, there should be only one pathway i.e. to start with a Group and then decide which features/tools/resources to add. As of now, all resources (Planner, Site, Yammer, Teams) create a Group on their own, and once a Group is created it spawns all the resources attached to it whether needed or not. Not even talking about the duplicate names conundrum if a Group already exists. 

 

At least give an option/choice of whether to provision an O365 Group behind the scene or not. This way we can have Yammer Groups standing on their own and with the ability to connect to an O365 Group only IF REQUIRED.

 

 

Resources