L15. Microsoft Sentinel Fundamentals
Course outlineLesson 15 of 18
Microsoft Sentinel is the AZ-500's cloud-native SIEM and SOAR platform. Learn workspaces, data connectors, analytics rules, incidents, and the KQL queries the exam expects you to recognise.
Exam update: AZ-500 retired on August 31, 2026. Continue current security operations study in SC-500 and SC-200.
Microsoft Sentinel is available in the Microsoft Defender portal. After March 31, 2027, Sentinel will no longer be supported in the Azure portal and will be available only in the Defender portal.
What Is Microsoft Sentinel?
Microsoft Sentinel is a cloud-native Security Information and Event Management (SIEM) and Security Orchestration, Automation, and Response (SOAR) solution built on Azure. It collects data at cloud scale, detects threats using built-in and custom analytics rules, and automates response via playbooks.
Workspace Architecture
This lesson focuses on Sentinel analytics in a Log Analytics workspace. KQL queries analyze the data ingested there. Key design considerations:
- Choose workspaces based on tenancy, region, data residency, access boundaries, and operations requirements
- Multiple workspaces are used for data sovereignty (keep EU data in EU)
- You can query across workspaces with the workspace() KQL function
Data Connectors
Data connectors ingest logs from sources into the workspace. Types:
- Native connectors: Microsoft Defender XDR, Entra ID, and Azure Activity; each has its own permissions, licensing, and configuration prerequisites
- CEF/Syslog via Azure Monitor Agent: network appliances typically send to a Linux log forwarder with AMA and a data collection rule; Linux sources can also run the agent directly
- API connectors: Third-party services sending logs via REST API
Analytics Rules
Scheduled and NRT analytics rules evaluate KQL and can generate alerts. Incident creation and grouping depend on rule settings and, in the Defender portal, Defender XDR correlation. Other detection types do not all follow the same KQL schedule.
Rule types:
- Scheduled: KQL runs every N minutes/hours on a lookback window
- NRT (Near-Real-Time): Runs every minute using a two-minute built-in ingestion delay: for high-priority detections
- Anomaly: ML-based baselines produce anomalies in the Anomalies table; these are not alerts or incidents by themselves
- Fusion: Correlates low-fidelity signals into high-confidence incidents
Incidents and Alerts
An Alert is a single rule firing. An Incident groups related alerts together. Ticket creation needs an explicit integration or automation. SOAR playbooks use Azure Logic Apps and can run through automation rules when their trigger and permissions match. An incident is an investigation object, not automatically an external ticket.
References
- Sentinel overview and portal timeline
- Sentinel near-real-time rules
- Sentinel anomaly records
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓Sentinel analytics uses Log Analytics: query workspace data with KQL
- ✓CEF/Syslog via AMA needs agent and data collection rules; native connectors have product-specific prerequisites
- ✓Enabling a connector does not guarantee data is flowing: verify via connector health dashboard
- ✓Scheduled rules run on a timer; NRT rules run every minute; Fusion correlates low-fidelity signals into incidents
- ✓Alerts fire from rules; Incidents group related alerts. Playbooks (Logic Apps) attach to incidents via automation rules
1. What is the role of a Data Connector in Microsoft Sentinel?
2. A scheduled or NRT analytics rule in Sentinel matches security events. What can it generate?
3. A Microsoft Sentinel workspace has data from 10 Azure subscriptions. Where must the Log Analytics workspace be located?