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.

More Microsoft Teams updates coming out of preview

The new Teams client was implemented with the "new channel" experience, so this might not be news to everyone. But now is the time to prepare for the new experience in the old client as well. The biggest change is probably how the feed in every channel will change to hae the latest post on top, and to have the creation of new posts on top (instead of on the bottom). Thinking about it, this is something users recognize from other social media services, and it will hopefully prevent the common mistake users do when they want to reply toa post, but inadvertatly creats a new post instead. The roll out should be completed by mid July.

Shortly after the rollout of the new experience, the new search experience will also be introduced to the client. Instead of using the searchbar on top of the client, it will soon be possible to search within the context of a spesific channel or chat on the right hand side of the thread. Hopefully, this change is implemented by the end of August.

Another enhancement to the chat layout is the "compact" mode for chat, saving users some space in the application. The feature should be in the works, and is listed as "rolling out" in the roadmap.