Skip to content

Learning Paths

Use this page to choose a reading path based on your current architecture expertise, not on your title. 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 tier first

If you fit multiple tiers, pick the one that matches your current gap and complete it before moving up. Trying to jump straight to Advanced without Intermediate patterns produces subjective reviews.

Path selection principle

[Inferred] Teams learn faster when they move from shared platform concepts to workload-specific trade-offs.

[Documented] Microsoft Learn already organizes Azure learning by role and scenario; this guide narrows that into architecture decision paths tiered by expertise.

Choose Your Path

Level Goal Time Budget Start With
Beginner Architect Build a stable architecture mental model on Azure 4-6 hours Overview, Platform Hub
Intermediate Architect Improve trade-off judgment across patterns and operations 6-10 hours Beginner path, then Patterns Hub
Advanced Architect Lead reviews, design labs, and portfolio-wide standards 10-15 hours + ongoing Intermediate path, then Design Labs

Want a hands-on companion?

Follow the Practical Journey for a staged deploy → verify → destroy path that turns the architecture concepts into concrete Azure baselines.

flowchart TD
    A[Start Here] --> B{Choose your tier}
    B --> C[Beginner: Platform and WAF]
    B --> D[Intermediate: Patterns and Ops]
    B --> E[Advanced: Labs and Reviews]
    C --> C1[Platform]
    C1 --> C2[Well-Architected]
    C2 --> C3[One Workload Guide]
    D --> D1[Beginner Path]
    D1 --> D2[Patterns]
    D2 --> D3[Operations]
    E --> E1[Intermediate Path]
    E1 --> E2[Design Labs]
    E2 --> E3[Architecture Reviews]

Beginner Architect Path

Best for readers who know Azure services at a high level but do not yet have a stable architecture mental model.

Time: 4-6 hours

flowchart TD
    A[Overview] --> B[Platform Foundations]
    B --> C[Well-Architected Pillars]
    C --> D[Service Selection Basics]
    D --> E[One Workload Guide]

Read in order:

  1. Overview
  2. Architecture vs Service Guides
  3. Platform sequence:
  4. Well-Architected Framework Hub — read using-waf-in-this-guide.md first
  5. Pick one Workload Guide that matches your current domain

Outcomes

  • You can describe platform boundaries such as subscriptions, identity, and networking without ambiguity.
  • You can pick a service family (compute, data, integration) before locking a product-specific choice.
  • You can map a workload to one Well-Architected pillar tension it exposes.
  • You can read a workload guide and identify which decisions are compliance decisions vs cost decisions.

What to focus on:

  • [Documented] platform boundaries such as subscriptions, identity, and networking
  • [Inferred] service family choices before product-specific detail
  • [Assumed] one workload baseline to connect abstract concepts to a real system

Microsoft Learn anchors

Intermediate Architect Path

Best for readers who already design Azure solutions and now need better trade-off judgment across patterns, data, integration, and operations.

Time: 6-10 hours

flowchart TD
    A[Beginner Path] --> B[Service Selection Patterns]
    B --> C[Decomposition and Integration]
    C --> D[Data and Resilience Patterns]
    D --> E[Operations Ownership]

Read in order:

  1. Complete the Beginner Architect Path first
  2. Patterns Hub
  3. Service Selection Patterns
  4. Pattern deep-dive by concern:
  5. Operations Hub
  6. Reference cheatsheets:

Outcomes

  • You can select a decomposition style (modular monolith, microservices, stamp) with explicit trade-off rationale.
  • You can pick an integration model (sync vs async, saga vs choreography) tied to consistency and cost targets.
  • You can define an operational ownership model as an architecture constraint, not a post-design detail.
  • You can read the Architecture Decision Matrix and defend a specific product choice with 3-5 criteria.

What to focus on:

  • [Inferred] pattern selection for decomposition, messaging, data, and resilience
  • [Inferred] operational ownership as an architecture constraint, not a post-design detail
  • [Observed] common anti-patterns that appear when teams scale without shared guardrails

Microsoft Learn anchors

Advanced Architect Path

Best for principal engineers, review boards, platform owners, and architects supporting multiple delivery teams.

Time: 10-15 hours + ongoing reference

flowchart TD
    A[Intermediate Path] --> B[Design Labs]
    B --> C[Architecture Reviews]
    C --> D[WAF Trade-Offs]
    D --> E[Portfolio Constraints]

Read in order:

  1. Complete the Intermediate Architect Path first
  2. Design Labs Hub
  3. Individual design labs:
  4. Architecture Reviews Hub — expanding in Phase 2
  5. WAF Pillar Trade-offs and Architecture Assessment Checklist
  6. Operations at scale:

Outcomes

  • You can run a design lab, capture evidence tags, and defend the resulting architecture at a review.
  • You can score a workload against WAF pillars with explicit RTO, RPO, cost, and performance targets.
  • You can write and defend an Architecture Decision Record (ADR) using the guide's ADR process.
  • You can identify a portfolio-wide constraint that changes multiple workload architectures at once.

What to focus on:

  • [Inferred] falsification criteria and review prompts, especially after the Phase 2 Architecture Reviews section is published
  • [Inferred] architecture decisions tied to explicit RTO, RPO, cost, and performance targets
  • [Correlated] how platform constraints influence workload outcomes across portfolios

Microsoft Learn anchors

Track Selection Matrix

Situation Start with Why
New cloud adoption program Beginner Architect Establish shared vocabulary and landing-zone thinking first
Existing Azure estate with inconsistent decisions Intermediate Architect Normalize decision criteria and operating model choices
Architecture board or center of excellence Advanced Architect Drive review quality, evidence discipline, and portfolio consistency
Senior developer moving into architecture Beginner, then Intermediate Build platform context before deep pattern comparisons

How to combine with Microsoft Learn

Tip

Use this guide to pick the next question, then use Microsoft Learn to confirm product-specific facts.

  • Read a page here to understand the decision boundary.
  • Open the linked Microsoft Learn article for authoritative platform behavior.
  • Return here to compare trade-offs and ownership implications.

Failure modes when choosing a path

  • [Observed] jumping straight to workload blueprints without platform fundamentals leads to weak identity and governance choices
  • [Observed] learning services one by one without patterns produces fragmented architectures
  • [Inferred] starting with design labs before establishing evidence tags makes reviews subjective

See Also

Sources