Study guide
15.3 Microsoft Sentinel Workspace & KQL Threat Hunting
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.3 Microsoft Sentinel Workspace & KQL Threat Hunting
Key Takeaways Explain This Topic AI
Microsoft Sentinel is a cloud-native SIEM and SOAR solution delivering scalable security telemetry collection, AI analysis, and threat hunting.
Workspace data retention supports three tiers: interactive Analytics logs (30 to 730 days), low-cost Basic logs (8 days), and long-term Archive logs (up to 12 years).
Data collection uses native service connectors, Data Collection Rules (DCR) with Azure Monitor Agent (AMA) for Syslog/CEF forwarders, and threat intelligence feeds.
Kusto Query Language (KQL) processes tabular data streams using piped operators including search, where, summarize, render, join, and let.
Custom detection rules evaluate KQL queries on defined schedules, generating security alerts with mapped entity identifiers for graphical investigation.
Last updated: August 2026
8.3 Microsoft Sentinel Workspace & KQL Threat Hunting
Microsoft Sentinel is a cloud-native Security Information and Event Management (SIEM) and Security Orchestration, Automation, and Response (SOAR) platform. Built natively on Azure Log Analytics, Sentinel eliminates the operational overhead of infrastructure maintenance, scaling compute dynamically to process terabytes of security data per day.
Workspace Architecture & Data Retention Tiers
Sentinel operates on top of an Azure Log Analytics workspace. Architectural decisions regarding workspace design impact security isolation, compliance compliance, and cost.
Single vs. Multi-Workspace Design
Single Workspace Architecture (Recommended Baseline): Centralizes all security log streams into one workspace, providing single-pane-of-glass visibility, simplified query correlation, and unified incident management.
Multi-Workspace Architecture: Deployed when strict data boundary isolation is required by law (e.g., European GDPR data residency restrictions), across distinct legal entities, or in Managed Security Service Provider (MSSP) environments using Azure Lighthouse for delegated access.
Data Retention Tiers
Log Analytics categorizes log tables into three distinct retention tiers to optimize ingestion and storage costs:
Analytics Logs (Interactive Tier):
Standard high-performance storage tier supporting full KQL operator capabilities, analytics rules, and interactive threat hunting.
Retention Window: Default 30 days; configurable up to 730 days (2 years) per table.
Basic Logs:
Designed for high-volume, verbose log streams (e.g., raw NetFlow, IIS logs, or internal network debug logs) required primarily for ad-hoc troubleshooting.
Retention Window: A fixed 30-day query period at a significantly reduced ingestion cost per gigabyte. Total retention can still be extended for long-term compliance, but the interactive query window stays at 30 days and is not configurable.
Query Constraints: Supports basic KQL operators ( where , extend , project ) but does not support complex join operations or scheduled analytics rules.
Archive Logs (Long-Term Retention):
Low-cost storage for historical data compliance requirements after the interactive analytics period expires.
Retention Window: Configurable up to 12 years (4383 days) .
Access Mechanism: Searchable on-demand via Search Jobs (which write matching results to a temporary search table) or by temporarily Restoring the archived data table back into the interactive Analytics tier.
Data Connectors & Ingestion Architecture
Microsoft Sentinel collects security logs across multi-cloud and on-premises environments using dedicated Data Connectors :
Ingestion Mechanisms
Native Service-to-Service Connectors: Direct, agentless API connections for Microsoft services, including Microsoft Entra ID ( SigninLogs , AuditLogs ), Azure Activity, Office 365, Microsoft Defender XDR, and Azure Key Vault.
Data Collection Rules (DCR) & Azure Monitor Agent (AMA): Modern architecture for ingesting OS logs, Linux Syslog, and Common Event Format (CEF) messages. Syslog/CEF logs are forwarded from network appliances (firewalls, routers) to a dedicated Linux Syslog Forwarder virtual machine running the Azure Monitor Agent, which parses and streams logs to Sentinel based on DCR filtering rules.
Threat Intelligence Connectors: Ingests threat indicators (IOCs such as malicious IP addresses, domain names, and file hashes) via TAXII standards (STIX/TAXII) or Threat Intelligence Platform (TIP) APIs.
Custom REST API Connectors: Custom ingestion using the Azure Monitor Data Collector / Log Ingestion API paired with Azure Functions or Logic Apps for custom applications.
Kusto Query Language (KQL) for Security Analysts
Kusto Query Language (KQL) is a read-only request language used to query Log Analytics tables. KQL uses a tabular data pipeline structure where data flows from left to right through pipe operators ( | ).
Core KQL Operators Matrix
Operator Syntax / Example Functional Description SOC Security Use-Case
search search 'unauthorized' Scans all columns or specified tables for a text term Rapid initial threat investigation across unknown log tables
where | where ResultType != 0 Filters rows based on boolean predicates and conditions Isolating failed authentication events or specific IP ranges
summarize | summarize count() by Account, bin(TimeGenerated, 1h) Aggregates data and groups records by dimensions or time windows Detecting brute-force attacks by grouping failed logins per user per hour
render | render timechart Visualizes query results as graphs or charts Rendering login volume spikes or anomaly charts on dashboards
join | join kind=inner (SecurityAlert) on \$left.Host == \$right.Host Merges columns from two tables based on matching key fields Correlating Entra ID sign-in failures with endpoint Defender alerts
let let KnownIPs = dynamic(['10.0.0.1']); Declares named variables, constants, or subqueries Defining whitelist IP arrays or reusable dynamic lookup tables
extend | extend RiskScore = FailureCount * 10 Creates calculated columns or transforms existing fields Calculating custom risk metrics or parsing JSON properties
project | project TimeGenerated, Account, IPAddress Selects specific columns to include in output schema Cleaning query results for export or downstream alert ingestion
Custom Detection Rules & Threat Hunting
Security analysts create Scheduled Analytics Rules by writing custom KQL queries to identify suspicious behaviors. When configuring a custom rule, analysts define:
Query Logic & Lookback: The KQL query and execution frequency (e.g., run every 5 minutes, evaluating data over the past 1 hour).
Alert Threshold: Triggers an alert when results exceed a threshold (e.g., count > 5 ).
Entity Mapping: Maps query output columns to standard Sentinel entity types ( Account , Host , IP Address , URL , FileHash ). Entity mapping is required to enable visual graph investigation and automated playbook responses.