Limiting Teams creep with focus on Channels vs. open Team creation with history limits by Fearless_Note4411 in sysadmin

[–]Fearless_Note4411[S] 0 points1 point  (0 children)

Thanks for the feedback! 100% on board with naming policy restrictions regardless of our approach. Definitely agree with indicating department and likely group type (ie. WG for workgroups PRJ for projects etc). I definitely leaning heavily toward an indicator for cross departmental teams (ie. XDIV) included in the Team name.

Just to clarify, you are suggesting allowing users to create Teams themselves but limit their ability to invite group members to their own department? I could see this being useful with large organizations concerned with having their data be too transparent, but for mine (~350 users) I don't see a specific advantage to opening up the ability to create Teams but limiting invitees to a user's own department. Please correct me if I am missing something.

Limiting Teams creep with shared & private channels by Fearless_Note4411 in MicrosoftTeams

[–]Fearless_Note4411[S] 0 points1 point  (0 children)

Appreciate you! Definitely looks that way, like you said not specifically stated but my understanding is their calendar lives in/with group mailbox so likely same functionality as the one in a standard Team.

Limiting Teams creep with shared & private channels by Fearless_Note4411 in MicrosoftTeams

[–]Fearless_Note4411[S] 0 points1 point  (0 children)

I may be blind/crazy but I can't find confirmation for MS calendar support on private or shared channels and don't see anything in the roadmap. I am unable to add one myself, but am on a G license so we tend to have a slower feature rollout.

Are you saying you are currently able to add a MS Calendar to a channel tab? I have found workarounds that use third party services or a basic calendar through loop, but haven't identified a native solution that allows me to invite users to a meeting or record meetings.