2.3.2. Alerts in Defender for Office 365
💡 First Principle: An alert is a signal that one thing happened; an incident is the story that several related signals tell together. Defender correlates alerts into incidents so analysts investigate attacks, not individual events.
Alert policies define which activities raise alerts. They live in the Defender portal at Email & collaboration > Policies & rules > Alert policy. Microsoft provides default alert policies covering, among others, elevation of Exchange admin privileges, malware campaigns, phishing campaigns, unusual volumes of file deletion or external sharing, and "Email reported by user as malware or phish". Some threat-management alert policies automatically trigger AIR investigations (Plan 2). You can create custom alert policies with a severity, a category and recipients for email notifications.
Permissions. Creating and managing threat-management alert policies requires the Organization Management or Security Administrator role groups in Email & collaboration permissions; Security Reader can view alerts. (Tenants using Defender XDR unified RBAC assign the equivalent permissions there instead.)
Where alerts go. Alerts appear in the Defender portal's Incidents & alerts queues and are grouped into incidents. Each incident shows the related alerts, the affected users and mailboxes, the evidence (messages, URLs, files), and — with Plan 2 — any automated investigations and pending actions. Built-in alert tuning rules can suppress repetitive benign alerts so the queue stays useful.
⚠️ Exam Trap: Alert policies are configured under Email & collaboration > Policies & rules, but alerts are triaged in the Incidents & alerts queues. A question about "reviewing" points to the queue; a question about "being notified when X happens" points to an alert policy.
Reflection Question: Your security lead wants an email whenever someone in the tenant shares an unusually large number of files externally in one day. Which object do you configure, and where would analysts then investigate the resulting signal?