Translation: "We have spending limits, but only for accounts where stopping the spending is important to us. For accounts where the spending is important to you, there cannot be a limit configured. Even though we wrote the code. In fact, we had to add extra code so that we could selectively remove this option."

I like your sense of humor, even if it's sarcastic in this case. :-) However, the main point of my previous comment was to demonstrate that the above-cited statement by OP is false. As for selective - at this time - use of this option in Azure, I have mentioned it, but the big difference is that, should Microsoft decide to allow it for the larger subset of users (perhaps, including pay-as-you-go plans) eventually, the infrastructure is there, unlike in the AWS case (as I understand).