Immersive Labs · Microsoft Azure

Microsoft Sentinel SOAR

Demonstrate Your Skills — Capstone Lab

10 June 2026 Workspace: sentinel63763db8 Region: UK South Status: ✓ Completed

Built a fully automated threat-response pipeline in Microsoft Azure — from suspicious blob download detection through IP risk scoring to autonomous storage key rotation — with zero manual analyst intervention required.

02

Automation Pipeline

// SOAR chain — incident creation to automated remediation
🔍
Blob Download Detected
⚠️
Incident Created (Low)
⚡
Automation Rule Fires
🔗
IP Risk Check Playbook
🌐
Third-Party API Call
🔴
Severity → High
🔑
Key Rotation Triggered
01

Scenario & Objectives

Metrolio reported that an Azure Storage Account access key had been leaked externally. Core services were hardcoded to use the key, so the organisation was reluctant to rotate it without confirmed evidence of active exploitation. A scheduled analytics rule was monitoring for suspicious blob download activity.

The task was to build a SOAR pipeline that could automatically assess the risk of the originating IP, escalate incident severity if confirmed high-risk, and autonomously rotate the compromised key — with no manual steps required.

Environment
Platform
Immersive Labs
Cloud
Microsoft Azure
Workspace
sentinel63763db8
Resource Group
sentinel
Region
UK South
Lab Type
Capstone
03

What I Built

Playbook: determine-severity-based-on-ip

A Logic App with an incident trigger, built from scratch in the Logic App Designer. The playbook implements the following workflow:

01
Entities — Get IPs
Extracts all IP address entities from the triggering Sentinel incident using the Microsoft Sentinel connector. Connection set to azuresentinel-determine-severity-based-on-ip.
02
For Each Loop
Iterates over every IP returned. Output referenced via expression: body('Entities_-_Get_IPs')?['IPs'] — entered manually through the Expression editor.
03
HTTP POST — IP Risk API
POSTs each IP to the third-party risk scoring endpoint with Content-Type: application/json. The current item from the For Each loop is passed as the request body.
04
Parse JSON
Parses the API response using a defined schema to surface the Risk string field as typed dynamic content for downstream use.
05
Condition → Update Incident
If Risk == "High", the Update Incident action sets the incident severity to High using the Incident ARM ID from the trigger. False branch left empty.
HTTP Action Configuration
FieldValue
MethodPOST
URIhttps://ipcheckerd6b781a5.azurewebsites.net/api/ipchecker
HeaderContent-Type: application/json
BodyCurrent item (dynamic — For Each loop)
Parse JSON Schema
{ "type": "object", "properties": { "Risk": { "type": "string" } } }
Automation Rule 1: auto-update-incident-severity
FieldConfiguration
TriggerWhen incident is created
ConditionAnalytics rule name Contains Blob Download with SDK via an Access Key
ActionRun playbook: determine-severity-based-on-ip
Automation Rule 2: emergency-rotate-key
FieldConfiguration
TriggerWhen incident is updated
Condition 1Analytics rule name Contains Blob Download with SDK via an Access Key
Condition 2Severity Changed to High
ActionRun playbook: storage-account-access-key-rotate
Managed Identity & RBAC

The Logic App required a system-assigned managed identity with the Microsoft Sentinel Contributor role assigned at the resource group scope. This enables the playbook to update Sentinel incidents programmatically without hardcoded credentials.

04

Issues & Resolutions

Body/IPs not surfaced in dynamic content panel
Logic App Designer doesn't always expose nested properties in the UI picker
Used Expression editor: body('Entities_-_Get_IPs')?['IPs']
Playbook run failed — 0 successful, 1 failed
Managed identity lacked permission to update Sentinel incidents
Assigned Microsoft Sentinel Contributor role to Logic App identity at RG scope
Microsoft Sentinel Responder role unavailable in lab tenant
Restricted role availability in the Immersive Labs Azure tenant
Used Microsoft Sentinel Contributor as functional equivalent
emergency-rotate-key: state change condition error
Incident update trigger requires at least one state change condition
Added Severity Changed to High as required state change condition
05

Results

🏅
Lab Completed — Badge Awarded
All tasks validated by Immersive Labs. The full SOAR chain executed automatically: incident created → IP checked → severity escalated → key rotated.
Incident Entities Identified
🖥️
134.175.229.59
IP · IPv4 Internet · HIGH RISK
👤
metrolio9f6be6
Account · Storage Identity
📄
architecture.png
File · Blob accessed
📄
invoice.pdf
File · Blob accessed
06

Key Learnings

Microsoft Sentinel Azure Logic Apps SOAR Automation Managed Identity Azure RBAC REST API Integration Incident Response KQL
💡
Automation rules are the entry point, not the logic
Rules evaluate conditions and trigger playbooks but contain no orchestration logic themselves. The real power lives in the Logic App workflow.
💡
Chaining rules enables multi-stage response
Using "incident created" and "incident updated" triggers in separate rules allows clean separation of detection, analysis, and remediation phases.
💡
The Expression editor is essential knowledge
The Logic App dynamic content picker doesn't always surface nested properties. Knowing body('Step_Name')?['Property'] syntax is critical for real-world playbook builds.
💡
Managed identity is the right credential model
System-assigned managed identities eliminate hardcoded credentials from playbooks. Role assignments must be scoped correctly — resource group level for Sentinel-specific roles.