Feature Update: Office 365 Connected Yammer Groups

Occasional Contributor

Is someone on a Groups adoption related bonus?

Beginning May 2017, existing groups in your network will be connected to Office 365 and provisioned with Office 365 Group resources.


We've previously locked down group creation to only a few defined persons so when creating groups in Yammer no group is created in O365.  We don't really want a plethora of SharePoint sites for mundane Yammer groups.


Anyone know if the O365 Group blocks are now redundant or bypassed via Yammer?



13 Replies

The "additional info" link provides your answer:


Only groups owned by users with group creation privileges will be connected to O365. In other words, people who cannot create new O365-Connected Yammer groups today will not see the existing Yammer groups they own get connected to O365.


I'd like to see more detail on what happens in cases where O365 Group membership is dynamic, for example.

Since when did Yammer groups have owners?

If we are to assume this means admins, then that's still not something we want.  Just becauise one of the admins of a particular group has rights to create O365 groups doesn't mean we want more O365 groups...


I have a case open with Prem so we'll see what they say.


I'm curious about your concern here about the proliferation of sites, etc. Do the new retention policies not meet your governance needs?

We have a lot of Yammer groups paired with existing SharePoint sites, will we have a way to link them deliberately or will this result in a bunch of duplicated sites we need to ignore or clean up in some way?
Or on the flip side of this will it be possible to hide the Office 365 Resources section in a group where we already use another SharePoint site?

Found a "work-around" - Make sure your tenant does not meet the criteria for this automation.  Add a new Yammer network but do not merge them.  Bit of a pain in that you need another domain & to register in in O365.  But at least blocks this process if it's going to be an issue.


We're not approved to even use SP in the cloud as yet - so no go for us.

You're very likely going to need to move some content around.


MS has been pretty firm about O365 Group resources not having an "ala carte" model at the time of the creation of the group. So if you have content in an existing SharePoint site when the Yammer Group gets O365 resources (which include a SP site) you'll either need to leave the new SP site empty, or move the content into it (and then retire the old SP site).


I made a little how-to video you can share with employees that want to move the content to the new site. https://techcommunity.microsoft.com/t5/Yammer/quot-But-Now-I-Have-Two-Sites-quot-A-Tip-for-After-the...

Yes, we will have a number of groups where the new modern site is just going to be a link to the existing site because they require features that won't work in modern sites.


While we are on the subject, is this rolling out yet?




The “duplication of Team Sites, libraries and One Notes is a headache already, but will only get worse, when Microsoft also will “connect” existing Yammer Groups.


One of our clients have a provisioning solution where a new team site is created with a default setup, including a unique site home page, branded look and feel, libraries, lists, Onenote, metadata and a linked / embedded Yammer group. Everything according to provisioning recommendations from Microsoft at the time.


After phase #1 of  the Yammer group roll out, all the Yammer groups created through the Site provisioning, creates duplicate Sites, libraries and Onenotes. None of these additional sites have the look and feel, metadata or other features that are being configured via the provisioning app. In addition: They are not accessible through the intranet, based on regular Sharepoint publishing features (while the provisoned sites and libraries are an integrated part of the intranet).


In the short term there only seems to be the alternatives to disable Groups altogether or letting all most of the duplicate sites being empty. Even if we love the Group concept as such!


In the long term, viable solutions could be that Microsoft b) lets us keep “no-connected” apps as an alternative, b) when we are creating O365 groups, we should b able to pick and choose which apps the group needs and/or c) we should manually be able to add/link existing implementations, for instance an existing classic site to a new O365 group.


Before the roll out of phase #2, can you guys please come to our rescue? @Adrienne Trudeau, @Pavan Tapadia or @Angus Florance

I definitely appreciate the challenge that your customer faces. For now, since the backfill phase to connect existing groups is already underway, I'd recommend disabling creation of O365 groups so that you don't wind up with duplicate sites, libraries and OneNotes. 

Thanks, Adrienne! And long term?

No commitments for long term solutions yet.