Merge pull request #49556 from lootle1/MR78

Technical Review 1037312: Preview Azure deployment changes by using w…

Author: JamesJBarnett

learn-pr/azure/arm-template-whatif/1-introduction.yml

@@ -8,7 +8,7 @@ metadata:
   description: Introduction
   author: mumian
   ms.author: jgao
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   ms.topic: unit
   ms.custom:
     - team=nextgen

learn-pr/azure/arm-template-whatif/2-deployment-modes.yml

@@ -8,7 +8,7 @@ metadata:
   description: Learn about the two deployment modes for Azure, incremental and complete.
   author: mumian
   ms.author: jgao
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   ms.topic: unit
   ms.custom:
     - team=nextgen

learn-pr/azure/arm-template-whatif/3-what-if.yml

@@ -5,10 +5,10 @@ metadata:
   adobe-target: true
   prefetch-feature-rollout: true
   title: Predict what a deployment will do by using what-if
-  description: Deploying and hoping for the best is not the approach you should be taking. The what-if operation is here to address this fact. This unit will cover what it is and how to use it.
+  description: Deploying and hoping for the best isn't the approach you should be taking. The what-if operation is here to address this fact. This unit covers what the operation is and how to use it.
   author: mumian
   ms.author: jgao
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   ms.topic: unit
   ms.custom:
     - team=nextgen

learn-pr/azure/arm-template-whatif/4-exercise-what-if.yml

@@ -8,7 +8,7 @@ metadata:
   description: Use the what-if tool to predict what a deployment will carry out if it's applied.
   author: mumian
   ms.author: jgao
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   ms.topic: unit
   ms.custom: team=nextgen, devx-track-bicep
   zone_pivot_groups: arm-template-language-azure-shell-interface

learn-pr/azure/arm-template-whatif/5-knowledge-check.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: Three multiple-choice questions
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   author: mumian
   ms.author: jgao
   ms.topic: unit

learn-pr/azure/arm-template-whatif/6-summary.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: Summary
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   author: mumian
   ms.author: jgao
   ms.topic: unit

learn-pr/azure/arm-template-whatif/includes/4-exercise-what-if.md

@@ -31,8 +31,8 @@ You start with an existing template that your team has been using. The template
 
 1. Create a new file called *azuredeploy.json*.
 
-1. Save the empty file so that Visual Studio Code loads the ARM template tooling. 
- 
+1. Save the empty file so that Visual Studio Code loads the ARM template tooling.
+
    You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you've saved the file. For example, you might want to create a *scripts* folder to save it in.
 
 1. Copy the following code into *azuredeploy.json*.
@@ -49,8 +49,8 @@ You start with an existing template that your team has been using. The template
 
 1. Create a new file called *main.bicep*.
 
-1. Save the empty file so that Visual Studio Code loads the Bicep tooling. 
- 
+1. Save the empty file so that Visual Studio Code loads the Bicep tooling.
+
    You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you've saved the file. For example, you might want to create a *scripts* folder to save it in.
 
 1. Copy the following code into *main.bicep*.
@@ -173,7 +173,7 @@ To validate that your deployment has been created and sent to Azure, go to the [
 
 ::: zone pivot="jsonpowershell,jsoncli"
 
-1. In the *azuredeploy.json* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this: 
+1. In the *azuredeploy.json* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this:
 
    :::code language="json" source="code/4-template-after.json" range="12-14" :::
 
@@ -191,7 +191,7 @@ To validate that your deployment has been created and sent to Azure, go to the [
 
 ::: zone pivot="biceppowershell,bicepcli"
 
-1. In the *main.bicep* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this: 
+1. In the *main.bicep* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this:
 
    :::code language="bicep" source="code/4-template-after.bicep" range="6-8" :::
 
@@ -273,9 +273,9 @@ The what-if output is similar to the following one:
 
 Notice that the result is color-coded in addition to having a prefix:
 
-- Purple and **~** for any modifications
-- Green and **+** for new resources to be created
-- Orange and **-** for deletions
+* Purple and **~** for any modifications
+* Green and **+** for new resources to be created
+* Orange and **-** for deletions
 
 ## Remove the resources in the template
 

learn-pr/azure/arm-template-whatif/index.yml

@@ -7,7 +7,7 @@ metadata:
   description: Apply the what-if command to see the effect of a deployment before it's applied.
   ms.service: azure-resource-manager
   manager: jasongroce
-  ms.date: 01/31/2025
+  ms.date: 03/18/2025
   author: mumian
   ms.author: jgao
   ms.topic: module