Thanks for sharing this perspective.
AWS IAM does have resource condition keys which allow matching resources by account, org, org path, and tag. Resources in a Cloudformation stack would be automatically tagged, for example.
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p...
You now have full permissions to servers, storage and anything else created under that group without me having to enumerate them. If I want to create a new blob store under that group, you already have access without me having to edit iam. I can still make granular permissions where suitable.
Azure makes the path to having all console users require mfa much simpler too.