Study guide

7.5 Hunting, KQL Awareness, and Notebooks

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.5 Hunting, KQL Awareness, and Notebooks

Key Takeaways Explain This Topic AI

Hunting is proactive, hypothesis-driven searching for threats that no analytics rule has detected yet.

Sentinel ships hunting queries mapped to the MITRE ATT&CK framework's tactics and techniques.

Kusto Query Language (KQL) is the read-only query language behind analytics rules, hunting, and workbooks.

Bookmarks preserve interesting hunting findings; livestream watches for activity in near real time.

Jupyter notebooks extend hunting with advanced analysis, ML, and external data via the Sentinel API.

Last updated: June 2026

Hunting Is Proactive Threat Searching

Hunting is Microsoft Sentinel's proactive, hypothesis-driven search for threats that analytics rules have not flagged. Instead of waiting for an alert, an analyst forms a hypothesis ("could an attacker be using this technique?") and runs queries across the ingested data to look for weak signals, unusual behavior, or evidence of compromise. It is the opposite operating mode from automated detection: analytics rules wait and fire; hunting goes looking.

Sentinel ships with built-in hunting queries that are mapped to the MITRE ATT&CK framework — the industry knowledge base of adversary tactics (the why , e.g., Persistence, Lateral Movement) and techniques (the how ). This mapping lets a SOC hunt systematically across the attack lifecycle and spot coverage gaps. When a prompt mentions MITRE ATT&CK tactics/techniques in a Sentinel context, hunting is the associated feature.

Several hunting tools support the workflow:

  • Tool Role in hunting
  • Hunting queries Prebuilt and custom KQL searches, many mapped to MITRE ATT&CK
  • Bookmarks Save interesting query results to revisit, share, or promote to an incident
  • Livestream Run a query continuously to watch for matching activity in near real time
  • Notebooks Jupyter notebooks for advanced, programmatic investigation

The payoff of a successful hunt is often a new analytics rule : once an analyst confirms a meaningful pattern by hunting, they can codify it as a scheduled rule so future occurrences are detected automatically. That hunt-to-rule loop is a clean way to remember how hunting and detection relate.

KQL and Notebooks at the Fundamentals Level

Kusto Query Language (KQL) is the read-only query language used throughout Sentinel and Azure Monitor. Analytics rules, hunting queries, and workbooks all express their logic in KQL. SC-900 calls for KQL awareness , not authoring: recognize that KQL is how you search and filter ingested security data , and that it is the common language tying detection, hunting, and visualization together. You will not need to know operators or syntax.

Notebooks in Sentinel are Jupyter notebooks that extend investigation beyond what the portal UI offers. They combine live code, queries, and narrative text, and they can pull Sentinel data through its API , bring in external/threat-intelligence data , and apply machine learning or custom visualizations. Notebooks suit deeper, repeatable, or data-science-style hunts. For a fundamentals question, notebooks should make you think advanced investigation and analysis , sitting next to hunting in your mental model.

Use these scenario cues:

Proactively search for undetected threats -> hunting .

Map searches to adversary tactics and techniques -> hunting with MITRE ATT&CK .

Query and filter ingested security data -> KQL .

Advanced or programmatic investigation with external data and ML -> notebooks .

Automatically detect a known pattern -> analytics rule (not hunting).

  • Concept Mode SC-900 expectation
  • Hunting Proactive, manual Know its purpose and the MITRE ATT&CK link
  • KQL Query language Recognize it; no syntax required
  • Notebook Advanced analysis Match to deep investigation support
  • Analytics rule Automated detection Keep distinct from hunting

This is a topic where overstudying wastes time. SC-900 is a fundamentals exam, so the skill is recognizing the vocabulary: hunting is proactive, KQL is the query language, notebooks add advanced analysis, and all three live inside Microsoft Sentinel's SIEM/SOAR story. Avoid sending a labels, retention, or access-review prompt here — those belong to Purview and Entra.

Why Proactive Hunting Matters and How MITRE ATT&CK Organizes It

Automated detection can only catch what someone has already taught it to recognize. Threat hunting exists to find the rest — novel techniques, slow and low activity, and attacker behavior that stays under the threshold of any single analytics rule. A hunter starts from a hypothesis grounded in adversary tradecraft, for example, "if an attacker had compromised an account, I would expect to see unusual remote service creation," and then runs queries to confirm or rule it out. The mindset is investigative and iterative rather than reactive, which is exactly why SC-900 contrasts it with rule-based detection.

The MITRE ATT&CK framework gives this work structure. It catalogs how real adversaries operate across tactics — the attacker's tactical goals such as Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Lateral Movement, and Exfiltration — and the specific techniques used to achieve each one. Sentinel tags its built-in hunting queries (and many analytics rules) with the ATT&CK tactics and techniques they relate to.

This lets a SOC view its detection and hunting coverage across the attack lifecycle , spot stages where it is blind, and prioritize new hunts and rules to close those gaps.

  • MITRE ATT&CK term Meaning Example
  • Tactic The attacker's goal at a stage Lateral Movement
  • Technique How the goal is achieved Use of remote services
  • Coverage mapping Which tactics/techniques you can detect or hunt Finds blind spots

When a hunt confirms a real pattern, the analyst typically promotes a bookmark to an incident for investigation and converts the successful query into a scheduled analytics rule so the behavior is detected automatically next time. That hunt-to-rule loop, plus livestream for watching emerging activity and notebooks for deep analysis, is the complete picture. For SC-900, hold onto the essentials: hunting is proactive and hypothesis-driven, it is organized by MITRE ATT&CK, it uses KQL, and notebooks extend it — recognizing these roles is all the exam requires.