We’ve taken note that interest in this particular request has increased. Please continue to provide feedback on this item as we evaluate what it would take to support this scenario. Thanks!
An error occurred while saving the commentTristan commented
Face it everyone, the whole office365 groups thing was a rushed feature, poorly thought out. The idea that all people involved in a project are going to be allowed to have the same permissions to to all data within the project is nonsensical in many many environments.
Add to that the different security models of the different apps (e.g., SharePoint with it's own internal groups and users) and the issue is just getting worse.
My users are already making a hash of this - realisticly we'll probably have to move ownership back to IT... which is kinda backwards from the intent eh?
The idea of creating a 'collection' of some kind, which grouped synergistic apps together was sound, but perhaps that should have been separate to the existing azureAD groups, and allowed existing groups to be used for permissions.
Perhaps even a set of standard groups (files r/o, files r/w, cal r/o, cal r/w) created with each parent team ( which maybe could have been something more like an ou? ), and a clear mechanism for owners to create new special case groups.