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.

Loop in Channels for Microsoft Teams

Loop has gradually been added to Microsoft Teams, and now the time has come for Loops in Channels

Loop components are collaborative components that allow users to crowd-source an agenda, track a group's action items, or take notes collectively. With Loop components, users can collaborate right inside a chat message or channel conversation. Everyone in the chat or channel can edit the component inline, and changes are visible instantly.

To send a Loop component in a channel, users can select "Actions and apps" in the post compose box, then select "Collaborate with Loop". They can then select the type of component they want to insert into their message, enter content into the component, and select "Send". Everyone in the channel conversation will be able to edit the content inline.

Loop components are saved automatically to the user's OneDrive, which means they can be found from Office.com in addition to Teams. Users are encouraged to give their components easy-to-remember titles to help them search for and find them quickly.

Read more about how to control Loop in M365

This is associated with Roadmap ID: 123491 And should be rolling out this month.