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
