How do Workbooks differ from Azure Dashboards?

Azure Dashboards are simple pinboard-style layouts where you pin individual tiles from metrics, logs, and other Azure blades. Workbooks offer a richer authoring experience with parameterized queries, conditional logic, interactive drill-down, Markdown text blocks, and group layouts. Workbooks support cross-resource queries, template sharing via ARM templates, and version-controlled JSON definitions. Use Dashboards for quick at-a-glance monitoring with pinned widgets. Use Workbooks for interactive reports, runbook-style troubleshooting guides, and detailed analysis that require query parameterization and interactivity.

What parameter types are available in Workbooks?

Workbooks support several parameter types: Text (free-form input), Drop down (static or query-driven options), Subscription picker, Resource Group picker, Resource picker, Time Range, Interval, and Multi-value. Parameters can cascade — one parameter's value can filter the options in another. Query-based parameters run a KQL or ARG query and present the results as selectable options. All parameters can be referenced in subsequent queries using {paramName} syntax. This enables building highly interactive, reusable templates that adapt to the selected scope.

Azure Workbook Template Builder

MonitoringAzure

Build Azure Monitor Workbook templates with parameters, charts, and KQL queries.

Last verified: May 2026

Azure Monitor Workbooks Configuration

Build Azure Monitor Workbook template configs with parameters, metrics, queries, and visualizations.

Required Fields

nameresourceGroupdisplayNamesourceIdserializedData.items

{
  "name": "workbook-infra-overview",
  "resourceGroup": "rg-monitoring",
  "location": "eastus2",
  "displayName": "Infrastructure Health Overview",
  "description": "Comprehensive view of VM, AKS, and storage health with cost trends",
  "category": "workbook",
  "sourceId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-monitoring/providers/Microsoft.OperationalInsights/workspaces/law-central-prod",
  "serializedData": {
    "version": "Notebook/1.0",
    "items": [
      {
        "type": "parameter",
        "name": "parameters",
        "parameters": [
          {
            "name": "TimeRange",
            "type": "timerange",
            "defaultValue": "P1D",
            "label": "Time Range"
          },
          {
            "name": "Subscription",
            "type": "subscription",
            "multiSelect": true,
            "label": "Subscription"
          },
          {
            "name": "ResourceGroup",
            "type": "resourcegroup",
            "dependsOn": "Subscription",
            "multiSelect": true,
            "label": "Resource Group"
          }
        ]
      },
      {
        "type": "metric",
        "name": "vmCpuMetric",
        "title": "VM CPU Utilization",
        "resourceType": "Microsoft.Compute/virtualMachines",
        "metrics": [
          {
            "namespace": "Microsoft.Compute/virtualMachines",
            "metric": "Percentage CPU",
            "aggregation": "Average"
          }
        ],
        "visualization": "timechart",
        "gridSettings": {
          "width": "50%"
        }
      },
      {
        "type": "query",
        "name": "failedDeployments",
        "title": "Failed Deployments (Last 24h)",
        "query": "AzureActivity | where TimeGenerated {TimeRange} | where OperationNameValue endswith 'write' | where ActivityStatusValue == 'Failed' | summarize FailedCount = count() by ResourceGroup, ResourceProviderValue, OperationNameValue | sort by FailedCount desc | take 25",
        "visualization": "table",
        "gridSettings": {
          "width": "50%"
        }
      },
      {
        "type": "query",
        "name": "aksNodeHealth",
        "title": "AKS Node Status",
        "query": "KubeNodeInventory | where TimeGenerated > ago(1h) | summarize arg_max(TimeGenerated, *) by Computer, ClusterName | project Computer, ClusterName, Status, KubeletVersion, KubeProxyVersion, OperatingSystem | sort by ClusterName, Computer",
        "visualization": "table",
        "gridSettings": {
          "width": "100%"
        }
      },
      {
        "type": "query",
        "name": "storageCapacity",
        "title": "Storage Account Capacity Trend",
        "query": "StorageBlobCapacity | where TimeGenerated {TimeRange} | summarize AvgCapacityGB = avg(Capacity / 1073741824.0) by bin(TimeGenerated, 1h), AccountName | render timechart",
        "visualization": "timechart",
        "gridSettings": {
          "width": "100%"
        }
      }
    ],
    "styleSettings": {
      "paddingStyle": "narrow",
      "spacingStyle": "narrow"
    }
  },
  "tags": {
    "hidden-title": "Infrastructure Health Overview",
    "environment": "production"
  }
}

