Merge pull request #2717 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-02 23:00 UTC

Author: learn-build-service-prod[bot]

articles/virtual-machines/disks-hdd-os-retirement.md

@@ -6,7 +6,7 @@ ms.service: azure-disk-storage
 ms.topic: how-to
 ms.date: 09/08/2025
 ms.author: rogarana
-
+ai-usage: ai-assisted
 ---
 
 # Migrate your Standard HDD OS disks by September 08, 2028
@@ -27,13 +27,15 @@ This retirement is only for the ability to use Standard HDD disks as OS disks. N
 
 ## What actions should I take?
 
+Stop creating new virtual machines with Standard HDD OS disks. Use Standard SSD or Premium SSD for new OS disks instead.
+
 To start planning a migration to either Standard SSD or Premium SSD OS disks, first, make a list of all affected OS disks and VMs.
 
 If you have multiple subscriptions, use the [Disk Storage Center](https://portal.azure.com/#view/Microsoft_Azure_StorageHub/StorageHub.MenuView/~/DisksBrowse) to create a list. Add two filters, one for **Storage type** which should be equal to **Standard HDD LRS** and one for **OS type** which should equal to **Linux and Windows**. This produces a list of all Standard HDD OS disks across all your subscriptions. The **Owner** column is the name of the virtual machine that uses the listed Standard HDD OS disks.
 
 The Disk Storage Center still works for individual subscriptions. But, if you prefer, you can use the Azure CLI or the Azure PowerShell module to get the same list for an individual subscription. For the Azure PowerShell module, use `Get-AzDisk | Where-Object { $_.Sku.Name -eq "Standard_LRS" -and $_.OsType }` and for the Azure CLI, use `az disk list --query "[?sku.name=='Standard_LRS' && osType!=null]" --output table`.
 
-Once you have a list of Standard HDD OS disks, [convert your Standard HDD OS disks](disks-convert-types.md#change-the-type-of-an-individual-managed-disk) to either Standard SSD or Premium SSD disks.
+Once you have a list of Standard HDD OS disks, [convert your Standard HDD OS disks](disks-convert-types.md#change-the-type-of-an-individual-managed-disk) to either Standard SSD or Premium SSD disks. Review [Azure Disk Storage billing guidance](disks-understand-billing.md) to choose the most cost-effective disk type for your workloads.
 
 For technical questions and issues, contact support.
 

articles/virtual-machines/disks-types.md

@@ -35,7 +35,7 @@ The following table provides a comparison of the five disk types to help you dec
 | **Max disk size** | 65,536 GiB | 65,536 GiB |32,767 GiB | 32,767 GiB | 32,767 GiB |
 | **Max throughput** | 10,000 MB/s | 1,200 MB/s | 900 MB/s | 750 MB/s | 500 MB/s |
 | **Max IOPS** | 400,000 | 80,000 | 20,000 | 6,000 | 2,000, 3,000* |
-| **Usable as OS Disk?** | No | No | Yes | Yes | Yes |
+| **Usable as OS Disk?** | No | No | Yes | Yes | [Yes (retiring Sept 8, 2028)](disks-hdd-os-retirement.md) |
 
 \* Only applies to disks with performance plus enabled.
 
@@ -55,7 +55,7 @@ Ultra Disks must be used as data disks and can only be created as empty disks. W
 
 Ultra Disk sizes range from 4 GiB up to 64 TiB, in 1 GiB increments. Ultra Disk capacity works like Premium SSD v2 disks and you're billed on a per GiB ratio.
 
-Ultra Disks offer up to 100 TiB per region per subscription by default and Ultra Disks support higher capacity by request. To request an increase in capacity, request a quota increase or contact Azure Support.
+By default, for each individual region, you can deploy a total of 100 TiB of capacity as Ultra Disks per subscription. If you need more than 100 TiB of Ultra Disk capacity per region per subscription, request a quota increase or contact Azure Support.
 
 The following table provides an example of performance caps an Ultra Disk has depending on the size you set for the disk.
 

articles/virtual-machines/extensions/agent-linux-fips.md

@@ -36,12 +36,11 @@ For more information, see [What are the Federal Information Processing Standards
 | MICROSOFT.CPLAT.CORE.LINUXPATCHEXTENSION | Commercial,<br>Government |
 | MICROSOFT.CPLAT.CORE.RUNCOMMANDLINUX | Commercial |
 | MICROSOFT.CPLAT.CORE.VMAPPLICATIONMANAGERLINUX | Commercial |
-| MICROSOFT.CPLAT.PROXYAGENT.PROXYAGENTLINUX | Commercial |
-| MICROSOFT.CPLAT.PROXYAGENT.PROXYAGENTLINUXARM64 | Commercial |
-| MICROSOFT.CPLAT.PROXYAGENT.PROXYAGENTWINDOWS | Commercial |
+| MICROSOFT.CPLAT.PROXYAGENT.PROXYAGENTLINUX | Commercial,<br>Government |
+| MICROSOFT.CPLAT.PROXYAGENT.PROXYAGENTLINUXARM64 | Commercial,<br>Government |
 | MICROSOFT.GUESTCONFIGURATION.CONFIGURATIONFORLINUX | Commercial |
 | MICROSOFT.MANAGEDSERVICES.APPLICATIONHEALTHLINUX | Commercial,<br>Government |
-| MICROSOFT.OSTCEXTENSIONS.VMACCESSFORLINUX | Commercial |
+| MICROSOFT.OSTCEXTENSIONS.VMACCESSFORLINUX | Commercial,<br>Government |
 
 ## Prerequisites
 
@@ -64,7 +63,7 @@ To view the latest supported regions, use the Linux VM Guest [v2.14.0.1](https:/
 
 | Cloud | Region |
 |:-----|:-----|
-| Commercial | Australia Central, Australia Central 2, Australia East, Australia Southeast, Austria East, Brazil South, Brazil Southeast, Canada Central, Canada East, Central India, Denmark East, East Asia, France Central, France South, Germany North, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia South, Malaysia West, Mexico Central, New Zealand North, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US 2, South India, Southeast US, Southeast US 5, Spain Central, Sweden Central, Sweden South, Switzerland North, Switzerland West, Taiwan North, Taiwan Northwest, UAE Central, UAE North, UK West, West India, West US 2, West US 3 |
+| Commercial | All regions |
 | USGov | All regions |
 | Air-Gap | All regions |
 

articles/virtual-machines/faq-for-disks.yml

@@ -77,7 +77,7 @@ sections:
       - question: |
           Are unmanaged disks still supported?
         answer: |
-          Yes, but they'll be [retired by September 30, 2025](unmanaged-disks-deprecation.md), and as of November 18, 2022, new customer subscriptions aren't eligible to create unmanaged disks. We recommend that you use managed disks for new workloads and migrate your current workloads to managed disks.
+          Yes, but they'll be retired on [March 31, 2026](unmanaged-disks-deprecation.md) (extended from September 30, 2025). As of November 18, 2022, new customer subscriptions aren't eligible to create unmanaged disks. Page blobs aren't affected by this change. Plan and complete migration of any VMs using unmanaged disks to managed disks before March 31, 2026. See [pricing](https://azure.microsoft.com/pricing/details/managed-disks/) and migration guidance for [Windows](windows/convert-unmanaged-to-managed-disks.md) and [Linux](linux/convert-unmanaged-to-managed-disks.md) VMs, or refer to the [migration overview](windows/migrate-to-managed-disks.md). You should use managed disks for new workloads and migrate your current workloads to managed disks.
 
       - question: |
           Can I colocate unmanaged and managed disks on the same VM?

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

@@ -37,9 +37,9 @@ For the latest CUDA drivers and supported operating systems, visit the [NVIDIA](
 >
 > [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.
+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 an NVIDIA vGPU software license server.
 
-The GRID drivers redistributed by Azure don't work on most non-NV series VMs like NC, NCv2, NCv3, ND, and NDv2-series VMs but works on NCasT4v3 series.
+The GRID drivers redistributed by Azure don't work on most non-NV series VMs, like NC, NCv2, NCv3, ND, and NDv2-series VMs, but they work on NCasT4v3 series.
 
 For more information on the specific vGPU and driver branch versions, visit the [NVIDIA](https://docs.nvidia.com/grid/) website.
 
@@ -48,11 +48,11 @@ For more information on the specific vGPU and driver branch versions, visit the
 |Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS<br/><br/>Red Hat Enterprise Linux 8.6, 8.8, 8.9, 8.10, 9.0, 9.2, 9.3, 9.4, 9.5<br/><br/>SUSE Linux Enterprise Server 15 SP2, 12 SP2,12 SP5<br/><br/>Rocky Linux 8.4| NVIDIA vGPU 18.5, driver branch [R570](https://download.microsoft.com/download/0541e1a5-dff2-4b8c-a79c-96a7664b1d49/NVIDIA-Linux-x86_64-570.195.03-grid-azure.run) <br/><br/> NVIDIA vGPU 18.5, driver branch [R570](https://download.microsoft.com/download/0541e1a5-dff2-4b8c-a79c-96a7664b1d49/NVIDIA-Linux-x86_64-570.195.03-grid-azure.run)
 
 > [!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.
+>For Azure NVads A10 v5 VMs, we recommend that you use the latest driver version. The latest NVIDIA major driver branch (n) is only backward compatibile with the previous major branch (n-1). For example, vGPU 17.x is backward compatible with vGPU 16.x only. Driver failures might occur on any VMs still running n-2 or lower when the latest drive branch is rolled out to Azure hosts.
 >>
->NVs_v3 VMs only support **vGPU 16 or lower** driver version.
+>NVs_v3 VMs only support **vGPU 16 or lower** driver versions.
 >>
-> GRID Driver 17.3 currently supports only NCasT4_v3 series of VMs. To use this driver, [download and install GRID Driver 17.3 manually](https://download.microsoft.com/download/7/e/c/7ec792c9-3654-4f78-b1a0-41a48e10ca6d/NVIDIA-Linux-x86_64-550.127.05-grid-azure.run) . 
+> GRID Driver 17.3 currently supports only the NCasT4_v3 series of VMs. To use this driver, [download and install GRID Driver 17.3 manually](https://download.microsoft.com/download/7/e/c/7ec792c9-3654-4f78-b1a0-41a48e10ca6d/NVIDIA-Linux-x86_64-550.127.05-grid-azure.run). 
 >>
 > GRID drivers are having issues with installation on Azure kernel 6.11. To unblock, downgrade the kernel to version 6.8. For more information, see [Known Issues](/azure/virtual-machines/extensions/hpccompute-gpu-linux#known-issues).