Lab Guides¶

Troubleshooting labs are reproducible experiments that turn a storage symptom into a testable hypothesis, a controlled reproduction, and a falsifiable fix. This hub introduces the Troubleshooting > Lab Guides surface and tracks both published labs and scoped follow-on scenarios.

The lab lifecycle every guide in this hub follows:

mermaid flowchart LR A["Pick a storage failure to reproduce"] --> B["Trigger the fault in a lab subscription"] B --> C["Capture evidence: metrics, diagnostics, portal state"] C --> D["Diagnose against the matching playbook"] D --> E["Fix and verify recovery"] E --> F["Record the evidence chain in the lab guide"]

How to Use This Hub¶

• Start with a symptom-first playbook when you need immediate guidance for a live incident.
• Use a lab guide when you want a controlled environment that reproduces the same failure pattern end to end.
• Expect each future lab to follow the series lab contract: background, hypothesis, runbook, experiment log, evidence, clean-up, and linked playbook context.

Planned Troubleshooting Labs¶

Starter Shape for the First Lab¶

The first lab guide now documents the canonical troubleshooting-lab structure for the private-endpoint DNS substrate. Use it as the reference shape for future storage troubleshooting labs:

1. Lab metadata for difficulty, duration, and scope.
2. 1) Background, 2) Hypothesis, 3) Runbook, and 4) Experiment Log sections.
3. Evidence sections that capture verification queries and portal or CLI proof.
4. Clean-up guidance plus a cross-link back to the supporting playbook.

See Also¶

• Troubleshooting Home
• Playbooks
• Private Endpoint and DNS Issues
• First 10 Minutes: Access

Sources¶

• Troubleshoot Azure Storage
• Storage account overview