05-29-2017 01:27 AM
05-30-2017 05:03 AM
I opened a support case with Microsoft and unfortunately the only solution is to delete the Yammer group and re-create it by an owner who does not have permissions to create Office 365 groups. I have opened a user voice request for Yammer and will post the link soon.
05-29-2018 02:39 PM
05-30-2018 02:39 AM - edited 05-30-2018 02:40 AM
Microsoft can disable the "enforce O365 identities" feature and you can add a new domain/network (not possible after September). Enforcing O365 identities and having only 1 Yammer network is required for Office 365 connected Yammer groups. Maybe these actions result in the group being converted to a normal group, but I'm not sure as I haven't tested it. An IT community sounds like a perfect opportunity to showcase all the features. May I ask why you're not considering using the O365 group features?
05-30-2018 02:56 AM - edited 05-30-2018 03:07 AM
This is really insane. The way O365 Groups (and services that depend on it) have been architected, it is a mess. I've complained about it on this forum a while back.
If I've already created a private group and an associated private team site has already been forcefully shoved into me, then why should I need to create another group just for creating a public open Yammer group for wider conversations? Beats me.
And, why can't I create a modern team site without forcefully having to create an O365 group with a mailbox and calendar all shoved in my face in Outlook? Beats me.
Why can't I choose only the workloads I want, the way I want? Beats me.
05-30-2018 09:54 AM
05-30-2018 09:54 AM
05-31-2018 07:43 AM
05-31-2018 10:09 AM