Merge pull request #175151 from MicrosoftDocs/release-v5-vm-series

Standing PR w/ Master | release-v5-vm-series

Author: huypub

articles/virtual-machines/TOC.yml

@@ -169,12 +169,18 @@
         href: dv2-dsv2-series.md
       - name: Dv3 and DSv3-series
         href: dv3-dsv3-series.md
+      - name: Dv4 and Dsv4-series
+        href: dv4-dsv4-series.md
       - name: Dav4 and Dasv4-series
         href: dav4-dasv4-series.md
       - name: Ddv4 and Ddsv4-series
         href: ddv4-ddsv4-series.md
-      - name: Dv4 and Dsv4-series
-        href: dv4-dsv4-series.md
+      - name: Dv5 and Dsv5-series
+        href: dv5-dsv5-series.md
+      - name: Ddv5 and Ddsv5-series
+        href: ddv5-ddsv5-series.md
+      - name: Dasv5 and Dadsv5-series
+        href: dasv5-dadsv5-series.md
     - name: Compute optimized
       items:
       - name: Overview
@@ -199,6 +205,12 @@
         href: edv4-edsv4-series.md
       - name: Ev4 and Esv4-series
         href: ev4-esv4-series.md
+      - name: Ev5 and Esv5-series
+        href: ev5-esv5-series.md
+      - name: Edv5 and Edsv5-series
+        href: edv5-edsv5-series.md
+      - name: Easv5 and Eadsv5-series
+        href: easv5-eadsv5-series.md
       - name: M-series
         href: m-series.md
       - name: Msv2 and Mdsv2 Medium Memory series
@@ -237,6 +249,8 @@
         href: nct4-v3-series.md
       - name: NDasrA100_v4-series
         href: nda100-v4-series.md
+      - name: NDm_A100_v4-series
+        href: ndm-a100-v4-series.md
       - name: ND-series
         href: nd-series.md
       - name: NDv2-series
@@ -1611,7 +1625,7 @@
       - name: Portal
         displayName: Maintenance control for OS image upgrade, OS, image, upgrade
         href: virtual-machine-scale-sets-maintenance-control-portal.md
-  - name: Automatic VM guest patching (Preview)
+  - name: Automatic VM guest patching
     items:
     - name: Overview
       displayName: Automatic VM guest patching, guest, OS, patching

articles/virtual-machines/acu.md

@@ -79,4 +79,4 @@ Here are links to more information about the different sizes:
 - [Compute optimized](sizes-compute.md)
 - [GPU optimized](sizes-gpu.md)
 - [High performance compute](sizes-hpc.md)
-- [Storage optimized](sizes-storage.md)
+- [Storage optimized](sizes-storage.md)

articles/virtual-machines/automatic-vm-guest-patching.md

@@ -6,12 +6,12 @@ ms.service: virtual-machines
 ms.subservice: maintenance
 ms.workload: infrastructure
 ms.topic: how-to
-ms.date: 10/18/2021
+ms.date: 10/20/2021
 ms.author: manayar
 ms.custom: devx-track-azurepowershell
 
 ---
-# Preview: Automatic VM guest patching for Azure VMs
+# Automatic VM guest patching for Azure VMs
 
 **Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets
 
@@ -24,11 +24,6 @@ Automatic VM guest patching has the following characteristics:
 - Virtual machine health, as determined through platform health signals, is monitored to detect patching failures.
 - Works for all VM sizes.
 
-> [!IMPORTANT]
-> Automatic VM guest patching is currently in Public Preview.
-> This preview version is provided without a service level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
-> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-
 ## How does automatic VM guest patching work?
 
 If automatic VM guest patching is enabled on a VM, then the available *Critical* and *Security* patches are downloaded and applied automatically on the VM. This process kicks off automatically every month when new patches are released. Patch assessment and installation are automatic, and the process includes rebooting the VM as required.
@@ -73,7 +68,7 @@ For OS types that release patches on a fixed cadence, VMs configured to the publ
 As a new rollout is triggered every month, a VM will receive at least one patch rollout every month if the VM is powered on during off-peak hours. This process ensures that the VM is patched with the latest available security and critical patches on a monthly basis. To ensure consistency in the set of patches installed, you can configure your VMs to assess and download patches from your own private repositories.
 
 ## Supported OS images
-Only VMs created from certain OS platform images are currently supported in the preview. Custom images are currently not supported in the preview.
+Only VMs created from certain OS platform images are currently supported. Custom images are currently not supported.
 
 The following platform SKUs are currently supported (and more are added periodically):
 
