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.

Don't forget to specify sql instance on install-csdatabase

I was upgrading a Lync 2010 standard edition server to 2013, when I came across a problem with the "Install-CsDatabse" command. The technet article (http://technet.microsoft.com/en-us/library/jj688013.aspx) is pretty good, but it left me with the impression "RTC" was the default database for the command.

I was using the following command:

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn myserver.domain.com -Verbose

But all I was getting was an error message saying the server\instance was not available:


According to the article, RTC is the default instance, and I made the mistake of beliving RTC was the default instance for the command as well. After reading a couple of logs, trying to make it work, I realized the default instance for the command is DEFAULT, not RTC.

When installing a database on a Standard Edition 2013 server, remember to specify the RTC instance, and save yourself some troubleshooting :).

This command worked like a charm:

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn myserver.domain.com -SqlInstanceName rtc