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.

An "important" lesson from day one at Lync 2013 Ignite

Lync 2013 comes with new features and new functionality. To support all of these new functions, there has been introduced a big set of new PowerShell cmdlets.
This didn't come as a surprise to me, as I have been playing around with the preview for a bit, and I have been reading Tom Arbuthnot's excellent post on the subject.
One of these "important" new cmdlets is the "Invoke-CsManagementServerFailover" command. Why?
Well, If you are anything like me, you type as little as possible, and you use the TAB as much as possible, you might to look out for this one. My "default" is to type "invoke-csma" + TAB. to get to the Invoke-"CsManagementStoreReplication" and then hit enter.

Unless I now hit enter twice, i will start the process of failing over the CMS.

I have no idea of how many times I'll fail over the CMS before I actually learn to hit tab twice, but I know I'll get there in the end.

So what was the important lesson here? It's not what you have to learn, but what you have to unlearn :)

For future reference, here's a list of all the cmdlets for Lync 2013