# At least one workbook is deployed in every Microsoft Sentinel workspace for visualization and operational reporting

Workbooks are Sentinel's primary visualization surface for SOC operations: they aggregate KQL queries against the workspace into curated dashboards…

Source: https://maester.dev/docs/tests/ZTA.41206

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

## Overview

Workbooks are Sentinel's primary visualization surface for SOC operations: they aggregate KQL queries against the workspace into curated dashboards (Microsoft Entra audit, Azure Activity, Office 365, Microsoft Defender XDR, data-collection health, identity-and-access, threat intelligence, security operations efficiency) so analysts can perform trend analysis, hunt visually, monitor connector health, and brief leadership with consistent metrics. Without workbooks, the SOC has no executive view, no longitudinal trend dashboards, and no visual entry point into the workspace; analysts revert to ad-hoc KQL, which slows investigation and increases the chance that a slow-burn pattern indicating a threat actor in the persistence or collection phase is missed. Workbooks are also the documented vehicle for Microsoft-published health-monitoring dashboards (Data Collection Health, Microsoft Sentinel Cost, Workspace Audit) that surface degradations in detection capability before they become detection gaps. The check confirms at least one workbook is deployed; production deployments typically install the recommended workbook set per the customer's connector inventory.

## Remediation

- [Visualize collected data with Microsoft Sentinel workbooks](https://learn.microsoft.com/azure/sentinel/monitor-your-data)
- [Deploy Microsoft Sentinel content from the content hub](https://learn.microsoft.com/azure/sentinel/sentinel-solutions-deploy)

## Run it

The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:

```powershell
Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-Maester
Invoke-Maester -Pack ZTA -SkipBuiltIn
```

Leave out `-SkipBuiltIn` to run Maester's own checks in the same run.

<details>
<summary>About this check</summary>

| | |
| --- | --- |
| Severity | Low |
| Effort to fix | Low |
| Impact on users | Low |
| Pillar | SecOps |
| Category | Security information and event management |
| Product | [Azure](/docs/tests/products/azure) |
| Feature | Microsoft Sentinel |
| Area | Logging and detection |
| Licence | Consumption-based: Microsoft Sentinel |
| Tenant | Workforce |

Product, feature, area and ATT&CK are Maester's: the assessment does not record them, so Maester keeps them in the pack's `taxonomy.json`.

</details>

<p class="mt-ms-note not-content"><svg class="mt-ms-note__logo" viewBox="0 0 21 21" aria-hidden="true"><rect width="10" height="10" fill="#f25022"/><rect x="11" width="10" height="10" fill="#7fba00"/><rect y="11" width="10" height="10" fill="#00a4ef"/><rect x="11" y="11" width="10" height="10" fill="#ffb900"/></svg><span>A Microsoft check, part of the <a href="/docs/tests/packs/zero-trust-assessment">Zero Trust Assessment</a> pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, <a href="/docs/tests/packs/zero-trust-assessment#licence">MIT licence</a>.</span></p>
