Study guide
15.4 Sentinel Incident Management & SOAR Automation
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
15.4 Sentinel Incident Management & SOAR Automation
Key Takeaways Explain This Topic AI
Microsoft Sentinel Incidents correlate related security alerts and mapped entities into actionable investigation cases.
The Investigation Graph visualizes compromised entity relationships, blast radius, and lateral movement timelines across an attack chain.
Analytics rule engines encompass Scheduled KQL rules, Near-Real-Time (NRT) rules, Threat Intelligence matching, and Fusion ML multi-stage correlation.
Automation Rules handle native, synchronous incident triage (owner assignment, tagging, severity updates), while SOAR Playbooks (Azure Logic Apps) orchestrate complex multi-system responses.
Logic App playbooks interact securely with Sentinel and Azure resources using Managed Identities paired with specific Azure RBAC roles.
Last updated: August 2026
8.4 Sentinel Incident Management & SOAR Automation
When security anomalies are identified by threat detection engines, Microsoft Sentinel aggregates related alerts into central investigation cases known as Incidents . Sentinel provides native Security Orchestration, Automation, and Response (SOAR) capabilities to streamline incident triage, reduce resolution SLAs, and execute automated response playbooks.
Sentinel Incident Triage & Investigation Graph
An Incident in Microsoft Sentinel represents a correlated grouping of one or more security alerts that together indicate a potential cyber attack. Triage operations take place within the Incident Management interface.
Incident Properties & Lifecycle
Status: New (unassigned/untriaged), Active (under active investigation), or Closed (resolved).
Severity: High, Medium, Low, or Informational.
Owner: Assigned SOC analyst or automated triage group.
Tactics & Techniques: Mapped MITRE ATT&CK categories.
Entities: Mapped identifiers (Users, Hostnames, IP Addresses, File Hashes, Azure Resources) involved in the attack chain.
The Investigation Graph
The Investigation Graph provides a visual, node-based interactive canvas that allows security analysts to examine an incident's full blast radius and lateral movement:
Entity Node Connections: Displays central entity nodes (e.g., a targeted user account) connected to related alert nodes, IP addresses, and hostnames.
Timeline Exploration: Allows analysts to scrub back and forth through time to trace the exact chronological sequence of events across compromised endpoints and identity services.
Entity Insight Sidebars: Generates real-time contextual telemetry for selected entity nodes (e.g., recent failed sign-ins, privilege escalations, or geographic location anomalies for a targeted account).
Expanding Related Entities: Enables analysts to expand node connections to discover whether an entity is implicated in other concurrent incidents across the enterprise.
Sentinel Analytics Rules Deep Dive
Sentinel correlates incoming log streams using five distinct Analytics Rule engines:
Scheduled Analytics Rules: Custom or built-in KQL queries that execute on a defined schedule (e.g., every 10 minutes looking back 30 minutes). Features custom alerting thresholds, suppression windows, and entity mappings.
Near-Real-Time (NRT) Rules: Evaluates KQL query conditions with ultra-low latency (evaluating log ingestion within 1 minute intervals) to detect critical threat indicators instantly.
Fusion ML Engine: A pre-configured machine learning engine that automatically evaluates low-fidelity signals and alerts across disparate telemetry sources (Microsoft Defender XDR, Entra ID Protection, Azure Activity) to synthesize high-fidelity multi-stage attack incidents without requiring KQL writing.
Threat Intelligence Rules: Matches ingested STIX/TAXII threat indicators (malicious IPs, domains, hashes) directly against streaming event logs (DNS, Web Proxy, Firewall logs) in real time.
Microsoft Security Rules: Automatically creates Sentinel incidents directly from native security alerts generated by Microsoft Defender products (Defender for Cloud, Defender for Endpoint, Defender for Identity).
Automation Rules vs. SOAR Playbooks
Sentinel provides two complementary mechanisms for response automation:
- Feature / Attribute Automation Rules SOAR Playbooks (Azure Logic Apps)
- Underlying Technology Native Sentinel portal control engine Azure Logic Apps workflow engine
- Execution Latency Synchronous, immediate execution upon trigger Asynchronous workflow execution
- Primary Purpose Basic incident triage & governance Complex, multi-system orchestration & response
Supported Actions Assign owner, change status, add tags, modify severity, invoke playbook External API calls, IP blocking, Teams/Slack notifications, user session revocation, VM isolation
Triggering Scenarios Triggered on Incident Creation or Alert Creation Triggered by Automation Rules, manual analyst click, or alert/incident triggers
External Connectors Restricted to native Sentinel incident properties 400+ turnkey Azure Logic App connectors (VirusTotal, ServiceNow, Teams, Entra ID)
Triggering Playbooks: Alert vs. Incident Triggers
SOAR Playbooks leverage dedicated Microsoft Sentinel Logic App connectors:
Alert Trigger (Microsoft Sentinel Alert): Executes when an individual security alert is generated. Useful for localized enrichment or immediate resource-level responses before incident correlation occurs.
Incident Trigger (Microsoft Sentinel Incident): Executes when an overall Incident is created or updated. Passes the entire array of correlated alerts and mapped entities into the Logic App, allowing holistic automation across all attack vectors simultaneously.
Managed Identity Permissions for Playbooks
For security playbooks to modify Sentinel incidents or execute remediation tasks against Azure resources, they must authenticate securely.
Authentication Best Practices
Managed Identity (Recommended): Playbooks use System-Assigned or User-Assigned Managed Identities rather than static credentials, API keys, or OAuth user tokens.
Required Azure RBAC Roles:
Microsoft Sentinel Automation Contributor: Grants Sentinel permission to execute the Logic App playbook on behalf of automation rules.
Microsoft Sentinel Contributor / Responder: Granted to the Logic App's Managed Identity so it can update incident statuses, assign tags, or post comments to Sentinel.
Target Workload Roles: Specific roles required for active remediation (e.g., Virtual Machine Contributor to isolate network interfaces, or Entra ID User Administrator roles to revoke compromised user sessions).
Incident Assignment & SLA Management
Effective Security Operations Center (SOC) management relies on structured incident response workflows:
SLA Tracking: Automation rules assign incoming incidents to specific analyst queues based on severity and source, establishing operational response targets.
Incident Closure Taxonomy: When closing an incident, analysts must select a mandatory Closure Reason :
True Positive – Suspicious Activity: Confirmed security incident requiring remediation.
False Positive – Incorrect Alert Logic: Alert logic was flawed or overly sensitive.
Benign Positive – Suspicious but Expected: Authorized activity (e.g., scheduled penetration test).
Audit Comments: Detailed closure comments are required to train Fusion ML models and maintain audit trails for regulatory compliance.