MC707648 - Microsoft Teams: Private and shared channels links

Service

Microsoft Teams

Last Updated

Apr 19, 2024

Published Jan 17, 2024

Tag

Updated message
Feature update
User impact

Platforms

Android
Desktop
iOS
Mac

Summary

Microsoft Teams will extend support for channel links to include private and shared channels. Members of these channels will be able to share links with other Teams users. The rollout will begin in early February 2024 and complete by late April 2024. No action is required to prepare for this change.

More information

Updated April 19, 2024: We have updated the rollout timeline below for DoD organizations. Thank you for your patience.

In Microsoft Teams, we are extending support for channel links to include both private and shared channels.  Once released, members of private and shared channels will be able to get links to a private or shared channel or channel post to share with other Teams users.

This message is associated with Microsoft 365 Roadmap ID 325325

When this will happen:

Targeted Release: We will begin rolling out early February 2024 and expect to complete by mid-February 2024.

Worldwide: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

GCC Release: We will begin rolling out late February 2024 and expect to complete by early March 2024.

GCCH Release: We will begin rolling out late February 2024 and expect to complete by early March 2024.

DoD Release: We will begin rolling out early March 2024 and expect to complete by late April 2024 (previously early April).

How this will affect your organization:

Users will now be able to share links to private and shared channels and channel posts with other members of the channel. Users who are not members of the channel will not be able to access the channel or channel post. Only members of the channel will be sent to the channel or post when clicking on a channel link.

What you need to do to prepare:

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.