New Feature in Microsoft Teams: Forwarding Messages to and from Channels

on
An upcoming Microsoft Teams feature will allow users to forward posts and reply messages to and from channels, enhancing collaboration by reducing limitations on the type of content that can be forwarded.  Change for users: Currently, users cannot forward messages to and from channels. With this new feature, users can select the three-dot More actions menu on any channel post or reply message and choose Forward. In the Forward this message dialog box, users can select any destination chat or channel, with channels now included in the people picker. Admin Impact: This feature will be enabled by default. Admins can control message forwarding for individual teams or at the tenant level using sensitivity labels control data important to the organization. If a sensitivity label is applied, message forwarding will be disabled, blocking users from sharing content outside the channel. The feature will according to the Roadmap ID 469508 be rolling out in January or February 2025.

Prepare for shared channels in Teams

on


According to a post in the message center not long ago, the shared channels feature in Teams is about to roll out in GA after being available in preview for some time.

Although shared channel seems to be available by default in the Teams client, please note that this is only an internal availability, unless the admin of the tenant has enabled/allowed the b2b-directconnect in Azure AD. 

I recommend reading up on this article in order to familiarize yourself with the configuration. It is not enabled by default, and there are several options available. A good approach could be by opening to specific partners and not allowing "everyone". If the company has invested in AAD P1 or P2 licenses, it is also possible to trust the partner's MFA and Compliance checks in conditional access, easing the usage for users.

This feature adds to the mix of external user access. It does not replace the guest user feature, nor anonymous access to teams meetings. But the real benefit of shared channel in my view, is how it adds the channel in the external user's existing list of teams and channels and does not require a tenant switch.

According to the message center post, this should be rolling out mid July and the following weeks.