A housing authority sees inspectors emailing unredacted resident IDs and wants a Purview control that can warn or block that sharing. Which capability fits?

A housing authority whose inspectors email unredacted resident IDs and wants a Purview control that can warn or block that sharing should use Microsoft Purview Data Loss Prevention policies that detect sensitive IDs in email. DLP is built to match sensitive information types in transit and apply user notifications, warnings, or hard blocks to reduce accidental disclosure of resident identifiers.

Microsoft Purview sensitivity label policies publish and auto-apply labels to classify and protect email, but they do not inspect mail flow to warn or block sends containing sensitive IDs the way a DLP policy does. Microsoft Purview Insider Risk Management policies correlate behavioral indicators to identify risky insider activity and trigger review workflows, but they do not block sensitive IDs in email at send time. Microsoft Purview Communication Compliance policies detect conduct and regulatory violations in communications for reviewer follow-up, but they do not warn or block resident ID sharing in mail flow.

Exam caveat: Warn/block on sensitive email content is the DLP action model. Sensitivity label policies, Insider Risk Management policies, and Communication Compliance policies test whether you confuse adjacent Purview governance and risk capabilities with content DLP.

Operational check: Scope a DLP policy to housing inspector mail flow, detect resident ID sensitive info types, configure warn-and-allow or block for external sends, educate inspectors on redaction before send, and monitor DLP match reports for repeat offenders and policy tuning.