Configure conditions for key communication compliance scenarios
This article provides multiple examples of creating conditions with the condition builder in Microsoft Purview Communication Compliance. Use the examples for your own scenarios and modify as needed for your organization.
For general information on creating conditions for communication compliance policies, see Choose conditions for your communication compliance policies.
Data security examples
Example 1: Detect all communications sent outside of Contoso.com that contain patterns detected by the Insiders sensitive info type OR that include any of these keywords: "confidential", "top secret", "Project Sparta", "GenAI"
Example 2: Detect all communications coming from outside or sent outside contoso.com that contain patterns detected by the Insiders sensitive info type
Example 3: Proactively detect sharing of secret keys and passwords outside of contoso.com
Example 4: Detect Teams phishing requests sent as multifactor authentication requests by using the Phishing Patterns sensitive info type
Example 5: Analyze all messages coming from the stateactor1.com, stateactor2.com, and stateactor3.com domains OR messages containing these keywords: recruit, payment for your services, good offer, hiring, recruitment
Example 6: Analyze specific emails sent to external domains by detecting patterns using the Personal sensitive info type, but ignore specific keywords
Example 7: Analyze and view all emails sent to personal email accounts
Business conduct examples
Example 8: Detect inappropriate content sent in messages by using the Sexual, Violence, Hate, and Self-harm trainable classifiers OR by using a curated keyword dictionary
Example 9: Detect threats and harassment addressed to Contoso's key executives by using the Targeted Harassment, Threat, and Hate trainable classifiers
Example 10: Detect all messages that contain patterns detected by the ABA Routing Number, Credit Card Number, U.S. Bank Account Number, U.S. Individual Taxpayer Identification Number (ITIN), and U.S. Social Security Number (SSN) sensitive information types sent by any employee, but not sent to or sent by the Finance Team
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for