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.

In case you missed it: Loop components in Teams chat

 As always, there are a lot of features coming out or being enhanced in the Teams client. Loop components is one of the new cool features released this spring. This is a feature allowing for better collaboration within a chat object.

Unless it has been disabled by an admin, it should be available to all by default, and really easy to set up. When writing a one on one chat or a group chat, just select the loop component you want to incorporate from the menu. At the time of this post, it's not possible to add components to channels, but this should be in the works.

A clever eye will notice that Loop components in a chat is stored as a file in the chat, and you don't need the Teams client to access the file. As long as you have the link (and access rights) you can access it through any web browser.

You can read all bout the feature in this post, and check out which Loop component controls an admins can change.