University of Bern
Dokumentationen
  1. Dokumentationen
  2. Cloud
  3. Azure
  4. First Steps
  5. Budget

Dokumentationen

Budget

Danger

A budget in Azure does not represent a hard limit. This means that the costs of a subscription can exceed the budget. Whether automatic actions are triggered upon exceeding the budget depends on its configuration (see the chapter Automation).

Default Budget for a Subscription

Note

The role Unibe-Subscription-Owner (mg-unibe) is required to change the budget.

When creating a Subscription, a default budget of 200 CHF is defined. This should be adjusted to individual needs.

  1. The budget is located in the navigation menu of the Subscription under Cost Management and Budgets.
  2. The budget named default is selected.
  3. Edit budget is selected in the top menu bar.
  4. Under Budget Amount, an amount can be defined at which the alert starts. The desired amount is entered and confirmed with Next.
  5. Under Alert conditions, custom conditions can be added for when an alert should occur.
  6. Under Alert recipients (email), additional email addresses can be added that should be notified when the alert is triggered.
  7. The changes are saved with Save.

Control Mechanisms

The IT Services of the University of Bern have also defined a budget per Subscription. This has a limit of 1000 CHF and notifies the Cloud Team. The team analyzes the costs for the respective Subscription and notifies the owners of the Subscription if necessary.

Setting Budgets for Individual Resources

In the above example, a budget was defined for a Subscription and adjusted to individual needs. However, a budget can not only be defined for a Subscription. It is also possible to define a budget for Resource Groups. A corresponding guide can be found in the Budget Tutorial.

Automation

In the cases discussed, a budget was mainly created to notify individuals if it was or will be exceeded. However, a budget can also be created that automatically executes individual actions. The budget itself is only the trigger; the actual automation can be implemented in various ways:

  • A Runbook in an Automation Account can be executed. A guide on how a Virtual Machine can be automatically shut down when a budget is exceeded can be found in the Budget Automation Tutorial.
  • Automation can be implemented via a Logic App.
  • An Azure Function can be automatically invoked.

Next Steps

The Subscription is now ready. Individual resources can now be created. In the article Resources, a website will be created and published.

Further Information