office 365 group disabling and implication on yammer connected groups

[null null]

Hi,

I was trying to figure out disabling of creation of office 365 groups following the link. 

1) Could you please let me know what will be implication to the existing yammer office 365 connected groups; will the files and resources still be accessible to members after disabling

2) Is there a programming workaround as in the article using Azure function , powershell and graph api new office 365 group is created by the one off ad group created with permission. Can we use the same to create Yammer office 365 connected group using Rest and powershell.

Thanks

[#2]

I had a similar question (link). What I know is that disabling self-service O365 group creation will disable creation of Office 365 connected Yammer groups as the only way to create them is via the Yammer UI or the API. Don't think the Office 365 connected Yammer group will be converted to a normal group. Then this would also have to happen if someone creates such a group and someone else becomes the admin and doesn't have the permissions to create O365 groups. Will test this when I have the time and let you know. 

Didn't find anything regarding using Azure functions/PowerShell/graph API to create O365 connected Yammer groups. We will be getting the option to create O365 connected Yammer groups via the O365 Admin Center. You can already use the Yammer API as this can be used to create Yammer groups and if the account creating the group has the permission to create O365 groups, then this will result in an O365 connected Yammer group. You do need a service account for this with the right permissions as you can't use the account of the user. Not sure if I would recommend doing that though. I'm assuming that the Azure functions are in the works as Yammer is being aligned with O365 groups. This would mean having to update the solution later down the road. My 2 cents: it's pretty obvious that Microsoft vision for O365 groups is self-service and right now disabling it will have an impact on the Yammer experience. Would recommend keeping self-service if possible and wait for updates on Yammer. 

[#3]

I can now confirm that disabling self-service won't have an impact on the O365 group features of existing O365 connected Yammer groups. Also noticed that it took about 5 minutes before it had an impact on the creation of new Yammer groups while it was instant everywhere else. 

[#4]

Self Service Office 365 site creation is the way forward. However, if the admin wants to view a site, then he needs to be put inside the owners as it is treated as a site collection, templating, provide a hook into the creation where custom bespoke functionality could be introduce during the time of templating, post site creation eg, navigation, change of locale, etc.
What do you think about these ..also we have site scripts coming in.

[#5]

Team sites connected to O365 groups show up in the SharePoint admin center preview. Options there are still limited, but I'm expecting more features as it evolves. I'm not sure why I would want to dive into each Team site though. Understand that this new model means that all Team sites connected to O365 groups are Site collections, but that doesn't mean that I have to manage them like I would manage "traditional" site collections where the collaboration sites are part of the Site Collection I have access to. There will be too many of these site collections for me to dive into them anyway. The new Site Designs and Site Scripts allow us to customize the SharePoint part of O365 groups, but this doesn't require us to disable self-service. My biggest concern right now with disabling self-service is the impact on Yammer. My expectation is that this will be addressed in the future, but even then my preference probably will still be to keep self-service enabled. Think there are still a lot of options to do what we want without disrupting the flow. Don't think we should force people to fill out lengthy forms just to give them what they need to get the job done. Have seen too many examples of IT building stuff nobody really needs and having a negative impact on the user experience just because the business asked for something that they can realize.