We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)Rob Al supported this idea ·Rob Al commented
@nick there are some really difficult options here. I would guess that one way is to allow spending limits per resource group as well as overall per subscription. Users can select to implement at either level, and at either level to be a "hard" stop or just a warning. So if i have something that absolutely has to keep running, i'd put it in an RG with a soft limit. if it's some development tool i'd put it in an RG with a hard limit etc.