Study guide
7.4 Workbooks for Visual Review
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.4 Workbooks for Visual Review
Key Takeaways Explain This Topic AI
Workbooks are Sentinel's interactive visualization and dashboard layer, built on Azure Monitor Workbooks.
They turn ingested data into charts, grids, maps, and tiles for monitoring, reporting, and investigation.
Dozens of built-in workbook templates ship with connectors; workbooks can also be customized with KQL.
Workbooks visualize data — they do not detect threats (analytics rules) or automate response (playbooks).
The visualization noun alone is not the cue; the subject must be security operations data for it to be Sentinel.
Last updated: June 2026
Workbooks Visualize Security Data
Workbooks are Microsoft Sentinel's interactive visualization and dashboard layer. They are built on Azure Monitor Workbooks , so the same engine that charts Azure telemetry powers Sentinel's security dashboards. A workbook turns ingested data into charts, tables, grids, time series, maps, and tiles that a SOC uses for monitoring, reporting, and investigation .
Workbooks come after data is connected. With no signals in the Log Analytics workspace, there is little to visualize. Once data is flowing, a workbook can show sign-in trends, incident volumes over time, top alerting rules, or geographic maps of suspicious traffic. That makes workbooks supportive — they help humans see and understand the environment — rather than the detection engine itself.
Sentinel ships with dozens of built-in workbook templates , and many connectors install a workbook tuned to their data source. Workbooks are also customizable: because they run KQL queries under the hood, an analyst can adjust or build visualizations, though SC-900 does not require you to do so.
- Sentinel feature Verb it answers Output
- Workbook Visualize / report / monitor Charts, dashboards, grids
- Analytics rule Detect Alerts and incidents
- Hunting Proactively search Query results to triage
- Playbook / automation rule Respond Automated actions
Do not equate a workbook with an incident . An incident is the case you investigate when something needs attention; a workbook is a view that helps you understand activity and trends. They support the same SOC process but answer different prompt verbs.
The Dashboard Trap and Product Matching
The most common workbook trap is the word dashboard or report . Many Microsoft products show dashboards: Purview Compliance Manager shows a compliance score dashboard, Defender for Cloud shows Secure Score, and Microsoft Entra shows identity dashboards. The noun alone is not the cue — the subject matter is. If the prompt is about visualizing security operations data already in Sentinel , the answer is a workbook . If it is about a compliance posture score , it is Purview Compliance Manager . If it is about a cloud security posture score across Azure resources , it is Defender for Cloud Secure Score .
Use these workbook cues with confidence:
Dashboard or visual view of security operations data -> workbook.
Trends, charts, or reporting over connected Sentinel data -> workbook.
Present security activity to support an investigation -> workbook.
Create the detection logic itself -> analytics rule, not workbook.
Take an automated action -> playbook/automation rule, not workbook.
A useful distinction: a workbook reflects what the data shows; it does not decide that something is a threat (that is an analytics rule) and it does not act on a threat (that is a playbook). Keeping those three apart — see, detect, respond — lets you answer almost any Sentinel feature question.
For SC-900 you will not build a workbook or write its KQL. Know that workbooks are part of Microsoft Sentinel, they provide interactive dashboards and visualizations over ingested security data , they are built on Azure Monitor Workbooks, and they differ from analytics rules, hunting, incidents, and Logic Apps playbooks. When a scenario asks to visualize or report on security data, choose workbooks.
What Workbooks Show and How They Compare to Other Dashboards
A Sentinel workbook can combine many visualization elements on one canvas: time charts of incident or alert volume, bar and pie charts of top categories, grids of recent events, geographic maps of source IP addresses, and single-value tiles for key metrics such as open high-severity incidents. Because workbooks are built on Azure Monitor Workbooks , they support parameters, drill-downs, and tabs, so a single workbook can serve both an executive summary view and a deep analyst view.
Microsoft and connector solutions ship template workbooks for common sources — Microsoft Entra sign-ins, Microsoft 365, Azure activity, and many third-party firewalls — that a team can use immediately or clone and customize.
It is worth contrasting Sentinel workbooks with the other posture dashboards SC-900 covers, because the exam likes to test whether you can keep them straight by their subject , not their visual format:
- Dashboard Product What it summarizes
- Workbook Microsoft Sentinel Security operations data: incidents, alerts, signals
- Secure Score Microsoft Defender for Cloud Cloud security posture across Azure/hybrid resources
- Compliance score Microsoft Purview Compliance Manager Progress against regulatory and standards controls
- Identity dashboards Microsoft Entra Sign-in, risk, and access governance views
Notice that all four are visual, yet only the workbook is about security operations telemetry inside Sentinel . If a prompt says "track our posture against ISO 27001," that is a compliance score in Purview; if it says "see our resource security recommendations and a percentage score," that is Secure Score in Defender for Cloud; only a request to visualize Sentinel's ingested security data or incident trends is a workbook.
For SC-900, remember three things about workbooks: they are the visualization layer of Sentinel, they are built on Azure Monitor Workbooks and ship as customizable templates, and they reflect data rather than detect threats or respond to them. Pair that with the see-detect-respond split — workbooks see, analytics rules detect, playbooks respond — and workbook questions become straightforward product-and-feature matches.