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)Michiel van Otegem commented
It is far too easy to make a configuration mistake that leads to huge costs. For instance, selecting instance size in VS2010 is a dropdown and selecting an Extra Large instance instead of Extra small instance is very easy. There is no warning. This should harder and more intuitive (e.g. a slider with color coding, green for low cost red for high cost). Also, you should be able to set a quota. One so you get a warning when you exceed certain costs, one to undeploy automatically if you exceed certain costs.
We are likely to support this in phases. Stay tuned for more details.Michiel van Otegem commented
This IMHO is an extremely important feature. There are companies that really only use their apps during office hours, and would like to shut it down outside those hours. An even better example is batch processes that run only once a day. I've worked on an app like that for a bank, and that only needed to run when the stock exchange was open. If you really want to make Azure interesting for these kinds of customers, make it possible to set a schedule during which instances are operational.