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)G commented
@nick Hard limits are a must. My clients feel like they are at risk of spending nearly infinite money due to attack, misconfiguration, or other circumstances. At the level of an enthusiast, even worrying about a few $100 can be enough to trade Azure for Iaas alternatives that provide pre-paid billing.
Why should Microsoft care if production services get shut down due a configuration setting made by Azure users?G supported this idea ·