Spending Limit or Maximum Cost CAP for Azure
As a customer, I really care about Spending Limit or Spending CAP feature of Azure.
How does Azure prevent some evil attack to my Azure sites causing charge a large billing of Credit Card?
For example, it should automatically shut off or temporary disable my site when a certain dollar amount has been reached.
Is this feature in the RoadMap of Azure?
Or is there anyway to control my maximum Spending Limit of Azure?
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)
Too scared of being attacked and go bankrupt
Jason Milczek commented
Seriously, why is this still incomplete???
Well, found the alerts menu (at least alerts if not hard limits) but for Pay-as-you-go it's not enabled to set an alert... well Microsoft doesn't care for the smaller customers :( , and it's ok, the only thing we can do is use another cloud, luckily there are plenty: AWS, GCE, Softlayer, Rackspace, and what not....
Hi, does it exist now? (2017 =) ) I didn't find any billing alarm or limit options in menu...
Martin Bérubé commented
This is a real problem for small businesses and individuals. Until this is fixed, I'll have to go for another hosting company.
Jon Reade commented
It's THE main reason I won't use or recommend Azure.
Please address this, it's a basic business issue that's losing you potential customers.
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.
Craig Main commented
come on - this is pathetic, you planned the most voted feature on the entire platform two years ago? No feedback added since then... with four times the votes of the most asked for general features?
I just converted my free trial to a pay-as-you-go subscription and tried to set a spending limit so that I don't get robbed by unexpected traffic, only to find out that this feature is not available for this subscription type. I don't quite understand why it's possible for certain subscriptions, but not for pay-as-you-go. Sounds like there are political motives at work, not technical ones.
I'll be looking elsewhere.
This is insane. So Microsoft has just decided that they can bankrupt their customers for the malicious actions of others? Wow. Azure just lost all credibility. I can't go bankrupt just because they refuse to implement this obviously necessary feature.
Hrvoje Kusulja commented
I am also interested in opt-in for CSP Azure subscription spending limit. To have hard / financial limit . After reaching the limit to automatically guarantee azure subscription is suspended / no further costs for end-customer should be generated.
Johan Eliasson commented
Peter, you can be notified. Opt-in for Email Alerts on your Account page.
Uaaa, I have subscribed to the service recently and was almost shocked that such a basic feature is not available out of the box! Or at least an option to send a notification when some amount is reached. Probably will switch to some other vendor then.
Over 4 years and still not implemented. Google and AWS have spending limits. Microsoft implement other "features" such as graphs and "better styling" but not one of the most requested features ever that has actual merits.
I would really want to have this feature as well. I don't see a problem when this is an opt-in feature and this cap is not enabled by default?
It's the user that gets to decide whether or not to activate this and he must accept the consequences of his decision. At least he will not be ruined when something goes wrong.
@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?
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.
Please look at the number of upvotes and the number of comments. I think it's now pretty obvious that it is a must-have feature. I am not even sure if I understand why you are still hesitating 4 years after this was suggested. I mean what is the reason?
I met so many clients who are not willing to implement Azure because it's pretty much an "open wallet". They are simple too scared of being attacked and go bankrupt (and to be frank, I understand them)
Can you please confirm that you are reading these comments in 2016 and please confirm that you are working on this feature? Can you please at least give us an approximate timeframe when it will be ready?
In response to Mike's concerns about the many workflows that would not respond well to sudden unexpected termination: I propose segmenting workflows that can be halted, or that are more prone to being attacked, into a separate billing plan with a hard spending limit. Put the non-uninterruptible things in a billing plan without a limit. It should be up to the client to decide when the cost of having a process rudely interrupted is going to be less than the cost of continuing to have it run beyond billing expectations / allocation.
Maybe some of us will get it wrong, and get burned. Then we will learn the hard way what not to interrupt, but at least the costs of recovering from that situation should be something manageable. It's too late to plan after the money has already been spent.
Hard spending limits are an absolute must. As an example I have a client who is a registered charity and thus very kindly receive $5000 of Azure a year for free. Sadly they've told me not to use this for them due to no spending limit and thus are still paying for hosting elsewhere.
The cost of a website or service being taken offline can indeed be costly, but the current alternative could destroy a small business or charity.