---
title: "Locke vs Microsoft Purview Information Protection"
description: "Microsoft Purview governs documents and M365 apps. It has no reach into ChatGPT, Claude, or Gemini in the browser. Locke closes that gap with on-device detection before any prompt is submitted."
url: "https://sonomos.ai/compare/sonomos-vs-microsoft-purview/"
source: "https://sonomos.ai/compare/sonomos-vs-microsoft-purview/"
---

# Locke vs Microsoft Purview Information Protection

Microsoft Purview (formerly Azure Information Protection) is a mature DLP and labelling platform built deep into Microsoft 365. It is strong at classifying and protecting documents, email, Teams and SharePoint, and its AI Hub now adds AI controls. Its reach stops at the Microsoft 365 boundary. A prompt typed into ChatGPT or Claude sits outside it, and so does a labelled Word document pasted into another vendor's AI tool.

## When Microsoft Purview Information Protection fits

- Your organisation is deeply invested in Microsoft 365 and needs sensitivity labelling, encryption, and rights management across email, Teams, SharePoint, and Office documents.
- You need centralised policy management, compliance manager dashboards, and eDiscovery that spans the full Microsoft 365 estate.
- Your primary AI governance concern is Microsoft Copilot. Purview's AI Hub provides prompt auditing and policy enforcement within the M365 boundary.

## When Locke fits

- Employees use browser-based AI tools outside the Microsoft 365 boundary, such as ChatGPT, Claude, Gemini, Grok and Perplexity, where Purview has no reach.
- You need a control that acts at the moment of composition, before text is submitted, rather than after the document is classified.
- You want a zero-knowledge control: no prompt content is logged by the privacy vendor, unlike Purview's audit logs which capture prompt text.

## Side-by-side

| Dimension | Locke | Microsoft Purview |
| --- | --- | --- |
| Coverage of non-Microsoft AI tools | Works on supported browser-based AI chats: ChatGPT, Claude, Gemini and others. | Limited to Microsoft 365 apps and Copilot; no coverage of competitor AI tools. |
| Where controls operate | On the device, inside the browser, at the moment of composition. | At the Microsoft 365 layer: documents, email, Teams, SharePoint. |
| Sensitive-data visibility to the vendor | Zero-knowledge: Sonomos never sees prompt content. | Purview audit logs capture prompt text and policy matches, visible to your admin. |
| Rollout effort | Per-user, on-device Locke Early Access install: days to deploy at scale. | Deep integration with M365 tenant configuration: weeks to months. |
| Best for | Preventing sensitive data from reaching any browser-based AI tool. | Classifying, labelling, and protecting documents and communications within M365. |

## Bottom line

Purview and Locke protect different surfaces and work well together. Purview governs the Microsoft 365 estate: documents, email, Teams and Copilot. Locke screens the moment someone uses another AI tool it covers, such as pasting a labelled Word document into ChatGPT.

[Download Locke](https://sonomos.ai/downloads/)[See the Locke demo](https://sonomos.ai/locke/#demo)[See pricing](https://sonomos.ai/pricing/)[Talk to the team](https://sonomos.ai/contact/)

## Related comparisons

- [Locke vs Cloud-Based Data Loss Prevention](https://sonomos.ai/compare/sonomos-vs-cloud-dlp/)
- [Locke vs Enterprise Privacy Platforms](https://sonomos.ai/compare/sonomos-vs-enterprise-privacy/)
- [Locke vs AI API Gateways and Proxies](https://sonomos.ai/compare/sonomos-vs-ai-gateway/)

[View all comparisons](https://sonomos.ai/compare/)

## Further reading

- [The Best AI Privacy Tools for ChatGPT, Claude, and Gemini (2026)](https://sonomos.ai/blog/best-ai-privacy-tools-chatgpt-claude-gemini-2026/)
- [AI Data Leakage: 7 Ways Sensitive Information Escapes to LLMs (and How to Stop It)](https://sonomos.ai/blog/ai-data-leakage-7-ways-sensitive-info-escapes-to-llms/)
- [What Is PII Redaction? A Plain-English Guide for AI Users](https://sonomos.ai/blog/what-is-pii-redaction-ai/)