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.

OCS Edge issues

Here are a tips regarding an Edge installation I recently deployed.

1. Edge does not support *.domain.whatever certificates. You need one cert per service.

2. Default values on a A/V edge settings on a pool states port 443. This is wrong, as when you install the edge it states 5062. (described in this blogpost).

3. Edge services currently only support the US regional settings. If you experience unexplainable issues, try to log on to the server as the service account and change region to English US (ther is a hotfix for this, but it's not widely available. (You need to contact MS to get it).
Read about it here.

I know you'll find this if you search for it, but I just wanted to collect them here for future referance for myself