A configuration change can succeed while the requested business outcome still fails. Reed Leasing repairs the wrong resource group because an archived service uses the same name as the live target. Another release rolls traffic back successfully but leaves data incompatible with the old application.
Read the scope, current state, approved inputs and recovery path as one change record. A preview is tied to a state and parameter set; a later change can invalidate it. Also distinguish a local checked setting from a real Azure deployment and a working customer action. These decisions use original fictional changes. They do not query production, execute rollback, or prove application behavior. A useful handoff names the exact target and observed state, the test of the original action, and any gap still open.
Keep change claims tied to the actual target and verified result.