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

Call Manager 4.2 database issue after a publisher failure

on
This is a post for future reference. A customer of mine experienced some strange symptoms on their CUCM’s this week. And it took me some time to figure out what and why.
Issue at hand: When logging on to ccmadmin on the publisher, several ip-phones where not registered. But the phones were operational, and showed no sign of error. When logging on to the subscriber, I found all of the “not registered” phones registered. But all phones registered on the publisher was here “not registered”.
Troubleshooting: I tried booting the CUCMs but it did not help. I tried to restart services and manually fail over phones to one of the CUCMs. But the result was always the same. Whichever CUCM which did not have the phones registered, listed the phones as "not registered”.
Resolution: I’ve seen this before, and suspected a broken SQL link. Running DBHelper confirmed my suspicions, and fixed part of my problems. After recreating the publish/subscribe link in SQL, I expected the call managers to perform normally. But not so. I then booted the subscriber, but nothing changed. Only after booting the publisher first, then followed by the subscriber fixed the problem entirely.