Regaining Control Over Unmanaged GenAI Apps: New Microsoft Purview Enhancements in Edge

Many organizations are growing increasingly concerned about the widespread use of unsanctioned Generative AI (GenAI) tools. These apps, often accessed through unmanaged browsers, pose significant risks to data security and compliance. To help with this, Microsoft is now updating some features in  Microsoft Purview that will enhance policy enforcement for unmanaged cloud apps accessed via the Edge browser.  What’s Changing? Previously, enforcing Purview Data Loss Prevention (DLP) and Collection policies required manual creation of Edge configuration policies. These policies were often complex and needed to be scoped correctly to block unsupported browsers or apply protections. With this update, Microsoft automates much of that process: Collection Policies now apply directly within Edge without needing a separate blocking configuration. DLP Policies automatically generate Edge configuration policies that align with the scope of the DLP rules. DLP policies can operate in two mode...

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 :)