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)Anonymous commented
Without a spending cap, the risk of pay-as-you-go is too high. I would prefer to set and adjust some limit, even if it's quite high at times, to suspend operations temporarily in cases of unanticipated (potentially malicious) surges in activity.