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

Lync owas windows 8_1 bug

** UPDATE **
The bug has been fixed in the following update: http://support.microsoft.com/kb/2837634
You might have to break the farm, and recreate it after the update.
**/UPDATE**

There is a known bug affecting windows 8.1 users when they try to present a PowerPoint presentation in any meeting. If you have installed any version of Windows 8.1 and tried it, you might have seen the all too familiar screen:


If you have tried to debug the error, you might be as frustrated as me, because there is (at least I was not able to find any) no visible error on any server or client component. Even a Fiddler trace revealed nothing but 200 OK messages.

This bug is not present in Lync Online, and I hope we'll see a bugfix for the onprem installations as well soon.

In the meantime, do as I did to correct the error. Join your meeting through the web browser, appending ?sl=2 to your meet url. At least I was able to run the presentation through my webapp.


Hope this helps, and that we see a bugfix soon :)