It was a rather easy choice.
Interesting that you say that about AWS when I would pin exactly the same complaints on Azure.
Last time I tried it their console designers clearly had a fetish for "blades" and horizontal scrolling, both of which can get in the bin.
I was initially frustrated by the steps required to set up a VM in AWS, but that's because they always used secure defaults - meanwhile Microsoft just went for the "firewalls are for pussies" approach.
When you graduate to automated deployments, AWS has multiple options to suit different tastes (Cfn or CDK), while Azure had ARM templates which are convoluted enough to make me stick to click-ops.
So really you're weighing up security disaster versus terrible UX.
I'd rather protect users.
If a user creates a resource they have the ability to delete it later, regardless of their permissions. An IT Admin creates a Network/VM/Storage/Whatever and later changes role and has no access to Azure. They can STILL delete that object whenever they want.
MSFT Bug Bounty declared it working as expected and by design. Owner can delete anything they own, regardless of permissions and access.