The biggest difference IMO is in how they're handled by large organizations and how prod permissions are provisioned by them. In Azure you have one user account and one org, with subscriptions for your user account to activate to get permissions. You can have multiple subscriptions but they're under the same login/user account and you can have multiple active at the same time. In AWS, you get access to an account or accounts that have different logins, so you get to juggle those with login/logout, even if there's SSO. In GCP, there are multiple projects, under a single login, but you may have to juggle projects.
The other aspect is how regions are dealt with. AWS global resource index/search thing is useful, but it totally feels like I spend more time juggling regions with AWS. Azure's regions themselves are, let's just say, interesting. GCP is better at it than AWS, and less interesting than Azure (which is a good thing).
The biggest difference IMO is in how they're handled by large organizations and how prod permissions are provisioned by them. In Azure you have one user account and one org, with subscriptions for your user account to activate to get permissions. You can have multiple subscriptions but they're under the same login/user account and you can have multiple active at the same time. In AWS, you get access to an account or accounts that have different logins, so you get to juggle those with login/logout, even if there's SSO. In GCP, there are multiple projects, under a single login, but you may have to juggle projects.
The other aspect is how regions are dealt with. AWS global resource index/search thing is useful, but it totally feels like I spend more time juggling regions with AWS. Azure's regions themselves are, let's just say, interesting. GCP is better at it than AWS, and less interesting than Azure (which is a good thing).