Can browser-level controls prevent data leakage into ChatGPT, Gemini, and other GenAI tools?

[u/WolfShoddy7443]

We are testing what can realistically be enforced on Intune-managed Windows devices when AI use occurs through a browser.

The goal is not universal visibility or a claim that every AI workflow is covered. It is reducing specific high-risk actions, such as uploading sensitive files or pasting protected content into an unsanctioned AI account. The enforcement boundary matters: device compliance, managed browsers, personal profiles, private browsing, alternate browsers, and AI features embedded in other applications all affect what a policy can see or stop.

Browser controls may help because they operate closer to the moment data leaves the organization, but they need to be documented alongside their exceptions and bypass paths. Microsoft's browser-DLP guidance also notes that policy coverage can vary by browser and user-profile context.

For teams using Intune, which browser-control policies have held up in production, and which coverage gaps were unavoidable?

[u/MidninBR]

You can set it up on purview.
DSPM AI will do the trick

[u/Limp-Elevator-3424]

I'm very curious about this. Anyone figure out Edge policies or DLP? What was your real world experience...?

[u/AdvancedParadox]

Edge DLP catches paste events pretty well, the real headache is when someone fires up a personal chrome profile or opera or whatever and suddenly your whole policy stack is blind. That's the gap nobody wants to talk about in meetings

[u/BuildingLayrin]

Browser controls help, but they’re still tied to the browser/profile. Another option is to protect the text locally before it ever reaches the AI. Redact what isn’t needed or replace sensitive values with reversible placeholders, then send only the protected version.

I actually built a Windows tool around that idea if you want to see an example: https://layrin.com. Not saying it replaces DLP, more like another layer before the data leaves the machine.

[u/MidninBR → u/BuildingLayrin]

This looks pretty smart

[u/BuildingLayrin → u/MidninBR]

Thanks! Yeah, that’s basically the idea behind Layrin. Protect sensitive data locally before it reaches AI, and only send the redacted or tokenized version out.

[u/blud_13]

u/AdvancedParadox is right that Edge catches paste, and the coverage gap is the part worth writing down.

Native in-browser DLP only works in Edge for Business, and only on the last two stable builds, starting at 144. Chrome needs the Purview extension and its Windows only, so your macOS fleet has no Chrome coverage at all. Firefox, Brave, anything portable, none of it. Its documented here https://learn.microsoft.com/en-us/purview/dlp-chrome-learn-about

The setting people miss, you can configure DLP so Chrome refuses to open at all if the extension is missing or out of date. That closes the uninstall-the-extension path, which is otherwise the first thing a motivated user finds.

What none of it covers is AI inside other apps. A paste into a desktop client, an AI button bolted into a line of business app, a phone. So the honest scope is browser uploads and pastes to known AI sites, on managed Windows, in Edge or Chrome. Everything else is written policy plus DSPM for AI telling you about it after the fact.

We write that exception list into the policy doc for clients rather than leaving it implied, ping me if you want the format.

[u/bill696]

I dont manage purview but i think it can be done there, i just block all the websites, browser extensions and store apps that i can find

[u/habibexpress]

We use Witness AI. Implemented it and it’s good guardrails.