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

More OCS challenges

on
Ok, So I have the basics up and running, but is it working? Aperantly, yes.
Front end and backend now run without errormessages, and I can chat, call and use livemeeting on all the clients.

I decided not spend to much time on running around, installing applications, so I am using AD Group policies to deploy the applications. Here is a quick rundown of what I did:

Livemeeting:
  • Download software from www.livemeeting.com (Remember to download both client and outlook plugin)
  • Convert exe files to .msi files by running "LMsetup.exe -out c:\temp" (presuming c:\temp exists)
  • Create a GPO for distribution (Assign or publish, Computer or User - It depends on your preference)
  • Create Groups for filtering of the GPO
  • Add objects to the groups
  • Remove "authenticated users" from the filtering, add the desired group.
Attendant:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.

Office Communicator:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.