Municipal HR/payroll reviews a Communication Compliance policy violation in a crew Teams chat. What are they identifying?

When municipal HR/payroll reviews a Communication Compliance policy violation in a crew Teams chat, they are identifying a potential Communication Compliance policy violation involving risky or inappropriate workplace communications. That Purview capability evaluates communications channels such as Teams for policy-defined conduct risks and surfaces findings for authorized reviewers—exactly the HR/payroll scenario in the stem.

A potential Communication Compliance policy violation involving payroll data exfiltration blocked by DLP policy fails: payroll exfiltration blocked by DLP policy is a DLP enforcement outcome, not a Communication Compliance conduct finding for risky or inappropriate workplace communications in crew Teams chat. A potential Communication Compliance policy violation involving anomalous access to payroll systems during review fails: anomalous access to payroll systems is an insider-risk-type access anomaly, not a Communication Compliance conduct finding for risky or inappropriate workplace communications in crew Teams chat. A potential Communication Compliance policy violation involving restricted external sharing by sensitivity labels fails: restricted external sharing by sensitivity labels is a labeling/protection enforcement outcome, not a Communication Compliance conduct finding for risky or inappropriate workplace communications in crew Teams chat.

Exam caveat: AB-900 expects you to identify Communication Compliance findings as risky/inappropriate communications issues. Privacy and role-based access for reviewers matter in real tenants; the exam item focuses on recognizing the class of finding, not configuring reviewer RBAC in depth.

Operational check: Confirm the HR/payroll reviewer role can open the Communication Compliance match, preserve chat context per policy, escalate per municipal HR procedures, and avoid conflating the case with payroll data exfiltration blocked by DLP policy, anomalous access to payroll systems during review, or restricted external sharing by sensitivity labels in the service desk.