Azure spending limit pr. Resource Group instead of pr. subscription.
I see a great potential for Azure if it was possible to control spending limit pr. ressource group.
In companies with many departments/developers or students at universities have need for develop environments in Azure. My aim is to reduce the risk of letting someone spin up 1000 VMs etc. and leaving them running for months before someone finds out.
Introducing spending limits / isolating cost for a resource group to each department/developer would be great.
Each developer could then be given control to his/hers own resource group.
This is definitely on our list!
In the meantime, please create a budget which will trigger a script (e.g. Automation, Functions, or Logic Apps) via action groups to shutdown or delete resources based on your specific needs.
Users can now set budgets at Subscriptions and Resource Group scopes in cost management. We also have APis that are available to do the same. Enterprise customer can also set budgets for their commercial scopes like Enrollment, Departments and Accounts.
https://aka.ms/costmgmt/videos (there is a video on creating budgets)
Justin Lazar commented
Definitely on the list and it's been more than an year. Are there any update?
John Barnard commented
What a sad predatory practice Microsoft engages in here. People have been asking this for years and the technology clearly already exists because the free trials have cost limits.
Phil Tomlinson commented
I would like to indicate that I support this feature.
It would be very helpful for us.
It is a real concern for our business and our customers that we have effectively unlimited liabilities with cloud computing. A control which lets us limit the liability for any one project would make cloud use more appealing.
Richard Davies commented
It would be great if one could specify a cost limit on a resource group (or even on a resource) basis and then have an alarm triggered when burn rate exceeds a certain percentage of that cost. Alarm could then send notifications to relevant individuals in the organisation.
Hari K Prasad commented
if you can provide resources Group wise cost spending limit that will help to manages sources cost.
Kristian Berggren commented
There would be great potential in this feature in companies with developers having spending limits on resource groups compared to the current alternative.
Right now the only way to achieve a spending limit is to put a spending limit on the subscription.
However this would imply creating a subscription for each developer.
This suggestion sounds way better and would simplify both management and billing.