Safeguarding Sensitive Data in Microsoft 365 Copilot with Purview DLP (GA Release)

The challenge with sensitive data and access to Copilot Microsoft 365 Copilot empowers users with AI-driven assistance across Microsoft 365 apps, but it also raises concerns about accidental oversharing of sensitive information. In response, Microsoft has extended its Purview Data Loss Prevention (DLP) capabilities to Microsoft 365 Copilot, allowing organizations to enforce information protection policies within AI workflows. The DLP for Microsoft 365 Copilot has been in preview for some time, but Microsoft has now announced it is released for GA (General Availability). Among some of the interesting features are new features like alerting and policy simulation. Key details:  Rollout Timeline: As of June 2025, the rollout has begun. It should be completed worldwide by late July 2025. Scope: Initially, DLP for Copilot was available for Copilot Chat scenarios. By the time of GA this is expanding to Copilot in core Office apps (Word, Excel, PowerPoint) as well. Ensuring that DLP prote...

Lost in the virtual time....

No, this isn't a sci-fi blog. It's about windows time in a virtual environment. Some applications depend on the computers having the same time. And this is no problem if all virtual machines are running on the same host. But in my case, I have a one server running virtual servers, and one or more computers running virtualPC images to access the VM's on the server.
Now, in a perfect scenario, all computers should have the same time scource (At least within the same campus). But as in my case, the lab is totally isolated. Time servers are not available to the hostserver or the vm's (who always, unless told otherwise sync with host-time).
I have recently discovered a way to stop the virtual pc from syncing the hostoperating system. There is no gui for this, and you have to turn your VM off first. Then edit the .vmc file:
Find the section of the .VMC file that looks like this:
<integration>
<microsoft>
<mouse>
<allow type="boolean">true</allow>
</mouse>
</microsoft>
</integration>
Change it to look like this:
<integration>
<microsoft>
<mouse>
<allow type="boolean">true</allow>
</mouse>
<components>
<host_time_sync>false
</enabled>
</host_time_sync>
</components>

Restart the virtual machine, and set any time you like. Very handy, also when testing betas that have expired ;)