Resources and properties
In an incremental deployment, existing resources omitted from the template remain. That rule does not mean omitted properties on a declared resource are preserved. Declare that resource’s complete intended state, including nondefault values.
Splitting properties across concurrent partial definitions does not automatically create a safe merge. Compare published configuration with application requirements before accepting a change as small or harmless.
Interpreting what-if
Compilation checks the definition; what-if compares predicted environmental changes. Neither alone proves application behavior. An unresolved expression can prevent analysis of a resource or module.
In that case, absence of displayed differences is not evidence of equality. Record the scope actually compared and resolve the dependency preventing analysis. Filtering output does not remove the resource from the actual deployment.
Execution identity
A Bicep module represents a nested deployment. Concurrent executions using the same fixed name at the same scope can interfere with observed outputs. The symbolic name in the file is different from remote deployment identity.
Use distinct execution names or generated names while retaining stable resource identity where intended. Isolating execution does not require indiscriminately duplicating infrastructure.
Migration and review exercise
Changing location in a template does not transport an existing VM to another region. Plan target resources, data, networking, dependencies and transition. In the exercise, a pipeline publishes a template with missing properties, an unanalyzed module and a shared name.
Produce three independent decisions: complete declared state, recover the omitted comparison and prevent execution collision. Then assess functional acceptance and recovery according to change risk.
Two teams receive storage outputs mixed between concurrent deployments. Record each deployment’s scope and name; correct execution identity before using outputs to authorize publication.
Common pitfalls
Avoid treating incremental as a property patch, omitted results as successful comparison, and module name as a mere comment.
Related topics: Machines, disks and effective capacity · Containers: repetition, revisions and promotion
Review should connect definition, remote state and execution identity to acceptance criteria.
References
- Deployment modes and resource state · Microsoft Learn documentation consulted 2026-10-15
- Self-service password reset eligibility · Microsoft Learn documentation consulted 2026-10-15
- Group licensing, membership and assignment transitions · Microsoft Learn documentation consulted 2026-10-15
- B2B invitation redemption · Microsoft Learn documentation consulted 2026-10-15
- Resize a virtual machine · Microsoft Learn documentation consulted 2026-10-15
- Policy remediation authorization · Microsoft Learn documentation consulted 2026-10-15
- Management group hierarchy and access · Microsoft Learn documentation consulted 2026-10-15
- Resource tags and inheritance · Microsoft Learn documentation consulted 2026-10-15
- Azure RBAC evaluation · Microsoft Learn documentation consulted 2026-10-15
- Block blob object replication · Microsoft Learn documentation consulted 2026-10-15
- Blob soft delete scopes and limitations · Microsoft Learn documentation consulted 2026-10-15
- Azure Files SMB share permissions and ACLs · Microsoft Learn documentation consulted 2026-10-15
- Shared access signatures and scoped delegation · Microsoft Learn documentation consulted 2026-10-15
- Bicep what-if and analysis limits · Microsoft Learn documentation consulted 2026-10-15
- Bicep modules and deployment identity · Microsoft Learn documentation consulted 2026-10-15
- Managed disk roles and performance limits · Microsoft Learn documentation consulted 2026-10-15
- Autoscale evaluation · Microsoft Learn documentation consulted 2026-10-15
- ACI restart policies · Microsoft Learn documentation consulted 2026-10-15
- Container Apps revision lifecycle · Microsoft Learn documentation consulted 2026-10-15
- App Service slot lifecycle · Microsoft Learn documentation consulted 2026-10-15
- App Service plan capacity · Microsoft Learn documentation consulted 2026-10-15
- App Service outbound integration · Microsoft Learn documentation consulted 2026-10-15
- KQL filtering and aggregation · Microsoft Learn documentation consulted 2026-10-15
- Azure diagnostic collection and destinations · Microsoft Learn documentation consulted 2026-10-15
- Azure VM restore options · Microsoft Learn documentation consulted 2026-10-15