Lets you preview a Bicep or ARM template deployment before running it, listing what Resource Manager would create, modify or delete while leaving everything untouched.
Also called what-if operation.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains What-if in context, with comparison tables and the common traps.
Terms in this definition
- Bicep
Domain-specific language for declaring Azure infrastructure as code, which is compiled into ARM templates.
- ARM template
JSON file describing Azure infrastructure declaratively. Once deployed it keeps no live connection to the resources, unlike Blueprints, which retires fully on 31 January 2027.
- Model deployment
Inside a resource, each deployment is a named copy of a Foundry model with its own TPM quota and deployment type. Requests identify the model by this deployment name.
- CRUD
Shorthand for create, read, update and delete, the four basic things you do with data. Data-plane roles in Azure Cosmos DB, for instance, authorise those operations on items.
- Modify
Policy effect in Azure that can add, replace or remove tags and other properties. Resources that already exist are brought into line by running a remediation task.
Related terms
- GENERATESERIES
A DAX function that builds a one-column table, with the column called Value, listing numbers that step evenly from a starting point to an end point (by 1 unless told otherwise). It is a common way to make a disconnected table for what-if parameters.