Merge pull request #101239 from jboeshart/patch-5

Update virtual-machines-using-managed-disks-template-deployments.md

Author: PRMerger13

includes/virtual-machines-using-managed-disks-template-deployments.md

@@ -91,7 +91,16 @@ With Azure Managed Disks, the disk becomes a top-level resource and no longer re
 
 ### Default managed disk settings
 
-To create a VM with managed disks, you no longer need to create the storage account resource and can update your virtual machine resource as follows. Specifically note that the `apiVersion` reflects `2017-03-30` and the `osDisk` and `dataDisks` no longer refer to a specific URI for the VHD. When deploying without specifying additional properties, the disk will use a Storage type based on the size of the VM. For example, if you are using a Premium capable VM Size (sizes with "s" in their name such as Standard_D2s_v3) then system will use Premium_LRS storage. Use the sku setting of the disk to specify a Storage type. If no name is specified, it takes the format of `<VMName>_OsDisk_1_<randomstring>` for the OS disk and `<VMName>_disk<#>_<randomstring>` for each data disk. By default, Azure disk encryption is disabled; caching is Read/Write for the OS disk and None for data disks. You may notice in the example below there is still a storage account dependency, though this is only for storage of diagnostics and is not needed for disk storage.
+To create a VM with managed disks, you no longer need to create the storage account resource. Referencing the template example below, there are some differences from the previous unmanged disk examples to note:
+
+- The `apiVersion` is a version that supports managed disks.
+- `osDisk` and `dataDisks` no longer refer to a specific URI for the VHD.
+- When deploying without specifying additional properties, the disk will use a storage type based on the size of the VM. For example, if you are using a VM size that supports premium storage (sizes with "s" in their name such as Standard_D2s_v3) then premium disks will be configured by default. You can change this by using the sku setting of the disk to specify a storage type.
+- If no name for the disk is specified, it takes the format of `<VMName>_OsDisk_1_<randomstring>` for the OS disk and `<VMName>_disk<#>_<randomstring>` for each data disk.
+  - If a VM is being created from a custom image then the default settings for storage account type and disk name are retrieved from the disk properties defined in the custom image resource. These can be overridden by specifying values for these in the template.
+- By default, Azure disk encryption is disabled.
+- By default, disk caching is Read/Write for the OS disk and None for data disks.
+- In the example below there is still a storage account dependency, though this is only for storage of diagnostics and is not needed for disk storage.
 
 ```json
 {