Merge branch 'main' into jushim-2

Author: cynthn

articles/virtual-machines/boot-diagnostics.md

@@ -20,10 +20,7 @@ Boot diagnostics is a debugging feature for Azure virtual machines (VM) that all
 
 ## Boot diagnostics storage account
 
-When you create a VM in Azure portal, boot diagnostics is enabled by default. The recommended boot diagnostics experience is to use a managed storage account, as it yields significant performance improvements in the time to create an Azure VM. An Azure managed storage account is used, removing the time it takes to create a user storage account to store the boot diagnostics data.
-
-> [!IMPORTANT]
-> The boot diagnostics data blobs (which comprise of logs and snapshot images) are stored in a managed storage account. Customers will be charged only on used GiBs by the blobs, not on the disk's provisioned size. The snapshot meters will be used for billing of the managed storage account. Because the managed accounts are created on either Standard LRS or Standard ZRS, customers will be charged at $0.05/GB per month for the size of their diagnostic data blobs only. For more information on this pricing, see [Managed disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/). Customers see this charge tied to their VM resource URI.
+When you create a VM in Azure portal, boot diagnostics is enabled by default. The recommended boot diagnostics experience is to use a managed storage account, as it yields significant performance improvements in the time to create an Azure VM. Using a managed storage account eliminates the time needed to create a user storage account to store the boot diagnostics data. When using a managed storage account: The managed storage account is not directly accessible, and the boot diagnostics data blobs (which comprise of logs and snapshot images) stored in the managed storage account are not currently billed. 
 
 An alternative boot diagnostic experience is to use a custom storage account. A user can either create a new storage account or use an existing one. When the storage firewall is enabled on the custom storage account (**Enabled from all networks** option isn't selected), you must:
 

articles/virtual-machines/capacity-reservation-group-share.md

@@ -501,7 +501,7 @@ Zonally deployed virtual machines or virtual machine scale sets from Consumer su
 
 2. Associate existing running zonal virtual machine or virtual machine scale set from the Consumer subscription to the shared capacity reservation group. Set the Virtual Machine or Virtual Machine Scale Set (VMSS) capacityReservationGroup property to the desired shared Capacity Reservation Group. When complete, each target capacity reservation will be overallocated. 
 
-3. Increase the reserved quantity of each capacity reservation (CR) to match the allocated Virtual Machine (VM) count. If sufficient quota is not available, this step requires additional quota on the Provider subscription to accomodate the workloads from the Consumer subscription. See [Using a shared Capacity Reservation Group](#using-a-shared-capacity-reservation-group). For more information on how to update the reserved count, see [Capacity reservation modify](/azure/virtual-machines/capacity-reservation-modify?tabs=api1%2Capi2%2Capi3#update-the-number-of-instances-reserved)
+3. Increase the reserved quantity of each capacity reservation (CR) to match the allocated Virtual Machine (VM) count. The Provider subscription must have sufficient quota to accomodate the workloads from the Consumer subscription for this step. See [Using a shared Capacity Reservation Group](#using-a-shared-capacity-reservation-group). For more information on how to update the reserved count, see [Capacity reservation modify](/azure/virtual-machines/capacity-reservation-modify?tabs=api1%2Capi2%2Capi3#update-the-number-of-instances-reserved)
 
 After the quantity increase, you should see the CR in a fully allocated state with all the virtual machines or virtual machine scale sets allocated. See [View VM allocation with the Instance View](/azure/virtual-machines/capacity-reservation-associate-vm?tabs=api1%2Capi2%2Capi3#view-vm-allocation-with-the-instance-view).
 

articles/virtual-machines/capture-image-resource.yml

@@ -132,7 +132,7 @@ procedureSection:
         Create the image configuration.
 
         ```azurepowershell-interactive
-        $image = New-AzImageConfig -Location $location -SourceVirtualMachineId $vm.Id 
+        $imageConfig = New-AzImageConfig -Location $location -SourceVirtualMachineId $vm.Id 
         ```
       - |
         Create the image.

articles/virtual-machines/configure.md

@@ -6,13 +6,13 @@ ms.subservice: hpc
 ms.custom: linux-related-content
 ms.topic: concept-article
 ms.date: 07/25/2024
-ms.reviewer: cynthn, mattmcinnes
-ms.author: jushiman
+ms.reviewer: mattmcinnes
+ms.author: cynthn
 author: cynthn
 # Customer intent: "As an HPC administrator, I want to configure and optimize InfiniBand-enabled virtual machines, so that I can ensure high performance and efficient workload management for my high-performance computing tasks."
 ---
 
-# Configure and optimize VMs
+# Configure and optimize the InfiniBand enabled H-series and N-series VMs
 
 **Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
 

articles/virtual-machines/ecasccv5-ecadsccv5-series.md

@@ -35,16 +35,15 @@ This series supports Standard SSD, Standard HDD, and Premium SSD disk types. Bil
 
 The ECas_cc_v5-series sizes offer a combination of vCPU and memory for most production workloads. The ECas_cc_v5-series sizes offer a combination of vCPU and memory that is ideal for memory-intensive enterprise applications. These new VMs with no local disk provide a better value proposition for workloads that do not require local temp disk.
 
-[Trusted Launch](trusted-launch.md): Not Supported - we are working to support for this feature. For now - please choose Standard security type when using this VM size) <br>
-[Premium Storage](premium-storage-performance.md): Supported <br>
-[Premium Storage caching](premium-storage-performance.md): Supported <br>
-[Live Migration](maintenance-and-updates.md): Not Supported <br>
-[Memory Preserving Updates](maintenance-and-updates.md): Not Supported <br>
-[VM Generation Support](generation-2.md): Generation 2 <br>
-[Accelerated Networking](/azure/virtual-network/create-vm-accelerated-networking-cli): Supported <br>
-[Ephemeral OS Disks](ephemeral-os-disks.md): Supported <br>
-[Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization): Supported <br>
-<br>
+- [Trusted Launch](trusted-launch.md): Not Supported - we are working to support this feature. For now, please choose Standard security type when using this VM size.
+- [Premium Storage](premium-storage-performance.md): Supported
+- [Premium Storage caching](premium-storage-performance.md): Supported
+- [Live Migration](maintenance-and-updates.md): Not Supported
+- [Memory Preserving Updates](maintenance-and-updates.md): Not Supported
+- [VM Generation Support](generation-2.md): Generation 2
+- [Accelerated Networking](/azure/virtual-network/create-vm-accelerated-networking-cli): Supported
+- [Ephemeral OS Disks](ephemeral-os-disks.md): Supported
+- [Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization): Supported
 
 
 | Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | Max data disks | Max uncached disk throughput: IOPS/MBps | Max NICs |
@@ -63,16 +62,16 @@ The ECas_cc_v5-series sizes offer a combination of vCPU and memory for most prod
 
 The ECads_cc_v5-series sizes offer a combination of vCPU, memory and temporary storage for most production workloads. The ECads_cc_v5-series sizes offer a combination of vCPU, memory and temporary storage that is ideal for memory-intensive enterprise applications. 
 
-[Trusted Launch](trusted-launch.md): Not Supported - we are working to support for this feature. For now - please choose Standard security type when using this VM size) <br>
-[Premium Storage](premium-storage-performance.md): Supported <br>
-[Premium Storage caching](premium-storage-performance.md): Supported <br>
-[Live Migration](maintenance-and-updates.md): Not Supported <br>
-[Memory Preserving Updates](maintenance-and-updates.md): Not Supported <br>
-[VM Generation Support](generation-2.md): Generation 2 <br>
-[Accelerated Networking](/azure/virtual-network/create-vm-accelerated-networking-cli): Supported <br>
-[Ephemeral OS Disks](ephemeral-os-disks.md): Supported <br>
-[Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization): Supported <br>
-<br>
+- [Trusted Launch](trusted-launch.md): Not Supported - we are working to support this feature. For now, please choose Standard security type when using this VM size.
+- [Premium Storage](premium-storage-performance.md): Supported
+- [Premium Storage caching](premium-storage-performance.md): Supported
+- [Live Migration](maintenance-and-updates.md): Not Supported
+- [Memory Preserving Updates](maintenance-and-updates.md): Not Supported
+- [VM Generation Support](generation-2.md): Generation 2
+- [Accelerated Networking](/azure/virtual-network/create-vm-accelerated-networking-cli): Supported
+- [Ephemeral OS Disks](ephemeral-os-disks.md): Supported
+- [Local temporary storage](overview.md#local-temporary-storage): Supported
+- [Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization): Supported
 
 | Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | Max data disks | Max uncached disk throughput: IOPS/MBps | Max NICs |
 |---|---|---|---|---|---|---|

articles/virtual-machines/ecasv5-ecadsv5-series.md

@@ -45,6 +45,7 @@ This series supports Standard SSD, Standard HDD, and Premium SSD disk types. Bil
 - [Memory Preserving Updates](maintenance-and-updates.md)
 - [Accelerated Networking](/azure/virtual-network/create-vm-accelerated-networking-cli)
 - [Ephemeral OS Disks](ephemeral-os-disks.md)
+- [Local temporary storage](overview.md#local-temporary-storage)
 - [Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization)
 
 ### ECasv5-series products
@@ -72,16 +73,17 @@ This series supports Standard SSD, Standard HDD, and Premium SSD disk types. Bil
 
 ### ECadsv5-series feature support
 
-*Supported* features in DCasv5-series VMs:
+*Supported* features in ECadsv5-series VMs:
 
 - [Premium Storage](premium-storage-performance.md)
 - [Premium Storage caching](premium-storage-performance.md)
 - [VM Generation 2](generation-2.md)
 - [Ephemeral OS Disks](ephemeral-os-disks.md)
+- [Local temporary storage](overview.md#local-temporary-storage)
 
-*Unsupported* features in DCasv5-series VMs:
+*Unsupported* features in ECadsv5-series VMs:
 
-- [Live Migration](maintenance-and-updates.md)
+- [Live Migration](maintenance-and-updates.md#live-migration)
 - [Memory Preserving Updates](maintenance-and-updates.md)
 - [Accelerated Networking](/azure/virtual-network/create-vm-accelerated-networking-cli)
 

articles/virtual-machines/ephemeral-os-disks.md

@@ -5,7 +5,7 @@ author: viveksingla08
 ms.service: azure-virtual-machines
 ms.custom:
 ms.topic: how-to
-ms.date: 07/23/2020
+ms.date: 10/08/2025
 ms.author: viveksingla
 ms.subservice: disks
 # Customer intent: As a cloud engineer, I want to implement ephemeral OS disks for Azure VMs, so that I can achieve lower latency and faster reimaging for stateless applications while optimizing storage costs and performance.
@@ -109,17 +109,20 @@ For the same example, if you create a standard Ephemeral OS disk VM you wouldn't
 >
 > If you use ephemeral disks with Trusted Launch VMs, any keys or secrets that the vTPM generates or seals after the VM is created might not be saved. As a result, these keys and secrets could be lost during actions such as reimaging or service healing events.
 >
+
 For more information on [how to deploy a trusted launch VM](trusted-launch-portal.md)
 
 ## Confidential VMs using Ephemeral OS disks
 
 AMD-based Confidential VMs cater to high security and confidentiality requirements of customers. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. There are limitations to use Confidential VMs. Check the [region](/azure/confidential-computing/confidential-vm-overview#regions), [size](/azure/confidential-computing/confidential-vm-overview#size-support), and [OS supported](/azure/confidential-computing/confidential-vm-overview#os-support) limitations for confidential VMs.
 Virtual machine guest state (VMGS) blob contains the security information of the confidential VM.
 Confidential VMs using Ephemeral OS disks by default **1 GiB** from the **OS cache** or **temp storage** based on the chosen placement option is reserved for VMGS. The lifecycle of the VMGS blob is tied to that of the OS Disk.
+
 > [!IMPORTANT]
 >
 > When choosing a confidential VM with full OS disk encryption before VM deployment that uses a customer-managed key (CMK). [Updating a CMK key version](/azure/storage/common/customer-managed-keys-overview#update-the-key-version) or [key rotation](/azure/key-vault/keys/how-to-configure-key-rotation) isn't supported with Ephemeral OS disk. Confidential VMs using Ephemeral OS disks need to be deleted before updating or rotating the keys and can be re-created later.
 >
+
 For more information on [confidential VM](/azure/confidential-computing/confidential-vm-overview)
 
 ## Customer Managed key
@@ -130,6 +133,7 @@ You can choose to use customer managed keys or platform managed keys when you en
 >
 > [Updating a CMK key version](/azure/storage/common/customer-managed-keys-overview#update-the-key-version) or [key rotation](/azure/key-vault/keys/how-to-configure-key-rotation) of customer managed key isn't supported with Ephemeral OS disk. VMs using Ephemeral OS disks need to be deleted before updating or rotating the keys and can be re-created later.
 >
+
 For more information on [Encryption at host](./disk-encryption.md)
 
 ## SSD storage account support for Ephemeral OS disks
@@ -139,6 +143,15 @@ SSD support is a new option that allows customers to choose the type of base dis
 - **Enhanced SLA**: VMs created with Premium SSD provide higher SLA than VMs created with Standard HDD. Customers can enhance [SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services) for their Ephemeral VMs by choosing Premium SSD as base disk.
 - **Improved performance**: By choosing Premium SSD as the base disk, customers can enhance the disk read performance of their VMs. While most writes occur on the local temp disk, some reads are performed from managed disks. Premium SSD disks provide 8-10 times higher IOPS than Standard HDD. 
 
+## Local temporary storage
+
+Some Azure VM sizes include [local temporary storage](overview.md#local-temporary-storage), with some of the newer sizes using [Temporary local NVMe disks](enable-nvme-temp-faqs.yml). Local temporary disks are different from Ephemeral OS disks. 
+
+Local temporary storage, also known as local ephemeral storage, are additional disks provisioned directly as local storage to an Azure virtual machine host, rather than on remote Azure Storage. This type of storage is best suited for data that does not need to be retained permanently, such as caches, buffers, and temporary files. Local ephemeral storage is not backed up and is lost when the VM is deallocated or deleted. The ephemeral storage is recreated on startup.
+
+Azure VM sizes featuring a 'd' in their naming convention - such as the Da***d***sv6, Ea***d***sv6, and FXm***d***sv2 series - include dedicated local temporary disks.
+
+
 ## Next steps
 
 Create a VM with ephemeral OS disk using [Azure Portal/CLI/PowerShell/ARM template](ephemeral-os-disks-deploy.md).

articles/virtual-machines/ev3-esv3-series.md

@@ -5,8 +5,6 @@ ms.service: azure-virtual-machines
 ms.subservice: sizes
 ms.topic: concept-article
 ms.date: 12/19/2022
-author: andysports8
-ms.author: mattmcinnes
 # Customer intent: "As a cloud architect, I want to evaluate the Ev3 and Esv3-series virtual machines, so that I can choose the optimal VM sizes for deploying memory-intensive enterprise applications effectively."
 ---
 

articles/virtual-machines/includes/virtual-machines-n-series-linux-support.md

@@ -35,7 +35,7 @@ For the latest CUDA drivers and supported operating systems, visit the [NVIDIA](
 > [!NOTE]
 > [vGPU18](https://download.microsoft.com/download/f5fdb58d-8a8b-4894-9add-6b93a1456f58/NVIDIA-Linux-x86_64-570.133.20-grid-azure.run) is available for the NCasT4_v3-series.
 >
-> [vGPU18 (Windows)](https://download.microsoft.com/download/dcf4d002-3a53-469d-91af-04bddf57a9d7/573.76_grid_win10_win11_server2019_server2022_server2025_dch_64bit_international_azure_swl.exe) and [vGPU18 (Linux)](https://download.microsoft.com/download/0541e1a5-dff2-4b8c-a79c-96a7664b1d49/NVIDIA-Linux-x86_64-570.195.03-grid-azure.run) are now available for the NVadsA10_v5-series in **public regions only**. vGPU18 for the NVadsA10_v5-series is **not** supported in the Mooncake and Fairfax regions yet. We'll provide an update once vGPU18 becomes supported for the NVadsA10_v5-series in the Mooncake and Fairfax regions.
+> [vGPU18](https://download.microsoft.com/download/0541e1a5-dff2-4b8c-a79c-96a7664b1d49/NVIDIA-Linux-x86_64-570.195.03-grid-azure.run) is now available for the NVadsA10_v5-series in **public regions only**. vGPU18 for the NVadsA10_v5-series is **not** supported in the Mooncake and Fairfax regions yet. We'll provide an update once vGPU18 becomes supported for the NVadsA10_v5-series in the Mooncake and Fairfax regions.
 
 Microsoft redistributes NVIDIA GRID driver installers for NV and NVv3-series VMs used as virtual workstations or for virtual applications. Install only these GRID drivers on Azure NV VMs, only on the operating systems listed in the following table. These drivers include licensing for GRID Virtual GPU Software in Azure. You don't need to set up a NVIDIA vGPU software license server.
 

articles/virtual-machines/includes/virtual-machines-n-series-windows-support.md

@@ -29,7 +29,7 @@ NVIDIA Tesla (CUDA) drivers for all NC* and ND*-series VMs (optional for NV*-ser
 > [!NOTE]
 > [vGPU18](https://download.microsoft.com/download/5ccc0984-e1b5-494d-8211-43b19ece6b9b/572.83_grid_win10_win11_server2022_dch_64bit_international_azure_swl.exe) is available for the NCasT4_v3-series.
 >
-> [vGPU18 (Windows)](https://download.microsoft.com/download/dcf4d002-3a53-469d-91af-04bddf57a9d7/573.76_grid_win10_win11_server2019_server2022_server2025_dch_64bit_international_azure_swl.exe) and [vGPU18 (Linux)](https://download.microsoft.com/download/0541e1a5-dff2-4b8c-a79c-96a7664b1d49/NVIDIA-Linux-x86_64-570.195.03-grid-azure.run) are now available for the NVadsA10_v5-series in **public regions only**. vGPU18 for the NVadsA10_v5-series is **not** supported in the Mooncake and Fairfax regions yet. We'll provide an update once vGPU18 becomes supported for the NVadsA10_v5-series in the Mooncake and Fairfax regions.
+> [vGPU18](https://download.microsoft.com/download/dcf4d002-3a53-469d-91af-04bddf57a9d7/573.76_grid_win10_win11_server2019_server2022_server2025_dch_64bit_international_azure_swl.exe) is now available for the NVadsA10_v5-series in **public regions only**. vGPU18 for the NVadsA10_v5-series is **not** supported in the Mooncake and Fairfax regions yet. We'll provide an update once vGPU18 becomes supported for the NVadsA10_v5-series in the Mooncake and Fairfax regions.
 
 > [!Note]
 >For Azure NVads A10 v5 VMs we recommend customers to always be on the latest driver version. The latest NVIDIA major driver branch(n) is only backward compatbile with the previous major branch(n-1). For eg, vGPU 17.x is backward compatible with vGPU 16.x only. Any VMs still runnig n-2 or lower may see driver failures when the latest drive branch is rolled out to Azure hosts.