An emergency-management office wants to reduce accidental Social Security number leakage from benefits case email. Which Purview capability fits?

An emergency-management office reducing accidental Social Security number leakage from benefits case email should use Microsoft Purview Data Loss Prevention to detect and help prevent sensitive data exfiltration. DLP policies can find sensitive information types such as SSNs in email (and other locations) and apply educate, warn, block, or encryption-related actions aligned to municipal policy.

Microsoft Purview Information Protection can detect and help classify sensitive benefits email content with sensitive info types and sensitivity labels, but classification alone does not prevent SSNs from leaving in outbound mail; a DLP policy is still required to detect and block that exfiltration. Microsoft Purview Insider Risk Management can detect and help review risky insider activity signals across activity patterns, but it does not scan outbound email content for SSNs or block that exfiltration in mail flow. Microsoft Purview Communication Compliance can detect and help review message policy violations such as harassment or regulatory breaches, but it does not block SSN exfiltration in mail flow; it routes flagged messages for human review rather than preventing sensitive data exfiltration.

Exam caveat: Accidental leakage of regulated data types in email maps to Purview DLP. Information Protection classification help, Insider Risk Management signal review, and Communication Compliance message review detect or flag content for review but do not prevent SSN exfiltration in outbound mail.

Operational check: Create or refine a Purview DLP policy scoped to emergency-management and benefits mailboxes, include U.S. SSN or relevant sensitive info types, start in audit/warn mode, review false positives with caseworkers, then enforce block or require override justification for external recipients per city legal guidance.