AWS ↔ Azure map and how to talk about it
Quick reference
| AWS | Azure |
|---|---|
| Organizations / OUs / SCPs | Management groups / Azure Policy (deny) |
| Account | Subscription (+ resource groups inside) |
| IAM users/roles, IAM Identity Center | Entra ID users/groups, service principals, managed identities; Azure RBAC |
| Instance profile / IRSA / Pod Identity | Managed identity / AKS workload identity |
| VPC / subnets (per AZ) | VNet / subnets (zone-spanning) |
| Security groups + NACLs | NSGs (+ ASGs) |
| Transit Gateway | Hub-and-spoke peering / Virtual WAN |
| Direct Connect / Site-to-Site VPN | ExpressRoute / VPN Gateway |
| PrivateLink / interface endpoints | Private Endpoint (Private Link) + Private DNS zones |
| Route 53 (zones / routing) | Azure DNS / Traffic Manager |
| NLB / ALB / CloudFront+GA | Load Balancer / Application Gateway / Front Door |
| EC2 / ASG | VMs / VM Scale Sets |
| Lambda / Fargate / App Runner | Functions / Container Apps, ACI / App Service |
| EKS / ECR | AKS / ACR |
| S3 (tiers) / EBS / EFS | Blob Storage (Hot/Cool/Cold/Archive) / Managed Disks / Azure Files |
| RDS / DynamoDB / ElastiCache | Azure SQL, PostgreSQL Flexible / Cosmos DB / Cache for Redis |
| SQS/SNS/Kinesis | Service Bus / Event Grid / Event Hubs |
| Secrets Manager + KMS | Key Vault |
| CloudWatch / X-Ray | Azure Monitor + Log Analytics / Application Insights |
| CloudFormation / CDK | ARM templates / Bicep |
| CodePipeline/CodeBuild | Azure DevOps Pipelines (or GitHub Actions) |
| GuardDuty / Security Hub | Defender for Cloud / Sentinel |
| Cost Explorer / Budgets | Cost Management + Billing |
| Control Tower | Azure Landing Zones |
Talking about Azure in interviews
- "You're AWS-strong — how fast could you work on Azure?" — "The concepts map closely: VNets to VPCs, AKS to EKS, managed identities and workload identity to instance profiles and IRSA, Azure Policy to SCPs and Config. My Kubernetes, Flux and Terraform skills carry over — only the providers and resource names change. I'd spend the first couple of weeks on identity and networking specifics — Entra, RBAC scopes, NSGs, private endpoints — and build an AKS + Terraform lab."
- On the résumé: list Azure only as "familiar / hands-on lab", with honest context — never imply production experience you don't have.
- "Azure is good to have" in a JD: learn the fundamentals in this lesson, do one small AKS + Terraform lab (cluster with workload identity reading a Key Vault secret, deployed via Flux), and talk about transferable skills.
Interview questions and model answers
"What's a resource group, and how does it differ from an AWS account?" — A resource group is a lifecycle and permission container inside a subscription; you deploy, manage, tag and delete its resources together. The subscription is the closer analogue of an AWS account — the billing, quota and access boundary — and resource groups add a finer layer AWS doesn't have natively.
"Contributor vs Owner?" — Both can manage resources; only Owner (or User Access Administrator) can assign roles to others. Reader is view-only.
"How do pods in AKS access Key Vault without secrets?" — AKS workload identity: enable the OIDC issuer, create a user-assigned managed identity with a Key Vault data role, add a federated credential trusting the cluster issuer and the service account, annotate the service account with the client ID — then the SDK or the Secrets Store CSI driver exchanges the projected token for an Entra token.
"How do you prevent accidental deletion of production resources in Azure?" — Resource locks (CanNotDelete) on critical resource groups and resources, least-privilege RBAC with PIM for elevation, Azure Policy guardrails, and changes through IaC pipelines.
"Design hub-and-spoke networking in Azure." — A hub VNet with Azure Firewall, VPN/ExpressRoute gateways, DNS Private Resolver and shared services; spoke VNets per workload peered to the hub with gateway transit; UDRs sending spoke egress and cross-spoke traffic through the firewall; private endpoints with private DNS zones linked centrally; NSGs on subnets — or Virtual WAN for large estates.