Guided Azure Runbooks

What Azure task are you trying to do safely?

Search for the thing you need to investigate, review, change, or recover. Each runbook starts with read-only discovery, explains what output means, and shows when to stop before a risky change.

Popular starter runbooks JavaScript is loading the full library. These starter links work immediately. Check current subscription Review RBAC assignments Inspect private endpoints Find public exposure Check cost and budgets
1Describe the job

Search for the operational task, not the perfect Azure product name.

2Open the safest match

Cards show risk, time, service area, and whether the path starts read-only.

3Run discovery first

Read-only checks come before change, delete, scale, failover, or assignment commands.

4Read, decide, escalate

Output patterns, evidence, and stop conditions tell you what to do next.

Runbook library

Matched runbooks

safe-first guides matched. The library now uses the full page width so every card has room to explain the task before you open the detailed command path.

Choose a runbook to open.

Start with search or a common job, then open the full safe-first command path only when you are ready.

Why these runbooks are different

Simple first layer. Full operational depth when you open a task.

The library stays task-first, but the runbooks still include expected inputs, safe discovery commands, output interpretation, stop conditions, evidence checkpoints, Resource Graph queries, related Azure terms, and command-group links.

runbooks
mapped commands
safe-first commands
discovery commands
Resource Graph examples
output pattern checks