8.9 Automated Investigation and Response for Email
Automated Investigation and Response for Email
By the end of this subsection, you will understand how AIR automates email threat investigation, know the approval workflow, and be able to monitor AIR effectiveness.
How email AIR works
When Defender for Office 365 detects a phishing email or malware, AIR automatically:
- Identifies the threat — classifies the email as phishing, malware, or spam
- Scopes the campaign — finds all related emails (same sender, URL, or attachment hash)
- Identifies affected users — which mailboxes received the campaign
- Recommends remediation — soft delete from all affected mailboxes
- Executes or waits — depending on your automation level, either acts immediately or waits for analyst approval
Automation levels for email
| Level | AIR behavior | Best for |
|---|---|---|
| Require approval | AIR investigates and recommends. Analyst approves. | Starting point — human reviews every action |
| Auto-remediate confirmed threats | AIR remediates high-confidence malware/phishing automatically. Lower confidence waits for approval. | After 90 days of reviewing AIR recommendations with high accuracy |
| Full automation | AIR remediates all findings automatically | High-volume environments where analyst review is a bottleneck |
Email AIR handles email threats: soft-delete campaigns, block senders, submit for analysis. Endpoint AIR handles device threats: quarantine files, isolate devices. They are configured independently and operate in their respective domains. A cross-domain incident (phishing email leads to malware on device) triggers both.
Monitoring AIR effectiveness
| |
| TotalAlerts | AutoRemediated | PendingApproval | NoAction | AutoRate |
|---|---|---|---|---|
| 142 | 98 | 31 | 13 | 69.0% |
Without AIR, every phishing email triggers manual investigation: identify the campaign, find all recipients, check clicks, decide on remediation, execute soft-delete across all mailboxes. With AIR, steps 1-4 are automated. The analyst reviews and approves — a 5-minute task instead of a 30-minute investigation. At 30+ email threats per week, this is the difference between a manageable workload and alert fatigue.
Reviewing AIR investigations
When AIR completes an email investigation, review these elements before approving:
1. Scope accuracy: Did AIR identify all emails in the campaign? Compare the count against your manual Threat Explorer search. If AIR found 18 but you find 23, there are 5 emails AIR missed — remediate manually.
2. Verdict confidence: Check the confidence level of the phishing/malware classification. High confidence = approve quickly. Low confidence = review sample emails before approving.
3. Recommended actions: Is soft delete appropriate, or do some emails need hard delete (e.g., malware that users might restore from Recoverable Items)?
4. Affected users: Review the list of affected mailboxes. Any VIP users? Any service accounts? VIPs may need additional follow-up (Module 13.7 phone notification).
| |
| Week | Investigations | Remediated | Approved | Failed | SuccessRate |
|---|---|---|---|---|---|
| Week 1 | 12 | 8 | 3 | 1 | 67% |
| Week 2 | 18 | 14 | 4 | 0 | 78% |
| Week 3 | 31 | 27 | 3 | 1 | 87% |
Try it yourself
Reject the AIR recommendation. Then:
1. Allow the sender: Add the vendor domain to the Tenant Allow/Block List as an allowed sender.
2. Submit as false positive: Submit a sample email to Microsoft for analysis to improve detection accuracy.
3. Verify anti-phishing policy: Check if impersonation protection is flagging the vendor's display name as impersonating an internal user.
4. Communicate: Notify the user who reported the vendor's emails as suspicious (or whose mailbox triggered the alert).
This is why the approval workflow exists — to catch exactly this scenario. If this had been on full automation, 200 legitimate vendor emails would have been deleted.
Check your understanding
1. AIR identifies a phishing campaign affecting 200 mailboxes and recommends soft delete. Your automation is set to "require approval." What do you do?