Merge pull request #234132 from divargas-msft/patch-6

[Doc-a-thon] Updating template-description.md

Author: prmerger-automator[bot]

articles/virtual-machines/windows/template-description.md

@@ -6,19 +6,18 @@ ms.service: virtual-machines
 ms.workload: infrastructure
 ms.custom: devx-track-arm-template
 ms.topic: how-to
-ms.date: 01/03/2019
+ms.date: 04/11/2023
 ms.author: cynthn 
 ---
 
 # Virtual machines in an Azure Resource Manager template
-**Applies to:** :heavy_check_mark: Windows VMs 
+
+**Applies to:** :heavy_check_mark: Windows VMs
 
 This article describes aspects of an Azure Resource Manager template that apply to virtual machines. This article doesn't describe a complete template for creating a virtual machine; for that you need resource definitions for storage accounts, network interfaces, public IP addresses, and virtual networks. For more information about how these resources can be defined together, see the [Resource Manager template walkthrough](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
 
 There are many [templates in the gallery](https://azure.microsoft.com/resources/templates/?term=VM) that include the VM resource. Not all elements that can be included in a template are described here.
 
- 
-
 This example shows a typical resource section of a template for creating a specified number of VMs:
 
 ```json
@@ -134,9 +133,9 @@ This example shows a typical resource section of a template for creating a speci
     ]
   } 
 ]
-``` 
+```
 
-> [!NOTE] 
+> [!NOTE]
 >This example relies on a storage account that was previously created. You could create the storage account by deploying it from the template. The example also relies on a network interface and its dependent resources that would be defined in the template. These resources are not shown in the example.
 >
 >
@@ -157,7 +156,6 @@ Use these opportunities for getting the latest API versions:
 - PowerShell - [Get-AzResourceProvider](/powershell/module/az.resources/get-azresourceprovider)
 - Azure CLI - [az provider show](/cli/azure/provider)
 
-
 ## Parameters and variables
 
 [Parameters](../../azure-resource-manager/templates/syntax.md) make it easy for you to specify values for the template when you run it. This parameters section is used in the example:
@@ -228,7 +226,7 @@ Also, notice in the example that the loop index is used when specifying some of
 }
 ```
 
-> [!NOTE] 
+> [!NOTE]
 >This example uses managed disks for the virtual machines.
 >
 >
@@ -270,17 +268,17 @@ To set this property, the network interface must exist. Therefore, you need a de
 ## Profiles
 
 Several profile elements are used when defining a virtual machine resource. Some are required and some are optional. For example, the hardwareProfile, osProfile, storageProfile, and networkProfile elements are required, but the diagnosticsProfile is optional. These profiles define settings such as:
-   
+
 - [size](../sizes.md)
 - [name](/azure/architecture/best-practices/resource-naming) and credentials
 - disk and [operating system settings](cli-ps-findimage.md)
 - [network interface](/previous-versions/azure/virtual-network/virtual-network-deploy-multinic-classic-ps) 
 - boot diagnostics
 
 ## Disks and images
-   
+
 In Azure, vhd files can represent [disks or images](../managed-disks-overview.md). When the operating system in a vhd file is specialized to be a specific VM, it's referred to as a disk. When the operating system in a vhd file is generalized to be used to create many VMs, it's referred to as an image.   
-    
+
 ### Create new virtual machines and new disks from a platform image
 
 When you create a VM, you must decide what operating system to use. The imageReference element is used to define the operating system of a new VM. The example shows a definition for a Windows Server operating system:
@@ -300,11 +298,14 @@ If you want to create a Linux operating system, you might use this definition:
 "imageReference": {
   "publisher": "Canonical",
   "offer": "UbuntuServer",
-  "sku": "14.04.2-LTS",
+  "sku": "20.04.2-LTS",
   "version": "latest"
 },
 ```
 
+> [!NOTE]
+> Modify `publisher`, `offer`, `sku` and `version` values accordingly.
+
 Configuration settings for the operating system disk are assigned with the osDisk element. The example defines a new managed disk with the caching mode set to **ReadWrite** and that the disk is being created from a [platform image](cli-ps-findimage.md):
 
 ```json
@@ -443,7 +444,7 @@ When you deploy a template, Azure tracks the resources that you deployed as a gr
 If you're curious about the status of resources in the deployment, view the resource group in the Azure portal:
 
 ![Get deployment information](./media/template-description/virtual-machines-deployment-info.png)
-    
+
 It's not a problem to use the same template to create resources or to update existing resources. When you use commands to deploy templates, you have the opportunity to say which [mode](../../azure-resource-manager/templates/deploy-powershell.md) you want to use. The mode can be set to either **Complete** or **Incremental**. The default is to do incremental updates. Be careful when using the **Complete** mode because you may accidentally delete resources. When you set the mode to **Complete**, Resource Manager deletes any resources in the resource group that aren't in the template.
 
 ## Next Steps