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 Build and deploy a container app 2-3 hours Overview, When to Use Container Apps
DevOps Engineer Standardize deployment pipelines and IaC 3-4 hours Platform Hub, Operations Hub
Architect Define environment, networking, and security boundaries 4-6 hours Platform: Architecture, Networking
SRE / Operator Reduce MTTR on incidents and stabilize scaling 3-5 hours + on-call reference Operations: Monitoring, Troubleshooting 
flowchart TD
    A[Start Here] --> B[Platform Concepts]
    B --> C{Choose your path}
    C --> D[Developer: Language Guides]
    C --> E[DevOps: Operations and IaC]
    C --> F[Architect: Best Practices]
    C --> G[SRE: Troubleshooting and KQL]
    D --> H[Production Readiness]
    E --> H
    F --> H
    G --> H

Developer Path

Build and ship containerized applications on Container Apps. Focuses on runtime, code deployment, and per-language ergonomics.

Time: 2-3 hours

flowchart TD
    A[Overview] --> B[Choose Language Guide]
    B --> C[First Deploy]
    C --> D[Recipes]
    D --> E[Revisions and Traffic]

Read in order:

  1. Overview
  2. When to Use Container Apps
  3. Choose one language guide:
  4. Language Guides Hub — recipes for CI/CD, IaC, and ingress
  5. Platform Hub — focus on revisions and traffic splitting

Outcomes

  • You can deploy a containerized web app to a Container Apps environment.
  • You can push new revisions and split traffic between them.
  • You can read platform logs for your app in Log Analytics.
  • You know where language-specific recipes (CI/CD, IaC, ingress) live.

Microsoft Learn anchors

DevOps Engineer Path

Standardize how teams deploy to Container Apps: IaC, CI/CD pipelines, environments, and rollout patterns.

Time: 3-4 hours

flowchart TD
    A[Platform Basics] --> B[Language Guide IaC Recipes]
    B --> C[CI/CD Pipeline]
    C --> D[Deployment Operations]
    D --> E[Multi-Environment Strategy]

Read in order:

  1. Platform Hub — focus on environments and deployment concepts
  2. Language Guides Hub — Bicep and GitHub Actions recipes for your language
  3. Operations Hub — deployment operations, secret rotation, recovery
  4. Best Practices Hub — revision strategy, blue/green patterns
  5. Reference Hub — CLI reference for automation

Outcomes

  • You can provision a Container Apps environment with Bicep.
  • You can wire a GitHub Actions or Azure Pipelines workflow to build, push, and deploy.
  • You can execute a blue/green or canary rollout with traffic splitting.
  • You can promote a revision from staging to production with rollback ready.

Microsoft Learn anchors

Architect Path

Define platform boundaries, networking topology, identity model, and security posture before code ships.

Time: 4-6 hours

flowchart TD
    A[Architecture Overview] --> B[Environments and Workload Profiles]
    B --> C[Networking Topology]
    C --> D[Identity and Secrets]
    D --> E[Best Practices Baseline]

Read in order:

  1. Platform: Architecture
  2. Platform: Networking — VNet integration, private endpoints, egress
  3. Platform: Security — managed identity, secrets, RBAC
  4. Best Practices Hub — production baseline patterns
  5. Reference Hub — platform limits and quotas

Outcomes

  • You can decide between Consumption and Dedicated workload profiles for a workload.
  • You can design VNet integration and DNS for private ingress and egress.
  • You can define an identity model using managed identities and RBAC.
  • You can document platform limits that constrain your workload design.

Microsoft Learn anchors

SRE / Operator Path

Instrument, alert, and diagnose incidents on Container Apps. Focuses on observability, alert design, and structured troubleshooting.

Time: 3-5 hours + on-call reference

flowchart TD
    A[Monitoring Baseline] --> B[Alert Design]
    B --> C[KQL Query Packs]
    C --> D[Playbooks]
    D --> E[Labs and Post-Incident]

Read in order:

  1. Operations: Monitoring
  2. Operations Hub — alerts, secret rotation, recovery
  3. Troubleshooting Hub — decision tree, first 10 minutes
  4. KQL Query Packs
  5. Troubleshooting Playbooks and Lab Guides

Outcomes

  • You can build a baseline monitoring workbook covering CPU, memory, replica count, and ingress errors.
  • You can design an alert set that catches the top failure modes without page-storming.
  • You can execute the First 10 Minutes runbook on a live incident.
  • You can select the right playbook from a symptom description.

Microsoft Learn anchors

Track Selection Matrix

Situation Start with Then continue to
New engineer onboarding Developer Path DevOps Engineer Path
Designing a new app Architect Path Developer Path
Preparing for launch DevOps Engineer Path SRE / Operator Path
Active incidents SRE / Operator Path Architect Path (hardening)

See Also

Sources