I was planning to blog about Microsoft Stream this weekend in any case but a discovery made this morning made me decide to put something out more quickly...
I had played with Stream before and enabled it for a few users on our system, but it went live this week properly. Having logged back in and broadly liked what I found I filed it under "look at weekend." One thing that did concern me is that by default it is intended for user-level publishing and sharing and commenting.
Just now logged in as a test account I realised Stream was enabled for ALL USERS on our systems. It is entirely possible this is my mistake from when I was trialling it, but I think not, I think it has been simply launched and enabled for all. I don't suggest trying to go into Azure Active Directory to disable it, simply making two small changes to render it safe while you may be planning to roll it out with appropriate levels of access.
- Log in as an admin level user at microsoftstream.com
- Click on your avatar in the top right and choose Admin Settings
- There you can make two important changes from the default.
You can set up a limited number of admin accounts for Stream. You can prevent users from leaving comments on videos. You can list the people that can make new channels and upload video.
If like me, you plan to use Stream as a much-improved version of 365 Video, then you will want to have only the people you want as channel publishers listed there.
To be clear, I'm surprised at what happened, not blaming anyone - I think Stream looks brilliant and I'm looking forward to properly trying it as we get ready to move a lot of channels across very soon (I hope we'll have all our video in Stream for the new school year) - but the risk of the system being left unmanaged and users discovering it, making channels and publishing any video they like seems to me to be way too high risk.
As I'll blog later - Microsoft seem to be putting social interaction front and centre of their educational offer (I find some elements of Teams for Education troubling), which strongly differentiates them from Google, where content and permissions underpin everything and limiting the ability of students to comment around work is baked in and easy to do. Nothing wrong with looking for students to interact as a group around learning - but I'd prefer the default position to be off not on so that it is only when it is desired and will be managed that it takes place.