The security operations team at Fabrikam wants to receive an email notification when Microsoft Defender for Office 365 detects that more than 10 users in the organization have received malware-containing emails within a one-hour window, indicating a potential malware campaign. What should the admin configure?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Alert policies in Defender for Office 365 are your tripwire. You define the event (malware detected), the threshold (more than 10 users, within 1 hour), and who gets the smoke signal (security team email). Once the tripwire is hit, the alert fires automatically. It's purpose-built for catching campaign-scale events rather than isolated incidents.
Full explanation below image
Full Explanation
Microsoft Defender for Office 365 alert policies (accessed via Microsoft 365 Defender > Alerts > Alert policies, or the Microsoft Purview compliance portal > Policies > Alert policy) allow administrators to define custom alerting rules with precise thresholds and notification targets. For a malware campaign scenario, the admin creates an alert policy with: Activity = 'Detected malware in email messages', Threshold = 'Activity count is greater than 10 events in 1 hour', Severity = High, and Notification = email addresses of the security operations team. This gives the team timely, actionable notification when the volume of malware detections suggests a coordinated campaign rather than isolated incidents.
Option A (Purview retention policy) is a data lifecycle management tool, not a security alerting tool. Retention policies determine how long content is kept or deleted — they have no ability to detect security events or send alert notifications based on malware detection activity.
Option C (Conditional Access blocking email access) is disproportionate and impractical. You cannot configure Conditional Access to dynamically monitor malware event counts and then block email access — Conditional Access policies evaluate conditions at sign-in time, not continuously against threat intelligence event thresholds. This would also block legitimate users from accessing email during an incident, compounding the problem.
Option D (Microsoft 365 service health alerts) notifies administrators about Microsoft 365 service degradation or outages — incidents where Microsoft's infrastructure is experiencing issues. Service health does not report on tenant-specific threat detections. When malware is found in Fabrikam's emails, that is a tenant-level security event, not a Microsoft service health event.
Exam tip: Alert policies support several activity types beyond malware: phishing detections, user-reported phishing, DLP policy matches, and more. Custom alert policies are also available in the Microsoft Purview compliance portal for compliance-specific events. Know the difference between alert policies (custom threshold-based alerting) and default alerts (pre-built alerts from Microsoft that are always on, such as 'Malware campaign detected').