Study guide

11.2 Incidents, Alerts & Advanced Hunting

Microsoft 365 Administrator Expert MS-102

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 MS-102 Exam Facts & Blueprint 1.2 Registration, Retake & Renewal 1.3 Study Strategy & Using This Guide

2 Tenant Setup, Domains & Org Settings

2.1 Creating a Microsoft 365 Tenant 2.2 Implementing and Managing Domains 2.3 Configuring Org Settings: Security, Privacy & Profile

3 Service Health, Network & Software Updates

3.1 Monitoring Service Health & Notifications 3.2 Network Connectivity Insights 3.3 Configuring & Monitoring Software Updates

4 Adoption, Usage & Microsoft 365 Backup

4.1 Monitoring Adoption & Usage 4.2 Configuring & Managing Microsoft 365 Backup

5 Users, Contacts, Groups & Shared Mailboxes

5.1 Creating & Managing Users Including External Users 5.2 Creating & Managing Contacts 5.3 Managing Microsoft 365 Groups & Shared Mailboxes

6 Licensing & Bulk User Management

6.1 Managing & Monitoring Microsoft 365 Licenses 6.2 Bulk User Management with Graph & Entra PowerShell

7 Roles, Admin Units & Privileged Identity Management

7.1 Implementing & Managing Roles in M365 & Entra ID 7.2 Managing Permissions for Defender XDR, Purview & Workloads 7.3 Managing Delegation with Administrative Units 7.4 Managing Entra ID Roles in PIM

8 Identity Synchronization with Entra Connect

8.1 Preparing for Identity Synchronization & IdFix 8.2 Directory Sync with Entra Connect Sync & Cloud Sync 8.3 Monitoring Sync with Entra Connect Health 8.4 Troubleshooting Synchronization

9 Authentication, SSPR & Password Protection

9.1 Implementing & Managing Authentication Methods 9.2 Self-Service Password Reset (SSPR) 9.3 Microsoft Entra Password Protection 9.4 Investigating & Resolving Authentication Issues

10 Identity Protection, Conditional Access & MFA

10.1 Planning for Identity Protection 10.2 Implementing Entra Identity Protection 10.3 Planning & Implementing Conditional Access Policies 10.4 Managing MFA with Conditional Access

11 Defender XDR Posture, Incidents & Threat Intelligence

11.1 Security Exposure Management & Secure Score 11.2 Incidents, Alerts & Advanced Hunting 11.3 Reviewing Defender XDR Reports 11.4 Defender Threat Intelligence

12 Defender for Office 365: Policies, Alerts & Investigation

12.1 Threat Policies & Rules in Defender for Office 365 12.2 Configuring Alert Policies 12.3 Investigating & Responding to Email Threats

13 Attack Simulation & Restricted Entities

13.1 Managing Attack Simulations & Training 13.2 Managing Restricted Entities & Blocked Users

14 Defender for Endpoint

14.1 Onboarding Devices to Defender for Endpoint 14.2 Configuring Endpoint Settings 14.3 Defender Vulnerability Management Dashboard

15 Defender for Cloud Apps

15.1 Configuring the App Connector for Microsoft 365 15.2 Defender for Cloud Apps Policies & Alerts 15.3 Interpreting the Activity Log 15.4 Cloud App Discovery

16 Purview Information Protection & Data Lifecycle

16.1 Sensitive Information Types 16.2 Retention Labels & Policies 16.3 Sensitivity Labels & Policies 16.4 Monitoring Label Usage: Content & Activity Explorer

17 Purview Data Loss Prevention

17.1 DLP Policies for Microsoft 365 Workloads 17.2 Configuring Endpoint DLP 17.3 Reviewing & Responding to DLP Alerts, Events & Reports

18 Final Review & Exam Strategy

18.1 Exam-Day Strategy & Question Handling 18.2 Final Review Checklist & Next Steps

11.2 Incidents, Alerts & Advanced Hunting

Key Takeaways Explain This Topic AI

A Microsoft Defender XDR incident aggregates correlated alerts from Defender for Endpoint, Defender for Office 365, Defender for Identity, Defender for Cloud Apps, and Entra ID into a single view with an investigation graph

Response actions available from the incident view include contain user, isolate device, restrict a cloud app, and block email — each maps to a specific workload's enforcement plane

Advanced hunting is a Kusto Query Language (KQL) query tool over up to 30 days of raw event data across device, email, identity, and cloud app tables in the Microsoft Defender portal

Shared and custom advanced hunting queries let teams codify hunts; supported actions can be taken directly on query results, including initiating detections on entities found

Triage an incident by assigning an owner, classifying it (true/false positive, with a determination), and managing its status through the incident queue

Last updated: August 2026

