Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
I wold like to see this as a functionality as well. I can think several different use cases where we could implement this.
We need this enabled for all Subscription types. Larges Org with an EA should be able to set spending limits on their subscriptions if they would like
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)
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.
This would be useful in our business as well. I would like to have the ability to trigger a runbook or logic app which would disable or stop a service once a budget threshold has been hit, but as an EA customer I don't see the ability to do this.
Thanks for your feedback. Currently, we don’t have any plans for R support in Functions. We will monitor the votes on this request to accordingly inform the priority on our backlog.