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

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

Still installing OCS, and getting grey hairs

on
I admit it, I guess I was a bit quick on that last post, when I said I did not run into any serious problems. Well, I did. Biggest problems though, were all related to naming conventions, certificates, and a very aggressive firewall on the brand new 2008 windows server.

- First of all the Firewall:
I was fooled by how easy the installation is, and I was not prompted for any errors. The databases and files were created as expected. The only problem was when I started to run the verification tools, and got error messages. I tried to Google the messages, and the answers indicated certificate problems. So I started all over again, being very careful about names and certificates (By the way; If your CA is a 2003 server, and the client is a Vista or 2008 machine. Make sure to search TechNet for CA updates to the website. And enable ssl on the CA site). After rebuilding the pool 3 times, I was pretty sure certificates weren’t the thing, even though the error message indicated the certificate. So what else could it be? In what way did this installation differ from the OCS 2007 installations I had made on 2003 servers? No...! It can't be that simple? Yes it was. As it turns out: Windows 2008 comes with the firewall turned on by default. Pretty nice actually. But if you're not aware of this, you're in for some grey hairs like me. 

Once the appropriate rules were enabled, the validation came through like a charm. Now most of the features are up and running.

My next project is to integrate the Exchange 2007, and really create that UC environment we need in the demo/lab here.