Jun 09 2017 05:29 AM
Jun 09 2017 05:29 AM
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 (office 365) group would be given limited access on a non-related site collection.
Any clues? We find it a bit disturbing.
Jun 09 2017 07:23 AM
Jun 09 2017 07:27 AM
There was an annoucement that existing yammer groups would also be transformed to Office 365 groups (with a team sites etc)...
Jun 09 2017 09:30 AM
I sure do hope it is ready because all our existing Y groups are transformed into O365 groups.
Jun 09 2017 10:06 AM
Jun 09 2017 11:33 AM
We found the cause of the limited acces rights to some yammer groups.
A user shared a document with yammer groups instead of regular groups because they have similar names. We use the yammer groups to communicate and discuss more broadly about projects, while O365 groups were used by the project teams.
It's a pitty, because we now end up with two groups for each project.
I still believe it would have been much more transparant if all groups were equal and it's up to the group owner to pick the services he wants or need allowing him to choose both yammer and mail for his group.
The distinction between a (new) Yammer group and Outlook group is hard to explain. Teams currently tied to Outlook groups only makes it even more difficult.
Last week a user told me: "No we don't use Groups anymore, we are now using Teams instead..."
The current mental model is too difficult. A group should be a flat collection of services (yammer, mail, teams, planner,...) which you can enable/disable yourself (group owner).
My 2 cents.
Jun 16 2017 08:50 AMSolution
Jun 20 2017 02:33 AM - edited Jun 20 2017 02:36 AM
@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.