@@ -86,8 +81,8 @@ The following platform SKUs are currently supported (and more are added periodic
 | Redhat  | RHEL | 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7_9, 7-RAW, 7-LVM |
 | Redhat  | RHEL | 8, 8.1, 8.2, 8_3, 8_4, 8-LVM |
 | Redhat  | RHEL-RAW | 8-raw |
-| OpenLogic  | Centos | 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7_8, 7_9, 7-LVM |
-| OpenLogic  | Centos | 8.0, 8_1, 8_2, 8_3, 8-lvm |
+| OpenLogic  | CentOS | 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7_8, 7_9, 7-LVM |
+| OpenLogic  | CentOS | 8.0, 8_1, 8_2, 8_3, 8-lvm |
 | SUSE  | sles-12-sp5 | gen1, gen2 |
 | SUSE  | sles-15-sp2 | gen1, gen2 |
 | MicrosoftWindowsServer  | WindowsServer | 2008-R2-SP1 |
@@ -227,7 +222,7 @@ It can take more than three hours to enable automatic VM guest updates on a VM,
 Automatic updates are disabled in most scenarios, and patch installation is done through the extension going forward. The following conditions apply.
 - If a Windows VM previously had Automatic Windows Update turned on through the AutomaticByOS patch mode, then Automatic Windows Update is turned off for the VM when the extension is installed.
 - For Ubuntu VMs, the default automatic updates are disabled automatically when Automatic VM Guest Patching completes enablement.
-- For RHEL, automatic updates need to be manually disabled in the preview. Execute:
+- For RHEL, automatic updates need to be manually disabled. Execute:
 
 ```
 systemctl stop packagekit

articles/virtual-machines/azure-vms-no-temp-disk.yml

@@ -15,7 +15,7 @@ summary: |
   > [!TIP]
   > Try the **[Virtual Machine selector tool](https://aka.ms/vm-selector)** to find other sizes that best fit your workload.
 
-  This article provides answers to frequently asked questions (FAQ) about Azure VM sizes that do not have a local temporary disk (i.e. no local temp disk). For more information on these VM sizes, see [Specifications for Dv4 and Dsv4-series (General Purpose Workloads)](dv4-dsv4-series.md) or [Specifications for Ev4 and Esv4-series (Memory Optimized Workloads)](ev4-esv4-series.md).
+  This article provides answers to frequently asked questions (FAQ) about Azure VM sizes that do not have a local temporary disk (i.e. no local temp disk).
   
 
 sections:
@@ -24,25 +24,16 @@ sections:
       - question: |
           What does no local temp disk mean? 
         answer: |
-          Traditionally, we have had VM sizes (e.g. Standard_D2s_v3, Standard_E48_v3) that include a small local disk (i.e. a D: Drive). Now with these new VM sizes, that small local disk no longer exists; however, you can still attach Standard HDD, Premium SSD or Ultra SSD.
+          Traditionally, we have had VM sizes (e.g. Standard_D2s_v3, Standard_E48_v3) that include a small local disk (i.e. a D: Drive). With the VM series such as [Dasv5](dasv5-dadsv5-series.md) and [Easv5](easv5-eadsv5-series.md) that small local disk no longer exists. However, you can still attach Standard HDD, Premium SSD or Ultra SSD to use as remote storage.
           
       - question: |
           What if I still want a local temp disk?
         answer: |
-          If your workload requires a local temporary disk, we also have new [Ddv4 and Ddsv4](ddv4-ddsv4-series.md) or [Edv4 and Edsv4](edv4-edsv4-series.md) VM sizes available. These sizes offer 50% larger temporary disk compared with the previous v3 sizes.
+          If your workload requires a local temporary disk, we still offer sizes such as the [Dadsv5](dasv5-dadsv5-series.md). 
           
           > [!NOTE]
           > Local temporary disk is not persistent; to ensure your data is persistent, please use Standard HDD, Premium SSD or Ultra SSD options. 
-          
-      - question: |
-          What are the differences between these new VM sizes and the General Purpose Dv3/Dsv3 or the Memory Optimized Ev3/Esv3 VM sizes that I am used to? 
-        answer: |
-          | v3 VM families with local temp disk	| New v4 families with local temp disk | New v4 families with no local temp disk |
-          |---|---|---|
-          | Dv3	| Ddv4 | Dv4 |
-          | Dsv3 | Ddsv4  | Dsv4 |
-          | Ev3	| Edv4  | Ev4 |
-          | Esv3 | Edsv4 |	Esv4 | 
+
           
       - question: |
           Can I resize a VM size that has a local temp disk to a VM size with no local temp disk?  
@@ -69,7 +60,7 @@ sections:
              > Follow the guidelines on the "Temporarily move pagefile.sys to C drive" section of Use the D: drive as a data drive on a Windows VM to move page file from the local temporary disk (D: drive) to C: drive. **Deviation from the steps outlined will lead to the error message - "Unable to resize the VM since changing from resource disk to non-resource disk VM size and vice-versa is not allowed.**
           
           3. Take a snapshot of the VM by following the steps outlined in [Create a snapshot using the portal or Azure CLI](./linux/snapshot-copy-managed-disk.md). 
-          4. Use snapshot to create a new diskless VM (such as, Dv4, Dsv4, Ev4, Esv4 series) by following the steps outlined in [Create a virtual machine from a snapshot with CLI](/previous-versions/azure/virtual-machines/scripts/virtual-machines-linux-cli-sample-create-vm-from-snapshot). 
+          4. Use snapshot to create a new diskless VM (such as, Dv5, Dsv5, Dasv5, Ev5, Esv5, Easv5 series) by following the steps outlined in [Create a virtual machine from a snapshot with CLI](/previous-versions/azure/virtual-machines/scripts/virtual-machines-linux-cli-sample-create-vm-from-snapshot). 
           
       - question: |
           Do these VM sizes support both Linux and Windows Operating Systems (OS)?
@@ -92,5 +83,8 @@ additionalContent: |
   
   In this document, you learned more about the most frequent questions related to Azure VMs with no local temp disk. For more information about these VM sizes, see the following articles:
   
-  - [Specifications for Dv4 and Dsv4-series (General Purpose Workload)](dv4-dsv4-series.md)
-  - [Specifications for Ev4 and Esv4-series (Memory Optimized Workload)](ev4-esv4-series.md)
+  - [Specifications for Dv5 and Dsv5-series](dv5-dsv5-series.md)
+  - [Specifications for Dasv5 and Dadsv5-series](dasv5-dadsv5-series.md)
+  - [Specifications for Ev5 and Esv5-series](ev5-esv5-series.md)
+  - [Specifications for Easv5 and Eadsv5-series](easv5-eadsv5-series.md)
+