Lab — Watch an omitted property reset itself
AZ-104 › Unit 3 › Lab
Lab — Watch an omitted property reset itself
Lab brief
- AZ104-U3.T1
- 20 minutes
- A resource group and two deployments
- required
- Advanced
The claim to make physical, and the one most people get wrong: incremental mode does not mean partial update. Leave a property out of a redeploy and it goes back to its default.
Before you start
A subscription and the Azure CLI with Bicep available. Everything deployed here is a resource group and tags on it, which cost nothing.
Walkthrough
Watch an omitted property reset itself
1. Deploy a resource with two settings
Write a small Bicep file that creates one resource with two non-default properties set — tags on a resource group are enough. Deploy it. Confirm both settings are present.
Did it teach you what it was meant to?
Step 3 showed a property returning to its default. What is the correct way to change one setting and leave the rest alone?
Your what-if output is clean, but the deployment still removed a resource. What is the likely cause?
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 resource group
az group delete --name bb-lab-bicep. Nothing here was billable, but leave the tenant as you found it.
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 |
|---|---|
| Azure Resource Manager deployment modes | d10ae932c680 |
| Bicep what-if: preview changes before deployment | 4e5ed2f22855 |
| Decompile ARM template JSON to Bicep | c5099f77afdc |
| Manage Azure resource groups by using Azure CLI | a3840d837a3d |