Scenario Router¶

Use this page when you have a specific architectural situation and want to jump straight to the page that answers it. This is a breadth-first index across four lifecycle phases — Plan (design), Deploy (build), Operate, and Troubleshoot (review) — that complements the depth-first Learning Paths. Unlike a service guide, this repository treats troubleshooting as design review that feeds back into planning, which is why the lifecycle below is circular rather than linear.

How to Use This Router¶

• Pick the table for the lifecycle phase you're in — Plan (design), Deploy (build), Operate, or Troubleshoot (review).
• Scan the left column for the situation that matches yours; open the destination on the right.
• If two rows fit, prefer the row from the phase you're actually in — the same architectural concept often appears in more than one phase.
• If your situation spans two phases (a design choice today that will surface in a review later), check Cross-Phase Scenarios first.
• Every destination is a real page in this guide, not an external link and not an aspirational page.
• Rows are intentionally short. Follow the link for the depth; this table is a switchboard, not a summary.
• If your situation is missing, open an issue — the router is meant to grow.

Lifecycle Overview¶

flowchart TD
    A[Plan] --> B[Deploy]
    B --> C[Operate]
    C --> D[Troubleshoot]
    D --> A

I'm Planning¶

I'm Deploying¶

I'm Operating in Production¶

I'm Troubleshooting¶

In architecture work, "troubleshooting" means reviewing an existing design — auditing a running architecture against reliability, cost, security, and operational-excellence expectations rather than debugging a single incident. Feed findings from this phase back into Planning. If you need service-specific incident response, open the matching service guide's Troubleshooting hub.

Cross-Phase Scenarios¶

Some situations straddle two phases — the design decision you make today determines the review finding you'll face months later. These rows link the two together so you can see the pattern and the review lens in one place.

When This Router Isn't the Right Entry Point¶

• You're brand new to Azure architecture → start with Learning Paths instead.
• You're evaluating whether the architecture guide applies or you should read a service-specific guide → use Architecture vs Service Guides.
• You need service-specific incident troubleshooting (a running Container Apps incident, an AKS pod failure) → open the matching service guide's Troubleshooting hub; this guide covers architectural review, not incident response.

See Also¶

• Learning Paths — depth-first, role-based reading order
• Overview — what this guide is and who it's for
• Repository Map — full section map
• Architecture vs Service Guides — when to use this guide versus a service guide
• Platform Hub — Azure architecture building blocks
• WAF Hub — Well-Architected Framework pillars
• Patterns Hub — reusable architecture patterns
• Workload Guides Hub — workload-specific baselines
• Architecture Reviews Hub — review methodology

Sources¶

• https://learn.microsoft.com/en-us/azure/architecture/
• https://learn.microsoft.com/en-us/azure/well-architected/