Oct 23 2018 12:40 AM
Oct 23 2018 12:40 AM
During May AMA @Marc Mroz speak about a concept of "Stream only groups" they are thinking about
@Marc Mroz, any news on that topic? I need to create publkic groups but don't want all the things around them like Sharepoint site, visibility from Outlook, ... Yes I can restrict access to Sharepoint site afterward or hide the Groups from Outlook but it should be beter if they are not existing and we don't need to think about removing things after creation.
Thanks for feedback on procress onnthis concept
Oct 24 2018 01:51 PMSolution
We've been delayed on that idea, sorry, so no update really at this point, other than we know this is still a pain point and need to come up with a plan on how to address it. We still have it high on the list to come up with some sort of solution here, but we haven't had time yet to put the plan together. I'm still at this point leaning toward something like "stream only groups" but with the ability to upgrade them to O365 Groups in the future, so it's not a one way door.
Dec 03 2018 04:44 AM
Could be interesting especially to move O365 Group to "Steam only" groups so that we will have a consistant solution.
I just found the following preview function https://docs.microsoft.com/en-us/power-bi/service-create-the-new-workspaces within Power BI.
Initially when you create a Power BI Workplace you create a O365 group but as for Stream, you don't always need the sharepoint, mail, ... part of the O365 group.
It seems that now you can create some "Power BI only" workplace with some more access granularity (new contribution role than can be also usefull in Steam to be able to publish without been an admin of
the group/channel). You can also grant access using access/distribution groups.
Same functionality at Stream level would be great (and consistant with what Power BI dev team are proposing in preview).
Mar 05 2019 04:23 AM
Hello @Marc Mroz,
Any progress on that topic? I need to create some private groups/channels within the coming weeks with hundreds of users and it will be painfull to add and maintain them manually with an O365 Group.
We really need this functionnality of "Stream only Groups" not linked to all the struff you have with an O365 group (mailbox, calendar, planner, Sharepoint site, ....) and to be able to manage access to thses groups thru already existing distribution or access list.
Aug 23 2019 09:07 AM
@Marc Mroz More feedback on why this feature is needed and why we still haven't fully adopted Stream.
In short, this causes a lot of extra work when all we need is a "Stream only group" for the purposes of having sub-channels to display different channels on different pages in Communication sites. Some of this could be resolved with training or configuration but in the end it shouldn't be this difficult. This has prevented us from fully adopting Stream.
Aug 29 2019 06:45 AM
Aug 29 2019 06:46 AM
Jan 14 2020 05:09 AM
We really need this too. We have 4Tb of videos and many different current O365 video channels.
Creating hundreds of shared modern groups and their automatically added associated mailboxes, sharepoint sites, shared calendars and notebook just so that videos can be organised is frankly, daft. I can't overstate the search, compliance (and in our case, client safeguarding) issues that this short-sighted design creates.
We're going to have to look at moving away from O365 if basic functionality like this can't be realised in a timely manner. It doesn't look as if it should be hard to create new Stream-only groups - the backend functionality of these groups is already there with the O365 migration.