You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What-if expands nested templates until these limits are reached:
24
+
25
+
- 500 nested templates.
26
+
- 800 resource groups in a cross resource-group deployment.
27
+
- 5 minutes have been taken for expanding the nested templates.
28
+
29
+
When one of the limits is reached, the remaining resources' [change type](#change-types) is set to **Ignore**.
30
+
23
31
## Install Azure PowerShell module
24
32
25
33
To use what-if in PowerShell, you must have version **4.2 or later of the Az module**.
@@ -132,7 +140,7 @@ The what-if operation lists six different types of changes:
132
140
133
141
-**Delete**: This change type only applies when using [complete mode](deployment-modes.md) for deployment. The resource exists, but isn't defined in the template. With complete mode, the resource will be deleted. Only resources that [support complete mode deletion](./deployment-complete-mode-deletion.md) are included in this change type.
134
142
135
-
-**Ignore**: The resource exists, but isn't defined in the template. The resource won't be deployed or modified.
143
+
-**Ignore**: The resource exists, but isn't defined in the template. The resource won't be deployed or modified. When you reach the limits for expanding nested templates, you will encounter this change type. See [What-if limits](#what-if-limits).
136
144
137
145
-**NoChange**: The resource exists, and is defined in the template. The resource will be redeployed, but the properties of the resource won't change. This change type is returned when [ResultFormat](#result-format) is set to `FullResourcePayloads`, which is the default value.
0 commit comments