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)
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!
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".
Jason Milczek commented
Almost 3.5 years and nothing?!?! Is this backlog in Bill Gates' basement?
This exists for MSDN subscriptions so you have the technology. Why is this not be implemented?
Michael de Selincourt commented
The above update is 3 years old... what's the best supported way to prevent unexpected costs on Azure PAYG?
Rama Indrawan commented
I know for sure that the BUDGET which gives us ability to send emails at certain thresholds are here, I am using it now from the Portal
Luke Maslany commented
It has been almost three years - did this ever make it onto the road-map?
When will this feature arrive? as it stands the upper limit is still unlimited.
Craig Humphrey commented
+1 for Enterprise Agreement based Azure Subscriptions.
And for some way to track/alert cost against a specific user.
E.g. user creates huge VM and leaves it turned on, racking up a huge bill.
Malon Körber commented
"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."
Why not EA Customers? I don't want to build a specific department and an account for each subscription. I need to configure the spending limit on the specific subscription.
I don't need a hard quota, I am even happy with a softquota on subscription level!
When doing this for Pay-As-You-Go, why not for EA-Customers?
Hello? Year after year I send my customers to other solutions...