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

Name vs. ip.addr. in the year 2008?

Here’s a problem I thought was history. In an environment with DHCP and DNS, I thought it was impossible to get things wrong. But obviously, I am the one who’s wrong.

I have been troubleshooting a Voicemail system with strange symptoms. Where among the strange log messages were: Could not locate %dbname% on server %hostname%. The database was running on the same server as the voicemail application, and name resolution was not an issue. Or so I thought. I tested name resolution through nslookup and tried to ping by using various names (hostname and fqdn). Everything seemed to be working. As a last desperate test, I changed the configuration in several places, to reflect the server’s ip-address instead of it’s hostname (inserted to the config by default during installation). Wonders of all wonders this solved my problems.