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

Installing OCS 2007 R2 (and fighting it)... Part 1; SQL 2008

on
Well, Here I am, about to install the next OCS version. I have three Windows 2008 servers at my disposal (in an existing domain). I am wondering just how easy a setup is, and if grandma could do it (which was my first impression during training) :) 
- First off is installing the backend server = SQL 2008
I thought this was going to be the easy part.... stupid as I am ;)
It turned out to be a little obstacle on my way. I launched the installer, and was prompted to first install .Net 3.5 and a installer hot-fix. I accepted, and the installation failed.... Again, and again.... As it turns out; The installer package only check for a few prerequisites of the installation, not prerequisites of the prerequisites. Only after installing (sorry; enabling the feature) .Net through server manager (and thereby enabling some IIS features as well) was I able to continue on with the SQL installation.
I guess I would have known if I read the manual first, but why do they make checks to an installation if they do not check (or install) all the prerequisites?
When it comes to the installation process (still talking about SQL), I can tell MS has been working a lot on it. The interface is clean, and easy to navigate through. They have even made a change in the defaults, to make you think. You now have to select the user under which the services (one for all or different for all) run under. This is a major improvement, as previous installation often run as local system or administrator. (Easy targets ;)