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)
Brandon McCaig commented
This is a vital feature. I cannot risk having my credit card charged a stupid amount due to my account getting hacked, or a bug or accidental misuse or something like that. I'm new to Azure. I don't know what I'm doing. It's likely I'll accidentally enable something expensive that I cannot afford. Nothing I'm doing with this account will be production. It's all development, testing, learning... Seriously, it's absolutely unacceptable that Microsoft does not support this feature for pay-as-you-go accounts. I was considering closing my account on another provider to use Azure instead since I'm typically a .NET developer, but NOT unless I can set a spending limit to protect myself and my family.
Totatlly aggree with the former commentors. I would like to use Azure privatly, but I'm affraid of creating a huge bill. I'm using Azure now for 2 Years at work and I'm really happy with it. But there, billing is not a big issue and we have insurance and a big team to take care in case of such cost explosions. In that scenario I can totally understand that you have to remove the cost limit as of high available services (We even had to increase the core limit in one case). But in private I really dont care about high availability. If the service is down, I can take care of it if needed.
This is a really drawback for me, as it would make me even better with Azure and I can go for new Ideas in my free time. And this limit would be the safty net I would need, as I (or noone) as a private person can be react to a spending alarm all the time!
And actually, there is already a limit in place that shuts down services: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/billing/billing-spending-limit.md
Why not, as a multi international company with thousands of developers, change this to make it available inside PAYG subscriptions...
Come on Microsoft, I want to set a limit on my PAYG subscription!!
I want to sleep easy know that even if I've done something stupid I wont wake up for a £10k credit card bill.
Please give us an update on when this will be available. Setting up cloud infrastructure is complex and estimating costs is difficult. The ability to set a cap is a vital tool to manage risk of something unexpected or malicious causing a devastating bill.
They have now something call "Alerts" but that will not cut it for me. It may be too late when I get the notification.
I will not use Azure until this feature is implemented. Will look at AWS in the mean time.
What a disappointment this feature has not been enabled yet. Four year after the update. Really makes it impossible for developers learning azure (and who will then punt Azure at their work places) as well as small to medium size business from using azure. Seems very short sighted to me, especially when the reply from Azure Billing Team has recognized the need.
I just created an account and have no needed to cancel it again.
Is there a timeline for this? Can you enable spending limits on Dev/Test subscriptions and/or EA subscriptions? Right now I do not see a way to disable resources such as the various Cognitive Services APIs. We would really like to have this feature so we can ensure our application teams don't overspend.
bui xuan hung commented
I really want to use Azure but I can't give you unlimited access to my bank account.
You're forcing people to go elsewhere, this can not make business sense.
Microsoft should also be embarrassed by how long this has been "Planned".
Ditto; this is the only thing stopping me using Azure.
Such a simple feature, approaching 7 years since it was raised and 4 since it was "Planned".
Do Microsoft read these at all?
Missing this feature is really the only thing stopping me from using Azure right now.
Man, what a huge development cycle you guys have there.
I wonder if you even look at this forums. Lots of people complaining about this missing feature, stating that they drop their subscriptions (or don't even consider to use the service in production) because this feature does not exist.
It's ridiculous this is still not implemented.
Why not for EA Customers!!??
Why 4 Years almost nothing happend and why just pay as you go customers!!??
Koen Janssens commented
Crazy that this feature is still not available after 4 years!
A lack of spending limits is preventing me from exploring Azure since my trial is expired. One month isn't enough time to learn much and I can't take the risk of authorizing unlimited spending on a pay-as-you-go subscription to continue learning. There's too much of a risk that I'll make a mistake and be responsible for costs that I can't afford.
I'm disappointed today because I found an awesome blog post with an ARM template that had me excited about trying out Azure Functions, but I'm not willing to add an unlimited spending subscription to my account to try out something that I expect to cost less than $1.
Please give an update on this. It's been 3 years and spending limits have been enabled for several other subscription types. Is this still planned?
Any updates? Without this feature, there is too much downside risk to using Azure. One misclick could cost 1000’s of dollars.
Is there any update on this for EA and CSP? We had a customer run up a $12k bill the other day that could have been easily avoided!