Skip to content

Learning Paths

Use this page to choose a reading path based on your role and goal. Each path is numbered, so read the pages in order for the best result. Every path ends with a checklist of concrete outcomes you should be able to demonstrate.

Pick one primary path first

If you fit multiple roles, pick the one that matches your current goal, complete that path, then read a second path opportunistically. Trying to follow every path in parallel dilutes progress.

Choose Your Path

Role Goal Time Budget Start With
Developer Ship a web app on App Service with a chosen stack 2-3 hours Overview, Platform Hub
Operator Run App Service in production with scale, recovery, and guardrails 3-5 hours Platform Hub, Operations Hub
Troubleshooter Diagnose startup, 5xx, and networking failures fast 2-4 hours + on-call reference Troubleshooting Hub 
flowchart TD
    A[Start Here] --> B[Platform Concepts]
    B --> C{Choose your path}
    C --> D[Developer: Ship a Stack]
    C --> E[Operator: Production Baseline]
    C --> F[Troubleshooter: Fast Diagnosis]
    D --> G[Production Readiness]
    E --> G
    F --> G

Developer Path

Build and ship a web app on App Service for a chosen runtime. Focuses on hosting choice, per-language ergonomics, and deployment pipelines.

Time: 2-3 hours

flowchart TD
    A[Overview] --> B[Hosting Models]
    B --> C[Choose Language Guide]
    C --> D[Production Baseline]
    D --> E[Deployment Automation]

Read in order:

  1. Overview
  2. Platform: How App Service Works
  3. Platform: Hosting Models
  4. Choose one language guide:
  5. Best Practices: Production Baseline
  6. Operations: Deployment — pick zip-deploy, container-deploy, or GitHub Actions

Outcomes

  • You can deploy a web app in your chosen stack to App Service with the right hosting model.
  • You can wire a CI/CD pipeline that promotes through a deployment slot.
  • You can read platform logs and diagnostics for your app.
  • You know where per-language recipes and runtime notes live.

Microsoft Learn anchors

Operator Path

Run App Service in production: capacity planning, deployment slots, security posture, and day-2 operations across a portfolio of apps.

Time: 3-5 hours

flowchart TD
    A[Platform Deep-Dive] --> B[Best Practices]
    B --> C[Operations: Scaling and Health]
    C --> D[Operations: Security and Slots]
    D --> E[Troubleshooting Methodology]

Read in order:

  1. Overview
  2. Platform deep-dive sequence:
  3. Best Practices sequence:
  4. Operations sequence:
  5. Troubleshooting Methodology

Outcomes

  • You can pick a Service Plan tier and scale-out policy that matches a workload profile.
  • You can run a slot swap safely and roll back if health degrades.
  • You can validate outbound networking and identity configuration for a production app.
  • You can define an alert set for the top App Service failure modes.

Microsoft Learn anchors

Troubleshooter Path

Diagnose fast during a live incident. Focuses on symptom-to-playbook mapping, evidence collection, and reproducible labs.

Time: 2-4 hours + on-call reference

flowchart TD
    A[Architecture Overview] --> B[Decision Tree]
    B --> C[First 10 Minutes]
    C --> D[Playbooks]
    D --> E[KQL Query Packs]
    E --> F[Labs]

Read in order:

  1. Troubleshooting Hub
  2. Architecture Overview and Mental Model
  3. Decision Tree and Quick Diagnosis Cards
  4. First 10 Minutes runbooks:
  5. Playbooks Hub — startup, deployment, performance, authentication, mTLS, SSL, and more
  6. KQL Query Packs
  7. Lab Guides — reproduce and validate failure modes

Outcomes

  • You can run the First 10 Minutes runbook for a common App Service symptom.
  • You can select the right playbook from a symptom description without guessing.
  • You can write a KQL query that isolates a failure window and its top offenders.
  • You can reproduce a lab scenario, apply the fix, and validate falsification evidence.

Microsoft Learn anchors

Track Selection Matrix

Situation Start with Then continue to
New engineer onboarding Developer Path Operator Path
Migrating an existing app to App Service Developer Path Operator Path
Preparing for launch Operator Path Troubleshooter Path
Active incident Troubleshooter Path Operator Path (hardening)

Live incident? Skip the path.

If you are actively responding to a page, jump straight to Troubleshooting Hub, the Decision Tree, and the First 10 Minutes runbooks.

See Also

Sources