Azure uses a unified resource manager that has everything in "one place".

AWS uses a "federation of systems" with almost nothing in common, except for authentication.

Azure's approach is more consistent and makes things like resource graph relatively easy to implement.

AWS's approach is more robust against failure, because the various service offerings are more independent and have fewer common failure points.

This isn't just theory, it matches my experience pretty well. I hate how in AWS I have to switch portals to go from service-to-service, whereas in Azure the "Resource Groups" contain all related resources in one place, even if it's a random mix of IaaS and PaaS. Conversely, I've been bitten by several wide-spread Azure outages. Repeatedly.

It all depends on your business requirements. For me, the consistency is more important. For other people, availability is far more critical.