Pular para o conteúdo principal

Protect sensitive AI prompts and files with Microsoft Purview network DLP

Implementation Effort: Medium - Requires joint network and data-protection ownership of acquisition, inspection, policies, and monitoring.
User Impact: Medium - Sensitive content can be blocked; inspection limits and false positives need operational handling.

Overview​

Global Secure Access (GSA) content policies can use Scan with Purview to inspect supported text and files for Microsoft Purview data loss prevention (DLP) decisions. This extends protection beyond destination blocking to sensitive content exchanged with unmanaged or cloud AI applications.

This supports Use least privilege access for data movement and Assume breach by adding inline controls on eligible traffic. Basic content filtering, collection-only policies, and Purview-backed enforcement remain different capabilities.

Prerequisites​

  • Complete AI network readiness, including acquisition and Transport Layer Security (TLS) inspection.
  • Appropriate GSA/Purview administrative roles and licensing. The supplied licensing reference lists Microsoft 365 E7 or Purview E5/equivalent plus Entra Internet Access/equivalent for this integration.
  • Traffic mapped to an Entra user identity.
  • Matching GSA content-policy and Purview DLP scope, joint operational ownership, a pilot scope, and approved synthetic test data.

Limitations​

  • GSA Scan with Purview supports content up to 3 MB for both files and text; optical character recognition (OCR) is not supported.
  • Oversized content or inspection errors can fail open. PurviewStatus identifies skipped inspection; API rate-limit exceedance is separately documented as fail-closed.
  • Encoded or chunked transfers can evade supported file detection. WebSocket file-type filtering is bypassed, although text type is still evaluated.
  • Basic Allow/Block content rules do not create Purview investigation records; collection alone does not prove blocking.
  • Agent-only, anonymous, or identity-unmapped traffic is not automatically eligible. Copilot Studio baseline traffic must not be assumed Purview-scanned without supported identity mapping and feature coverage.

Reference​