A team that knows Azure opens the AWS console and finds hundreds of services with names like Route 53, Fargate and Athena. Searching for the Azure name finds nothing. Worse, a few names do exist in both clouds and mean different things, so people assume they know how something works and get caught.
Microsoft keeps the full list in Azure for AWS professionals, and it reads just as well in the other direction. Bookmark it. The tables below cover what an Azure team reaches for first, and where the match is misleading.
This is where the two clouds differ most, and where a wrong assumption costs the most.
| Azure | AWS | Watch out |
|---|---|---|
| Entra tenant | Organization and its management account | The management account is a real account that can hold resources. Keep it empty |
| Management group | Organizational unit (OU) | |
| Subscription | Account | An account is a harder wall. Each one has its own IAM and its own root user. See Do you use separate AWS accounts as security boundaries? |
| Resource group | Nothing | AWS Resource Groups are saved searches over tags. Deleting one deletes no resources |
| Azure Policy deny | Service control policy | SCPs only block. AWS Config does the compliance reporting |
| Entra ID sign-in | IAM Identity Center | Usually fed from Entra ID, so people keep one login |
| Managed identity | IAM role | |
| Azure RBAC role | IAM policy | In AWS a role is an identity you assume, not a set of permissions. The permissions are in the policy attached to it |
| Activity log | CloudTrail | |
| Defender for Cloud | Security Hub CSPM and GuardDuty | |
| Key Vault | KMS for keys, Secrets Manager for secrets, Certificate Manager for certificates | |
| Cost Management | Cost Explorer and AWS Budgets | |
| Bicep | CloudFormation or CDK |
| Azure | AWS |
|---|---|
| Virtual Machines | EC2 |
| App Service | Elastic Beanstalk, or ECS Express Mode for containers |
| Functions | Lambda |
| Container Apps | ECS on Fargate |
| AKS | EKS |
| Blob Storage | S3 |
| Azure SQL Database | RDS or Aurora |
| Cosmos DB | DynamoDB |
| Service Bus | SQS and SNS |
| Event Grid | EventBridge |
| API Management | API Gateway |
| Front Door | CloudFront |
| Azure DNS and Traffic Manager | Route 53 |
| Azure Monitor and Application Insights | CloudWatch and X-Ray |
| ExpressRoute | Direct Connect |
| Private Link | PrivateLink |
| Microsoft Foundry | Amazon Bedrock |
Treat each row as a place to start reading. Two services in the same row rarely have the same limits, pricing or features, so choose by what the workload needs. See Do you know how to choose Azure services?
There is no resource group. In Azure you delete a resource group and everything in it is gone. AWS has no container like that below the account. Use tags to say what belongs together, and deploy each application as one stack, because deleting a CloudFormation stack deletes its resources.
A Northwind developer puts a test app in an AWS resource group and deletes the group when the test ends. The instances keep running and keep billing.
❌ Figure: Bad example - Bad example - An AWS resource group is a view, so deleting it removes nothing
The test app is one CloudFormation stack tagged project=poc-search. Deleting the stack deletes every resource in it.
✅ Figure: Good example - Good example - The stack is the unit you create and delete
The console shows one Region at a time. Most AWS resources belong to a Region, and the console lists only the Region you have selected. A server in another Region is easy to forget. See Do you monitor traffic and cull unused AWS resources?
A subnet lives in one Availability Zone. An Azure subnet spans every zone in its region. In AWS you create one subnet per zone to get the same resilience.