Playbooks¶

Symptom-oriented troubleshooting guides for Azure App Service Linux.

Each playbook follows a hypothesis-driven structure: start from the symptom, list competing hypotheses, collect evidence, validate or disprove, and identify the root cause.

Portal view: Diagnose and solve problems (the symptom-to-playbook entry point)¶

The category cards in this blade map almost 1:1 to the playbook sections below: Availability and Performance maps to Startup/Availability and Performance playbooks, Networking maps to Outbound/Network playbooks, Configuration and Management and Deployment map to Deployment Failures. When a symptom is reported, open this blade first to let Azure surface the most likely detectors, then use this index page to pick the matching playbook for hypothesis-driven validation. Treat detector output as a hypothesis generator (per Detector Map), not a conclusion - every playbook below uses logs + metrics to confirm or refute what the detectors suggest.

graph TD
    A[Reported symptom] --> B{Primary symptom area}
    B --> C[Performance]
    B --> D[Outbound or Network]
    B --> E[Startup or Availability]
    C --> F[Slow response low CPU]
    C --> G[Memory pressure]
    C --> H[Intermittent 5xx]
    C --> I[No space left on device]
    C --> J[Slow start / cold start]
    D --> K[SNAT vs app issue]
    D --> L[DNS resolution VNet]
    D --> M[Private endpoint and DNS routing]
    E --> N[Container HTTP pings]
    E --> O[Warm-up vs health check]
    E --> P[Slot swap warm-up failure]
    E --> Q[Deployment ok but startup fails]
    E --> R[Failed to forward request]
    E --> S[Slot swap config drift]

Performance¶

Core Platform Playbooks¶

Outbound / Network¶

Startup / Availability¶

See Also¶

• Troubleshooting
• First 10 Minutes Checklists
• Hands-on Labs

Sources¶

• Microsoft Learn source 1
• Microsoft Learn source 2
• Microsoft Learn source 3
• Microsoft Learn source 4