Study guide

7.3 Analytics Rules, Incidents, and Detection

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

7.3 Analytics Rules, Incidents, and Detection

Key Takeaways Explain This Topic AI

Analytics rules evaluate ingested data with KQL to detect threats and generate alerts that become incidents.

Rule types include scheduled (KQL), Microsoft security (promote Defender alerts), Fusion (ML multistage attack detection), anomaly, and near-real-time (NRT).

An incident groups related alerts and entities into one investigation case with a severity and status.

Fusion uses machine learning to correlate low-fidelity alerts into high-fidelity multistage attack incidents.

Detection (analytics) is automated and rule-driven; hunting is analyst-driven proactive search.

Last updated: June 2026

From Analytics Rules to Incidents

Analytics rules are Microsoft Sentinel's detection engine . A rule runs a query — usually written in Kusto Query Language (KQL) — over the data that connectors have ingested, on a schedule. When the rule's logic matches, it produces an alert . Sentinel then groups related alerts (and the entities they reference, such as users, hosts, and IP addresses) into an incident : a single case with a severity , status (New / Active / Closed), and owner that the SOC investigates.

The direction is fixed and exam-friendly: connectors -> data -> analytics rule -> alert -> incident -> investigation/response. Recognizing that an analytics rule detects and an incident organizes the investigation is most of what SC-900 wants.

Sentinel offers several rule types. You do not need to author them, but recognizing the names helps:

  • Rule type What it does
  • Scheduled Runs a custom KQL query on a schedule; the most common, flexible rule
  • Microsoft security Automatically creates Sentinel incidents from alerts raised by Microsoft Defender products

Fusion Uses machine learning to correlate many low-fidelity signals into high-fidelity multistage attack incidents

  • Anomaly Built-in machine-learning templates that flag unusual behavior
  • Near-real-time (NRT) Runs about once per minute for faster detection of time-sensitive threats

Fusion is worth remembering specifically: it is the machine-learning correlation engine that connects seemingly unrelated, individually weak alerts into a single incident describing a probable multistage attack , dramatically reducing alert noise. When a prompt mentions ML-based correlation of multiple signals into one high-confidence incident, Fusion is the concept.

Detection vs. Hunting, and Selecting Sentinel

Detection and hunting are easy to confuse. Analytics rules are automated, predefined detection logic that runs continuously and raises incidents on its own. Hunting (next section) is analyst-driven, proactive exploration of the same data looking for threats no rule caught yet. Both rely on ingested data and both feed investigation, but they start from opposite modes — automatic vs. manual.

Use verbs in the prompt to pick the right Microsoft product area:

Detect, correlate, alert, raise an incident, mitigate a threat -> Microsoft Sentinel (analytics/incidents).

Approve access, review entitlements, activate a privileged role, detect identity risk -> Microsoft Entra .

Label, retain, discover sensitive data, support eDiscovery -> Microsoft Purview .

Analytics rules also help you keep Sentinel apart from individual Defender products. A Microsoft security analytics rule is exactly the bridge that pulls Defender alerts into Sentinel as incidents — that is how XDR signals gain SIEM-wide context. But if the scenario is purely "protect endpoints" or "protect mailboxes," the right answer is the specific Defender product, not Sentinel.

  • Cue in the scenario Best match
  • Custom KQL detection on ingested logs Sentinel scheduled analytics rule
  • ML correlation of weak signals into a multistage attack incident Sentinel Fusion
  • One case grouping related alerts and entities to investigate Sentinel incident
  • Bring Defender alerts into the SIEM as incidents Sentinel Microsoft security rule

For SC-900, you are matching products and recognizing vocabulary, not writing detections. Know that analytics rules detect , incidents organize the investigation , Fusion adds ML correlation , and all of it lives in Microsoft Sentinel's SIEM role.

The Life of an Incident

Understanding what happens to an incident after it is created helps you answer investigation-flow questions. A new incident arrives with a severity (Informational, Low, Medium, or High) and a status of New. An analyst, or an automation rule, assigns an owner and moves it to Active while it is being worked, then to Closed with a classification such as true positive, benign positive, or false positive once resolved.

Throughout, the incident carries its grouped alerts and entities — the users, hosts, IP addresses, files, and URLs involved — so the analyst can see the full picture in one case rather than chasing isolated alerts.

Sentinel supports the investigation with several built-in aids. The investigation graph visually maps the relationships among the entities and alerts in an incident, letting an analyst pivot from a suspicious account to the devices it touched to the IP addresses it used. Entity pages summarize everything Sentinel knows about a single user or host. And because Sentinel can ingest Microsoft Defender XDR incidents through a Microsoft security analytics rule, a single Sentinel incident can carry context that originated across endpoints, identities, email, and cloud apps.

  • Incident attribute Possible values Purpose
  • Severity Informational, Low, Medium, High Prioritize analyst attention
  • Status New, Active, Closed Track investigation progress
  • Classification True positive, benign positive, false positive Record the outcome on closure
  • Owner A user or group Assign responsibility

For SC-900 you will not run an investigation, but recognizing this lifecycle clarifies why incidents are the heart of Sentinel's SIEM role : they convert raw alerts into a managed, prioritized, ownable unit of work. When a scenario describes grouping related alerts, assigning severity, tracking status, or reviewing the entities involved in suspicious activity, the concept is a Sentinel incident, and the detection that produced it traces back to an analytics rule running over connected data.