Optional extras
Azure for AWS engineers
Azure appears as "good to have" in many Bangalore DevOps postings, especially at GCCs of European and US enterprises that run Microsoft-heavy estates. You don't need production depth to pass — you need to map Azure concepts onto your AWS knowledge accurately, speak the vocabulary correctly (resource groups, Entra ID, managed identities, VNets, NSGs, AKS), and show you could be productive quickly. This optional topic is a complete orientation written for an AWS engineer, with the AKS and Terraform details interviewers ask about.
After this topic you can
- Map AWS knowledge to Azure equivalents
- Explain Azure identity, networking and AKS basics
- Answer Azure questions honestly without overstating experience
Lessons
-
1Azure fundamentals and the resource hierarchy
- The hierarchy
- Regions and availability
-
2Identity and access
- Microsoft Entra ID
- Azure RBAC
- Entra/RBAC vs AWS IAM in one paragraph
-
3Governance and cost
- Azure Policy
- Resource locks
- Landing zones
- Cost management
-
4Networking
- Virtual networks and filtering
- Connectivity
- Load balancing family
-
5Compute, storage and data services
- Compute
- Storage
- Databases and others
-
6AKS in depth
- Cluster basics
- Networking models
- Identity: workload identity
- Secrets, registry, ingress, scaling, monitoring
- Resilience
-
7Infrastructure as code and pipelines
- ARM templates and Bicep
- Terraform on Azure
- Azure DevOps Pipelines
-
8Monitoring and security
- Azure Monitor and Log Analytics
- Security services
-
9AWS ↔ Azure map and how to talk about it
- Quick reference
- Talking about Azure in interviews
- Interview questions and model answers