Skip to content

Commit 5063eb3

Browse files
committed
added clarification for property change
1 parent 4f5a848 commit 5063eb3

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)
@@ -51,6 +51,8 @@ The following screenshots show the two different output formats:
5151

5252
![Resource Manager template deployment what-if operation fullresourcepayloads output](./media/template-deploy-what-if/resource-manager-deployment-whatif-output-fullresourcepayload.png)
5353

54+
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.
55+
5456
- Resource ID only
5557

5658
![Resource Manager template deployment what-if operation resourceidonly output](./media/template-deploy-what-if/resource-manager-deployment-whatif-output-resourceidonly.png)

0 commit comments

Comments
 (0)