Quick Answer: A Microsoft Defender XDR incident is a correlated group of alerts across Defender for Endpoint, Defender for Office 365, Defender for Identity, Defender for Cloud Apps, and Entra ID, presented as one investigation unit. Advanced hunting lets you query up to 30 days of raw event data with Kusto Query Language (KQL) to proactively find threats that alerts missed.

The Incident Model

Microsoft Defender XDR's core value proposition is correlation across workloads . A phishing email that lands in a user's inbox (Defender for Office 365), leads to a suspicious sign-in from a new location (Entra ID), and triggers endpoint behavior on the user's device (Defender for Endpoint) would, in a siloed model, produce three unrelated alerts. Defender XDR correlates them into a single incident so an analyst sees the whole story and responds once, not three times.

Incident Properties

Severity — Low, Medium, High, or Informational, derived from the underlying alerts and impacted assets.

Status — New, In progress, or Resolved, tracked in the incident queue.

Categories — e.g., Impact, Malware, Initial access, Credential access, Exfiltration, mapped to MITRE ATT&CK tactics.

Impacted assets — devices, users, mailboxes, and apps, with the related alerts grouped under each.

Owner — the analyst assigned to investigate and resolve.

Classification — set on resolution: true positive (with a determination such as malware, phishing, or unwanted software), false positive, or informational activity expected.

The Investigation Graph

The investigation graph visualizes the entities (devices, users, IPs, files, emails, apps) and the relationships between them for an incident. It is the fastest way to understand blast radius — which accounts and devices an attacker touched — and to choose which response actions to apply first.

Responding to Incidents

From an incident (or an individual alert), an administrator can take workload-specific response actions without leaving the Defender portal:

Action Workload What it does

Isolate device Defender for Endpoint Disconnects the device from the network while keeping Defender connectivity for remediation

Contain user Entra ID / Defender for Identity Blocks sign-in and invalidates active sessions for a compromised account

  • Restrict app Defender for Cloud Apps Suspends or requires step-up auth for a connected SaaS app session
  • Block email Defender for Office 365 Removes or blocks delivery of a malicious message across the tenant

Run antivirus scan Defender for Endpoint Triggers a full or quick Microsoft Defender Antivirus scan on a device

  • Collect investigation package Defender for Endpoint Packages forensic data from a device for analysis
  • Incident Workflow

Triage — review the incident queue, sort by severity or impacted business-critical asset, and decide what to act on first.

Assign — set an owner so accountability is clear.

Investigate — read the alert story, open the investigation graph, and review the evidence per entity.

Respond — apply the appropriate response actions from the table above.

Classify and resolve — mark as true positive (with a determination) or false positive, set status to Resolved, and add notes for the post-incident review.

Advanced Hunting

Advanced hunting is a query-based threat-hunting tool in the Microsoft Defender portal. It exposes up to 30 days of raw event data from Defender for Endpoint, Defender for Office 365, Defender for Identity, Defender for Cloud Apps, and Entra ID using Kusto Query Language (KQL) — the same query language used by Azure Data Explorer and Microsoft Sentinel.

The Schema (conceptually)

Advanced hunting organizes data into tables by domain. You do not need to memorize every column for the exam, but you should recognize the major tables:

  • Table Domain Example events
  • DeviceEvents Endpoint Process creation, registry, file, network events
  • EmailEvents Email Mail flow, delivery, verdicts
  • IdentityEvents Identity Sign-ins, identity sensors (Defender for Identity)
  • CloudAppEvents Cloud apps SaaS activity from Defender for Cloud Apps
  • AlertInfo / AlertEvidence Alerts Alerts and the entities linked to them
  • A Simple Example Query

The query below finds processes launched by Office applications on endpoints in the last 7 days — a classic macro-execution pattern worth reviewing: DeviceProcessEvents

  • | where InitiatingProcessFileName in~ ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")
  • | where Timestamp > ago(7d)
  • | project Timestamp, DeviceName, FileName, FolderPath, InitiatingProcessFileName
  • | order by Timestamp desc

This is illustrative only — you are not expected to write KQL on the exam — but you should be able to read it at a conceptual level: filter the DeviceProcessEvents table to rows where the initiating process is an Office app, restrict to the last 7 days, project the interesting columns, and sort newest first.

Shared and Custom Queries

The advanced hunting experience ships with shared queries curated by Microsoft and the community, and lets you save custom queries for your tenant. From a query result you can take supported actions directly on matched entities — for example, initiate an antimalware scan on a device, add an indicator to Defender for Endpoint, or open an entity's page for deeper investigation.

How Incidents and Advanced Hunting Connect

A common workflow is to start from an incident's indicators (a file hash, a sender address, an IP), pivot into advanced hunting with a query that searches the whole tenant for those same indicators across the last 30 days, and then — if you find more impacted assets — add them to the incident or open a new one. This is the essence of "review and respond" at the MS-102 level.