What transfers
Your AWS experience already covers this
AWS project structure
→ Microsoft Azure project structure
Start by mapping where application entry points, reusable modules, configuration, and tests live so the new stack feels navigable.
AWS state and data flow
→ Microsoft Azure state and data flow
Compare how data enters the system, how it is transformed, and where side effects belong before translating syntax.
AWS production conventions
→ Microsoft Azure production conventions
Focus on logging, errors, build output, deployment shape, and performance defaults because those decide whether a stack switch works in real teams.
What's new
Where Azure asks you to think differently
Azure is built around subscriptions, resource groups, Entra ID, App Service, Functions, and Azure networking. Expect to spend real time on:
resource groups
managed identity
App Service
Azure Functions
Sample topics
3 of the 17 curated topics on this roadmap
Global Architecture
A multi-region E-Commerce Platform needs to serve customers across North America, Europe, and Asia with low latency and disaster-recovery resilience, requiring resources to be deliberately distributed across multiple geographic locations…
Compute Services
A Banking Application's transaction-processing backend needs flexible compute capacity that can scale with demand. AWS's foundational compute offering is EC2, a broad family of configurable virtual machine instance types. Azure's direct…
Storage Services
A Social Media Platform needs to store millions of user-uploaded images and videos durably and cost-effectively, accessible via simple HTTP requests from anywhere. AWS's S3 is the foundational, industry-defining object storage service.…
14 more topics, in order, with side-by-side AWS and Azure code, are in your roadmap after signup.
Create a free account to see your full roadmapOther switches
Related stack switches
Want the longer concept-by-concept comparison? Read the AWS to Azure overview.