Shared channels is a great addition to MS Teams and had no problems creating shared channels when it was widely available in second half of 2022.
After testing and adding to our IT governance we found use cases, then when I went to create a production Shared channel received errors both in TAC and in PS.
I raised a MS support ticket after searching the internet with no success.
It was found out that the Teams Policy setting (Team Owners can) Create Shared Channels completely overrides Global and Teams Administrator RBAC. This according to Product Engineering Group's response is as expected. The workaround create another policy with this enabled and have admins members of the policy group. Our IT governance has it where we don't allow end users to create private and shared channels so our global teams policy is private and shared channel creation disabled.
Some issue with this logic:
- How is ONE policy in all of teams logical to override RBAC ?
- How is it practical and/or viable to have to pay double license IT admins (standard account and admin account) for just ONE teams policy?
The admin account has to be an owner of the team to be able to create a shared channel too this again does not make sense. Though am told this is "as expected" according to PEG. That is like saying an exchange admin needs to be an owner of mailbox before you can add delegate access for other users or domain admin needs to be member of AD group to add other users to the group membership.
All documentation states this policy applies to teams users not admins e.g. - https://learn.microsoft.com/en-US/microsoftteams/teams-policies?WT.mc_id=TeamsAdminCenterCSH#createchannels
How are other IT admins out there dealing with this?
I've completed a DCR form to go to PEG but would like to know how others are managing this.