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.

Lock a Microsoft Teams Meeting

Another security feature is coming to Microsoft Teams meetings. Coming this May is the capability for an organizer to lock a meeting in progress. 

If an organizer chooses to lock the meeting, no one will be able to enter the meeting after the lock has been set.

It would be advisable to train users on how to control their meetings with all of the recent feature enhancements. Especially highlight the powers an "organizer" has, and the importance of controlling this role, to avoid unnecessary disruption be "rouge" organizers.