Making Private Teams Discoverable: The Game-Changing Microsoft Teams Update You've Been Waiting For

 Microsoft Teams is at the forefront of enterprise collaboration, but there's always room for improvement. One long-standing issue? The discoverability of private teams. Until now, private teams have been something of a walled garden, accessible only through an explicit invitation. However, Microsoft is rolling out a pivotal update that will make private teams discoverable based on admin settings. Let's delve into what this means for administrators and end-users alike.

Screenshot of a Microsoft Teams policy configuration panel. It's titled 'Teams policy'. Under the title, there's a field labeled 'Name' with an entry 'PrivateTeamDiscoveryPolicyTest1'. Below is a blank field labeled 'Description'. Various configuration settings follow:  'Discover private teams' set to 'On' 'Create private channels' set to 'On' 'Create shared channels' set to 'On' 'Invite external users to shared channels' set to 'On' 'Join external shared channels' set to 'On'.


What’s Changing and Why It Matters

The core of this update lies in making private teams discoverable, which will be controlled by administrators through a simple toggle in the Teams Admin Center. This feature revolutionizes the private team experience by allowing end-users to search for these teams through the "Join team gallery" in their Microsoft Teams client.

The beauty of this feature is its flexibility. Admins can make all private teams discoverable or apply discoverability based on sensitivity labels. For organizations, this means more control and a streamlined process for team membership, enhancing both user experience and administrative capabilities.

Screenshot of a Microsoft Purview configuration panel titled 'Edit sensitivity label'. On the left, a vertical navigation menu contains options: 'Name and tooltip', 'Scope', 'Items', 'Groups & sites', 'Schematized data assets (preview)', and 'Finish'. On the right, under the title 'Define protection settings for groups and sites', a description reads, 'These settings apply to teams, groups, and sites that have this label applied. They don't apply directly to the files stored in those containers.' Below are various configuration settings:  'Privacy and external user access settings' with a description: 'Control the level of access that internal and external users will have to labeled teams and Microsoft 365 Groups.' 'External sharing and Conditional Access settings' with a description: 'Control external sharing and configure Conditional Access settings to protect labeled SharePoint sites.' 'Private team discoverability and shared channel settings', which is highlighted. It has a note: 'Change the default settings for discoverability of private teams (Default: On) and sharing of shared channels (Default: Shared with all).' Further below, there's an option to 'Apply a label to channel meetings' with a dropdown menu set to 'None'.




Screenshot of Microsoft Purview's 'Edit sensitivity label' panel. On the left is a vertical navigation bar containing options: 'Name and tooltip', 'Scope', 'Items', 'Groups & sites' (highlighted), 'Teams discoverability and sharing', 'Schematized data assets (preview)', and 'Finish'. The main content on the right is titled 'Define Teams discoverability and sharing'. It instructs users on how to 'Configure the discoverability and shared channel settings for Teams that have this label applied', with a link to 'Learn more about these settings'.  Under 'Private team discoverability control', there's a checkbox labeled 'Make private teams discoverable'. A note elaborates: 'If selected, users will be able to search for teams with this sensitivity label. Users will still need owner approval to join the team. In order for this setting to take effect, go to the Teams admin center, and within Teams policies, make sure the Discover private teams policy setting is on.'  Below this, a section titled 'Shared channel controls (Select multiple for desired combination)' details:  A checkbox labeled 'Restrict to: Internal only', accompanied by a note stating: 'If not selected, the channel can be shared with External teams too. Note: If a sharing relationship has been established before the label was applied on team or if the label was edited, it would not be terminated.' A checkbox for 'Restrict to: Same label only (for Internal teams)', with an additional note about the implications of this setting. Another checkbox for 'Restrict to: Private Teams only' which applies to internal as well as external sharing. A related note provides specifics about the application of this setting. Lastly, a note at the bottom mentions that channels can always be shared with parent teams, and label-based policies will apply to private teams for both internal and external tenants.

The Rollout Plan You Need to Know

Mark your calendars because the targeted release starts rolling out in late October 2023 and aims to complete by early November 2023. For those on the standard release plan, the rollout will begin in early January 2024, completing by mid-January 2024. Timing is crucial, especially for admins who will need to prepare for these changes.

How This Empowers Administrators

Admins rejoice! This update provides granular control over which private teams are discoverable and by whom. You can set policies globally for all users or create custom policies for subsets of users. Plus, you can elevate your control by integrating sensitivity label settings through the Compliance portal.

Let's break it down:

  • Global Policy: Make private teams discoverable for everyone.
  • Custom Policy: Limit discoverability to specific groups.
  • Sensitivity Labels: Add an additional layer of specificity by making only teams with certain sensitivity labels discoverable.

User Experience Elevated

From an end-user perspective, this feature is a win-win. It empowers users to find and join relevant teams, boosting collaboration and overall productivity. However, it's essential to note that while users can discover private teams, they still need to send a join request for approval by the team owner. It's a balance between openness and control, which seems to be the theme of this update.

Prepping for the Transition

For admins, preparation is key. Before any sensitivity label policies can take effect, you must first enable the corresponding setting in the Teams Admin Center. Please note that the feature may take up to 24 hours to activate. For organizations with an E3 subscription or higher, you'll also have the option to use sensitivity labels for more nuanced control.

Limitations and Fine Print

Like any feature, there are some limitations:

  • The setting may take up to 24 hours to take effect.
  • This feature won’t work for customers with Information Barrier policies.
  • Instant refresh is not available in the "Join a team" page.

Wrapping Up

The upcoming Microsoft Teams update, aimed at enhancing private team discoverability, is a game-changer for both administrators and end-users. By understanding its features, rollout plans, and implications, you can prepare your organization to make the most of this innovative feature.

So, are you excited about this update as we are? Let us know your thoughts in the comments below!


Comments

Popular posts from this blog

Understanding Microsoft Teams Room Licence Changes Coming July 2023

Microsoft Teams Elevates External Collaboration with its New Feature Rollout

Enhance Teamwork with Microsoft Teams' New Feature: Collaborative Stageview