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)Anup Mistry commented
This feature exists in MSDN/Microsoft partner dev accounts and also Azure Trial Credits. Maybe do two levels of caps. Like two limits, one to halt service and second allows to bring service online, so VMs don't get entirely lost/de-allocated. Example: Halt service spending at $100 and keep $25 to allow snoozed service.Anup Mistry commented
Would like to go live and set spending limit max at $200 to avoid any surprises at end of month. In the portal billing section provide a way to set a custom max limit. If for whatever reason max is reached that deallocate resources and disable just like how it does for the MSDN subscriptions.Anup Mistry supported this idea ·