Study guide
7.1 Sentinel as SIEM and SOAR
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.1 Sentinel as SIEM and SOAR
Key Takeaways Explain This Topic AI
Microsoft Sentinel (formerly Azure Sentinel) is a cloud-native SIEM and SOAR platform built on a Log Analytics workspace.
SIEM collects and analyzes security signals to detect threats; SOAR orchestrates and automates the response.
Sentinel ingests from Microsoft and non-Microsoft sources, making it the cross-source single pane of glass.
Defender XDR is an XDR for Microsoft sources; Sentinel is the broader SIEM that can ingest Defender XDR incidents.
On SC-900, Sentinel sits in the Microsoft security solutions domain (~25-30% of the exam).
Last updated: June 2026
What Microsoft Sentinel Is
Microsoft Sentinel (formerly Azure Sentinel — the rebrand is commonly tested) is Microsoft's cloud-native SIEM and SOAR platform. SC-900 places it in the third skill area, Capabilities of Microsoft security solutions (roughly 25-30% of the exam), alongside Microsoft Defender for Cloud and Microsoft Defender XDR. You do not need to operate a Security Operations Center (SOC) to pass; you need to recognize when Sentinel is the right answer and how its parts fit together.
SIEM stands for Security Information and Event Management . It is the collection and analysis side of security operations: a SIEM ingests logs and security signals from across the estate, normalizes them, and analyzes them to detect threats and support investigation . SOAR stands for Security Orchestration, Automation, and Response . It is the response side: it coordinates and automates the actions a team takes after a threat is found, reducing manual, repetitive work. Sentinel delivers both in one service, which is why scenarios that pair detection with automated response point so cleanly to it.
Acronym Full name What it does in Sentinel
SIEM Security Information and Event Management Ingest, store, and analyze logs to detect and investigate threats
SOAR Security Orchestration, Automation, and Response Automate and orchestrate response via playbooks and automation rules
- UEBA User and Entity Behavior Analytics Baseline normal behavior to surface anomalous users/entities
- KQL Kusto Query Language The query language used by analytics rules and hunting
Sentinel is cloud-native : there is no server to deploy, patch, or scale. It runs as a service on top of an Azure Monitor Log Analytics workspace , which stores the ingested data, and you pay primarily for the volume of data ingested and retained. Because it is a managed Azure service, capacity scales elastically, a contrast the exam likes to draw against legacy, appliance-based SIEMs.
Sentinel vs. Defender XDR — the Selection Trap
The single most-tested distinction in this chapter is Sentinel (SIEM) vs. Microsoft Defender XDR (XDR) . XDR (Extended Detection and Response) automatically collects, correlates, and analyzes signals across a defined set of Microsoft workloads — endpoints, identities, email and collaboration, and cloud apps — and presents unified incidents with little setup. SIEM is broader and source-agnostic: Sentinel ingests from Microsoft and third-party and on-premises sources (firewalls, network gear, AWS, Google, syslog, custom apps) to give enterprise-wide visibility .
The two are complementary. Defender XDR can act as a high-fidelity data connector into Sentinel , feeding its correlated incidents upward so a SOC gets one cross-estate view and can hunt and automate on top of everything. Use these cues:
"Microsoft 365 / Microsoft workloads only, automatic correlation" -> Defender XDR.
"Aggregate logs from many sources, including non-Microsoft, into one SIEM" -> Microsoft Sentinel.
"Detect and automatically respond (SOAR)" -> Microsoft Sentinel.
Keep these product lanes separate
A second trap is sending a non-security task to Sentinel. If the prompt asks for sensitivity labels, DLP, retention, eDiscovery, audit, or Compliance Manager , the answer is Microsoft Purview . If it asks for access reviews, Conditional Access, PIM, or identity risk , the answer is Microsoft Entra . Sentinel owns the SIEM/SOAR, analytics, hunting, workbooks, and playbooks language.
- Scenario language Product
- SIEM, SOAR, cross-source log aggregation, automated response Microsoft Sentinel
- Correlated incidents across Microsoft endpoints/identity/email/apps Microsoft Defender XDR
- Sensitivity labels, DLP, retention, eDiscovery, compliance score Microsoft Purview
- Access reviews, Conditional Access, PIM, identity protection Microsoft Entra
Keep a simple mental sequence for any Sentinel question: connect data, detect with analytics, investigate via incidents and hunting, visualize with workbooks, and respond with automation rules and playbooks. Recognizing that flow is most of what SC-900 asks for.
The End-to-End Sentinel Workflow
Almost every Sentinel exam question maps to one stage of a single end-to-end pipeline, so learning the stages in order makes scenario questions easy to place. Data connectors ingest logs and alerts from across the environment into the Log Analytics workspace, where they become normalized, queryable tables. Analytics rules run queries over that data on a schedule, and when their logic matches they raise alerts.
Microsoft's built-in machine learning, including the Fusion engine, correlates weak or unrelated signals into high-confidence incidents, while User and Entity Behavior Analytics baselines normal behavior to surface anomalies and threat intelligence enriches detections with known indicators of compromise.
Stage three is investigation. Sentinel groups related alerts into incidents that a security analyst owns, prioritizes, and works, supported by an investigation graph and by proactive hunting across the same data. Stage four is visualization. Workbooks turn the data and incidents into interactive dashboards for monitoring and reporting. Stage five is response. Automation rules orchestrate triage, and playbooks built on Logic Apps run the actual remediation steps, such as disabling a compromised account or isolating a device.
The terms map cleanly to SIEM and SOAR. The SIEM role covers stages one through four — collect, detect, investigate, and visualize. The SOAR role covers stage five — orchestrate and automate response. When a question pairs broad, multi-source detection with automated, repeatable response, only one Microsoft product spans both halves end to end, and that is Microsoft Sentinel.
Finally, remember the positioning facts SC-900 favors. Sentinel is a paid Azure service billed mainly by data volume, has no hardware to manage, is the single pane of glass that unifies signals a SOC would otherwise chase across many consoles, and is the natural place to aggregate the high-fidelity incidents Microsoft Defender XDR produces. Holding the pipeline and these facts in mind lets you answer feature, selection, and definition questions confidently.