Skip to content

Troubleshooting¶

Hypothesis-driven troubleshooting for Azure Virtual Machines: classify the symptom, collect the right evidence, then move into a canonical playbook.

How this section works¶

graph TD
    A[Incident detected] --> B[Use quick diagnosis cards or decision tree]
    B --> C[Run first-10-minutes checklist]
    C --> D[Open canonical playbook]
    D --> E[Validate or disprove hypotheses]
    E --> F[Mitigate and prevent recurrence]

Start Here¶

Need	Go To
Understand VM failure domains first	Architecture Overview
Route a symptom to the right playbook	Decision Tree
Know what evidence to collect	Evidence Map
Build a troubleshooting mindset	Mental Model
Triage in under 60 seconds	Quick Diagnosis Cards
Work the first incident minutes	First 10 Minutes
Jump straight to deep-dive guides	Playbooks

Troubleshooting Domains¶

Connectivity¶

Performance¶

Boot and Disk Recovery¶

Quick Routing View¶

graph TD
    A[Observed symptom] --> B{Primary impact}
    B -->|Cannot connect| C[Connectivity]
    B -->|Slow or saturated| D[Performance]
    B -->|Won't boot or recover| E[Boot and disk]
    C --> C1[First 10 Minutes: Connectivity]
    D --> D1[First 10 Minutes: Performance]
    E --> E1[First 10 Minutes: Boot]

See Also¶

Sources¶