restrict access to video

Copper Contributor



in Office365 video we are able to restrict access to a video based on group membership (security / distribution group). It seems in stream it currently only possible to use Office 365 groups, will be it be possible to use synced groups from on premises in the future?


We have different organisations (~150 members) in the company which require private video sharing. It convenient in office 365 video to use existing groups.

3 Replies

Appears that only Security Groups can be used when using the Admin settings\Content Creation to restrict video uploads and channel creation( When creating channels Office 365 Groups or Security Groups can be used. The interface is inconsistent and we only want to use dynamic Office 365 Groups for everything and slowly decommission on-premise synced AD Security Groups. 

For having a landing page for videos, today we only support O365 Groups (modern groups). This means that if you make a team in MS Teams, or a team site in SPO, or a plan in Planner those make an O365 Group which can be used in Stream (and vice versa).


We do support AD security groups at the video level and in admin settings. At the video level if you switch to the "People" search scope in the permissions section you can search for AD security groups.


We are planning on adding a new group type to Stream that will have a landing page just like the O365 Groups. This new type will be a "Stream only group," not connected to an O365 Group. This Stream only group will have owners, contributors, and viewer roles. In each of those roles you'll be able to add AD security groups or individual users. This new group type should help in many cases where you want to use AD security groups instead of using O365 Groups. We hope we'll be able to start on this work in Q2/Q3 timeframe.

Thanks Marc,
I referencing the Admin Settings here: . We want to use Dynamic Office 365 Groups and the only option is to use a Security Group or user. We'd like to continue to use these Modern Groups instead of creating AD-Hoc one-off AD Security Groups.