Data Lifecycle Management: Separate Copilot retention policies from Teams chats

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.

Cross posting in multiple channels

Here is another feature that has been in the works for a while, and I know a lot of customers who have been waiting for this: Cross porting of messages in multiple channels in multiple teams.

It easy to use, and accessed through the "rich text" button on the bottom left when you create a new message. Then select your channels in the "select channels" button.

Be aware though, once these are posted, there is for now no way to see which channels you have posted the message in, and there is no aggregated view of all the comments in the different channels, they have to be monitored individually for now.

This is the M365 roadmap ID 52393 and should reach all tenants by the end of this month.