-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request - Implement Budgets - Subscriptions/Management Group #741
Comments
Hey @awood86, have you seen this policy that can help you do this https://www.azadvertizer.net/azpolicyadvertizer/Deploy-Budget.html |
Also i think this is something we'd probably move from a deployment angle to the Subscription Vending modules, would you agree? |
I hadn't! But that's certainly a worthwhile policy to implement, thanks for sharing.
Yeah would agree on that too, especially as the core platform subscriptions would be covered under the above mentioned policy |
Thanks @jtracey93, feel free to move this issue to the Subscription Vending modules if needed. |
Will link to Azure/bicep-lz-vending#4 and close this one |
Describe the feature end to end, including deployment scenario details under which the feature would occur.
Budgets on all subscriptions and management groups
Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?
Quite an important feature for most businesses moving their workloads into the cloud, so budget alerting would be great to increase awareness and ensuring that budgets are aligned
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Can you describe any alternatives that you have taken since this feature does not exist?
When deploying landing zones, I have an additional pipeline/biceps that apply budgets
Feature Implementation
Haven't created a branch but can certainly share
Check previous GitHub issues
Code of Conduct
The text was updated successfully, but these errors were encountered: