That's why you have people like me who straddle back and forth between the two cloud behemoths, and the services can become hard to keep track of.
It's relatively easy when you're dealing with the building block services like EC2 Instances in AWS and Virtual Machines in Azure, but it gets a little confusing when you're looking at more advanced services, like the service equivalent to AWS CodeCommit (Spoiler: it's Azure DevOps).
This information is handy too when you're preparing for a certification exam. Fundamental-level certifications like Azure Fundamentals (AZ-900) and AWS Certified Cloud Practitioner (CLF-C01) covers a very broad range of services, and it's very likely that you will find yourself “translating” between AWS and Azure.
One important thing to note is that mapping each service 1:1 might not be possible, but feature parity might be achieved by a combination of services.
Using the exam objectives of the AWS Certified Cloud Practitioner exam, here's a cheat sheet to lay out the mapping:
|Elastic Compute Cloud (EC2)||Virtual Machine (VM)|
|Auto-scaling||VM Scale Sets|
|Elastic Container Services||Container Instances|
|Elastic Block Storage||Storage Account|
|S3 Glacier||Archive storage|
|Elastic File System||Files|
|Cost Explorer||Cost Management|
This list is not exhaustive by any means, but I think it's a good starting point to help you with the high-level AWS-Azure mapping. Also, if I got anything wrong, I welcome your feedback!