Every "AWS to Azure to GCP" cheat sheet does the same thing: it gives you a table. S3 equals Blob Storage. EC2 equals Compute Engine. Done, ship it.
Except it's not done. The table tells you where to start, not where you'll get burned.
Where it actually breaks
Take storage. S3 is flat: bucket, then objects. Azure inserts a Storage Account above the container, and that account is where networking rules, access keys, and replication settings actually live. Port an S3-shaped Terraform module over without accounting for that layer, and you'll spend an afternoon figuring out why your access policies don't apply where you expect.
Or take networking. An AWS VPC is regional. A GCP VPC is global by default. "Just create a VPC" means two completely different blast radii depending on which cloud you're standing in.
