philosophy question: new controls in team admin control

Highlighted
Contributor

Philosophy question for you: it seems that whenever you release new controls, you always seem to release powershell controls first (that require admin privs) - and sometimes, or never, move those to be controls within the Team owner control.

 

Is that by design?  I would think that you would want to empower the team owner wherever possible.

2 Replies
Highlighted
Great question! The controls that we build out for IT admins let them manage across Teams - so they can set the policies that they need across the whole organization. We let team owners manage the settings for their specific teams that they own, but admins can manage settings that span across teams so they can set the policies that meet their regulatory needs.
Highlighted

Regulation vs. looser controls is always the pain point, I suspect.

 

Thanks for replying.