Lab — A budget notifies and stops nothing
AZ-104 › Unit 1 › Lab
Lab — A budget notifies and stops nothing
Lab brief
- AZ104-U1.T3
- 15 minutes
- A budget and an action group
- required
- Foundational
The shortest lab in the set, and it exists for one sentence: resources aren't affected, and your consumption isn't stopped. Every learner nods at that and a third of them still answer 'budget' when a stem says 'prevent overspend'.
Before you start
A subscription you can read cost data on. A budget is a cost-management object and creates no billable resource.
Walkthrough
A budget notifies and stops nothing
1. Create a budget below your current spend
Set the amount deliberately low — below what the subscription has already used this period — so the threshold is already exceeded and you do not have to wait for reality to catch up.
Did it teach you what it was meant to?
Step 4 deployed a resource with the budget already exceeded. What does a budget do at that moment?
Why is a budget a poor answer to 'alert us the moment a runaway script starts spending'?
What goes wrong
Tear it down
Run this whether or not the lab worked. Everything above was chosen to cost approximately nothing, and leaving it in place is how approximately nothing becomes something.
Teardown
Delete the budget and the action group
Neither costs anything, but a budget with a deliberately wrong amount left in place will keep emailing somebody every day, which is its own small punishment.
Where these figures come from
Every figure above was read from the raw documentation below on the day this sheet was written. The sha1 is git hash-object over the bytes as fetched, so a doc that changes underneath this sheet can be detected rather than assumed.
| Document | sha1 |
|---|---|
| Tutorial: Create and manage Azure budgets | 051db0341cf9 |