3 ms·

> There's no reasonable way to implement this. Oh, really? Azure wants to have a word with you ... Yes, currently they don't enable this for subscriptions with

by ablekh 6y ago

> There's no reasonable way to implement this. Oh, really? Azure wants to have a word with you ... Yes, currently they don't enable this for subscriptions with commitment plans or with pay-as-you-go pricing, but it is not because it is not possible or feasible, as you argue - the technical infrastructure in the form of spending limits, spending budgets and quotas is there [1-3] and is available for select plans [4]. [1] https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/spending-limit https://docs.microsoft.com/en-us/azure/cost-management-billi... [2] https://docs.microsoft.com/en-us/partner-center/set-an-azure-spending-budget-for-your-customers https://docs.microsoft.com/en-us/partner-center/set-an-azure... [3] https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits https://docs.microsoft.com/en-us/azure/azure-resource-manage... [4] https://azure.microsoft.com/en-us/support/legal/offer-details https://azure.microsoft.com/en-us/support/legal/offer-detail...

jiggawatts 6y ago
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."
- ablekh 6y ago
  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).

by ablekh 6y ago

jiggawatts 6y ago

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."

ablekh 6y ago
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).