Data Lifecycle Management: Separate Copilot retention policies from Teams chats

on
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.

Backup of your Lync 2013 script updated

on
Based on my own experience with this backup scripts, I have updated the persistent chat section

Instead of just running the "Export-CsPersistentChatData" command, it will now check to see if persistant chat is implemented at all.

I have done this to avoid the big blood red text you get if it is not implemented.

The script is signed, and should run on any server, unmodified.

Instead of sharing the script through Drop-box, I have posted it in the Technet Gallery, right here: Backupscript-Lync_2013_v3.ps1. It will give you an option to rate the script, or even discuss it.