Generated Output

Output will appear here...

See It in Action

Your operations team needs a unified troubleshooting workbook for production incidents. The builder generates a multi-tab Workbook: Tab 1 'Health Overview' shows resource health + key metrics; Tab 2 'Recent Errors' lists exceptions from Application Insights with conditional drill-down to specific request traces; Tab 3 'Cost Anomalies' highlights resources with unusual cost spikes. Subscription + time-range parameters cascade through all tabs. Used during incidents, the workbook reduces 'where do I look first' confusion — investigators have a single guided view that adapts to their selected scope.

What This Tool Does

Azure Monitor Workbooks provide a flexible canvas for creating rich interactive reports and dashboards that combine text, KQL queries, metrics, and parameters into a single shareable view. Workbook templates define reusable layouts with parameterized queries, chart visualizations (time charts, bar charts, grids, maps), conditional visibility, and dynamic content. Unlike simple dashboards, Workbooks support interactive elements — clicking a row in one grid can filter another visualization. The Workbook Template Builder helps you construct template JSON with parameters, query steps, and chart configurations for common monitoring scenarios.

Technical Details

The builder generates Azure Monitor Workbook JSON template definitions with: parameters (text, dropdown, subscription/RG/resource picker, time range), query steps (KQL queries with parameter substitution, multiple visualization types), text steps (Markdown), group steps (collapsible sections, conditional visibility), and links to other Workbooks/dashboards. Output is the Workbook ARM template ready for `az resource create` or for sharing via the Azure portal's gallery.

Common Use Cases

1Building workbook templates with subscription and resource group parameters that dynamically filter all downstream queries
2Creating multi-tab workbooks that combine resource health, performance metrics, and cost analysis in a single view
3Designing interactive troubleshooting guides with conditional steps that appear based on query results

Common Questions

How do Workbooks differ from Azure Dashboards?: Azure Dashboards are simple pinboard-style layouts where you pin individual tiles from metrics, logs, and other Azure blades. Workbooks offer a richer authoring experience with parameterized queries, conditional logic, interactive drill-down, Markdown text blocks, and group layouts. Workbooks support cross-resource queries, template sharing via ARM templates, and version-controlled JSON definitions. Use Dashboards for quick at-a-glance monitoring with pinned widgets. Use Workbooks for interactive reports, runbook-style troubleshooting guides, and detailed analysis that require query parameterization and interactivity.
What parameter types are available in Workbooks?: Workbooks support several parameter types: Text (free-form input), Drop down (static or query-driven options), Subscription picker, Resource Group picker, Resource picker, Time Range, Interval, and Multi-value. Parameters can cascade — one parameter's value can filter the options in another. Query-based parameters run a KQL or ARG query and present the results as selectable options. All parameters can be referenced in subsequent queries using {paramName} syntax. This enables building highly interactive, reusable templates that adapt to the selected scope.

Expert Tips

TIP

Cascading parameters are the killer Workbook feature. A 'Subscription' parameter populates 'Resource Group' options based on the selected subscription, which populates 'Resource' options based on the RG. Building this in dashboards is impossible; in Workbooks it's a few clicks.

TIP

Save Workbooks as ARM templates AND check them into git. The visual editor is great for authoring but git tracks the JSON definition for diff/review. PRs that modify Workbooks become reviewable changes instead of opaque 'I clicked some stuff in the portal' updates.

TIP

Conditional steps (visible only when a query returns results) are perfect for runbook-style workbooks. 'If error rate > 1%, show this troubleshooting section'. The viewer doesn't see noise during normal operation but gets contextual guidance when something's wrong.

Related Learning Guides

Azure Monitor & Application Insights26 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.