Skip to content

Commit 5c2c256

Browse files
authored
Merge pull request #96546 from tfitzmac/1119whatif
added clarification for property change
2 parents 02df5c4 + 9d2d07d commit 5c2c256

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-resource-manager/template-deploy-what-if.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Template deployment what-if (Preview)
33
description: Determine what changes will happen to your resources before deploying an Azure Resource Manager template.
44
author: mumian
55
ms.topic: conceptual
6-
ms.date: 11/12/2019
6+
ms.date: 11/19/2019
77
ms.author: jgao
88
---
99
# Resource Manager template deployment what-if operation (Preview)
@@ -90,6 +90,8 @@ Notice at the top of the output that colors are defined to indicate the type of
9090

9191
At the bottom of the output, it shows the sku name (storage account type) will be changed from **Standard_LRS** to **Standard_GRS**.
9292

93+
Some of the properties that are listed as deleted won't actually change. In the preceding image, these properties are accessTier, encryption.keySource and others in that section. Properties can be incorrectly reported as deleted when they aren't in the template but are automatically set during deployment. The final deployed resource will have the values set for the properties. As the what-if operation matures, these properties will be filtered out of the result.
94+
9395
### Test deletion
9496

9597
The what-if operation supports using [deployment mode](deployment-modes.md). When set to complete mode, resources not in the template are deleted. The following example deploys a [template that has no resources defined](https://github.com/Azure/azure-docs-json-samples/blob/master/empty-template/azuredeploy.json) in complete mode.

0 commit comments

Comments
 (0)