Introduction Microsoft Teams offers private and shared channels as specialized collaboration spaces to cater to different organizational needs. While these channels provide enhanced security and collaboration features, they come with specific limitations and management challenges, particularly around the associated SharePoint sites. This post covers some limitations, and management tips for SharePoint sites associated with private and shared channels, including PowerShell hacks and governance practices to overcome these challenges. Managing SharePoint Sites for Private and Shared Channels SharePoint sites associated with private and shared channels are special types of sites with the limitations as identified by Gregory in his blog post Why you should never mess with Private and Shared Channel SharePoint Sites related to the inability to attach to a hub directly, being accessible from the Teams interface mainly, and inability to manage permissions at the site level, and with constrained external sharing.

Introduction It is possible to create M365 Groups and Teams with the same name, and there is currently no built-in way to prevent this. The new Team/Site/M365 Group is created with a random number appended to the Team name for the SharePoint site and m365 Group email address. Having duplicate names can cause confusion and increase risks, including: Wrongly Granting Permissions: Users may accidentally grant permissions to the wrong M365 Group or Team, leading to unauthorized access.

Introduction Renaming the ‘Files’ tab in Microsoft Teams to something more meaningful for your business, such as “All Access,” can enhance user experience. It can help to differentiate other document libraries added as tabs. The Files has been renamed to Shared for chats to show all the files and links that were sent in the chat, making it easier to find them- all in one place. However, it is not possible to rename the Files and Posts tabs from the UI within channels.

Introduction By default, guest access for Microsoft 365 groups is enabled within the tenant. This can be controlled either to allow or block guest access at the tenant level or for individual Microsoft 365 groups / Teams. For more information, check out Manage guest access in Microsoft 365 groups. PowerShell Script to Prevent Guest Access Below is a PowerShell script that allows you to disable/enable guest access for specific Microsoft 365 groups.

Introduction If ever you had the chance to get your hands onto the New chats & channels experience, you may notice that the Teams icon is missing from the tray on the left To access the channels, it is an option within the chats. Revert In case you find it confusing you can turn it off by following those steps Click on the button Update, settings and more at the top of Teams

Teamifying an Existing M365 Group with PowerShell Within M365 , SharePoint and Teams together provides a rich collaboaration platform. When a team site is created from SharePoint admin centre, it is not associated with a Teams despite a M365 group is created in the background. To extend SharePoint collaboration features , there is a need to “teamify” an existing Microsoft 365 Group, essentially attaching a new Teams instance to it to allow use of channels and other apps.

Retrieving SharePoint Site URL for Teams Channels Have you ever needed to construct the SharePoint site URL for a private or shared channel using just the channel name? This post will guide you through the process using Microsoft Graph endpoint and PnP PowerShell though PowerShell. You may need the details for these reasons To specify within a retention policy Purview Retention Policy Questions from the Field eDiscovery Extract from eDiscovery of private and shared channels “Each private and shared channel has its own SharePoint site that’s separate from the parent team site.

Teams Add-in Not Showing Within Outlook The add-in for setting up a teams meeting within the outlook application was no longer showing. The add-in was not available to be enabled within Outlook as per Troubleshoot the Teams Meeting add-in in Outlook for Windows. Even after reinstalling Teams or creating a new profile within Outlook, it did not fix the issue. As a workaround I was using Use Team calendar to create meeting Use Outlook Web App to create meetings With Microsoft Support’s help via a case we identified the issue was the missing following key: