Data Lifecycle Management: Separate Copilot retention policies from Teams chats

on
In a previous post I mentioned how Microsoft is adding the capability to use Purview Data Loss Prevention on Copilot to block certain information from surfacing for the user. Now, Microsoft is adding Copilot to it's retention policy controls, and starting mid-February, public preview tenants can start exploringthis new feature. Admins will be able to create separate retention policies for Microsoft Teams chats and Microsoft 365 Copilot interactions, and allows for a more tailored data management. The feature will of course require that the targeted users have Microsoft 365 Copilot license.  According to the message center, the public preview will be during February, and we can hope for a general release sometime in March. The feature will be available by default, but policies will have to be set up.

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.