Merge pull request #2448 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-16 22:00 UTC

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

articles/virtual-machine-scale-sets/instance-mix-create.md

@@ -11,14 +11,14 @@ ms.reviewer: jushiman
 ---
 
 # Create a scale set using instance mix
-This article shows how to create a Virtual Machine Scale Set (VMSS) that uses instance mix, a way to specify multiple virtual machine (VM) sizes for a single scale set and control how Azure chooses sizes at provisioning time via an allocation strategy.
+This article shows how to create a Virtual Machine Scale Set (VMSS) with instance mix. Instance mix lets you specify multiple virtual machine (VM) sizes for a single scale set and control how Azure chooses sizes at provisioning time using an allocation strategy.
 
 ## Before you begin
 
 Confirm these prerequisites before you create an instance mix enabled scale set:
 
 - You intend to deploy a scale set that uses Flexible orchestration mode.
-- Consistent VM characteristics across selected sizes: same CPU architecture (x64 or Arm64), compatible disk interface (SCSI vs. NVMe), and compatible security profile.
+- Consistent VM characteristics across selected sizes: same CPU architecture (x64 or Arm64), compatible disk interface (SCSI or NVMe), and compatible security profile.
 - Sufficient quota for each VM size in the target subscription and region.
 - Choose a region that supports the VM sizes you want to include.
 - (CLI users) Azure CLI 2.66.0 or later is recommended. For PowerShell, use the latest `Az.Compute` module.
@@ -34,7 +34,7 @@ Confirm these prerequisites before you create an instance mix enabled scale set:
 6. In the **Size** section, click **Select up to 5 sizes** and the **Select a VM size** page appears.
 7. Use the size picker to select up to five VM sizes. Once you select your VM sizes, click the **Select** button at the bottom of the page to return to the scale set Basics tab.
 8. In the **Allocation strategy** field, select your allocation strategy.
-9. Using the `Prioritized (preview)` allocation strategy, the **Rank size** section appears below the Allocation strategy section. Clicking on the bottom **Rank priority** brings up the prioritization blade, where you can adjust the priority of your VM sizes.
+9. If you use the `Prioritized (preview)` allocation strategy, the **Rank size** section appears below the Allocation strategy section. Select **Rank priority** to open the prioritization blade, where you can adjust the priority of your VM sizes.
 10. You can specify other properties in subsequent tabs, or you can go to **Review + create** and select the **Create** button at the bottom of the page to start your instance mix scale set deployment.
 
 ### [Azure CLI](#tab/cli-1)
@@ -48,7 +48,9 @@ az vmss create \
   --resource-group {myResourceGroup} \
   --image ubuntu2204 \
   --vm-sku Mix \
-  --skuprofile-vmsizes Standard_DS1_v2 Standard_D2s_v4
+  --skuprofile-vmsizes Standard_D2s_v5 Standard_D2as_v5 \
+  --authentication-type ssh \
+  --generate-ssh-keys
 ```
 
 To specify the allocation strategy, use the `--skuprofile-allocation-strategy` parameter, like the following command:
@@ -58,8 +60,10 @@ az vmss create \
   --resource-group {myResourceGroup} \
   --image ubuntu2204 \
   --vm-sku Mix \
-  --skuprofile-vmsizes Standard_DS1_v2 Standard_D2s_v4 \
-  --skuprofile-allocation-strategy CapacityOptimized
+  --skuprofile-vmsizes Standard_D2s_v5 Standard_D2as_v5 \
+  --skuprofile-allocation-strategy CapacityOptimized \
+  --authentication-type ssh \
+  --generate-ssh-keys
 ```
 
 ### [Azure PowerShell](#tab/powershell-1)
@@ -156,7 +160,7 @@ Tips for REST deployments:
 
 - Ensure `sku.name` is set to `"Mix"` and that `sku.tier` isn't set (or is `null`).
 - The `rank` property is only required for the `Prioritized` strategy. Ranks with lower numbers are higher priority.
-- Always validate the template against the target subscription and region to confirm VM size availability and quota before PUT.
+- To confirm VM size availability and quota before deployment, validate the template against the target subscription and region.
 
 ---
 

articles/virtual-machine-scale-sets/instance-mix-update.md

@@ -17,12 +17,12 @@ This article explains how to update the instance mix settings on a scale set, in
 The instance mix settings can be updated on your scale set via CLI, PowerShell, and REST API. You can change either the virtual machine (VM) sizes or the allocation strategy, or both, in a single call.
 
 > [!NOTE]
-> When you change the allocation strategy, the new strategy takes effect only after the scale set scales in or out. Existing VMs are not affected until a scaling action occurs.
+> When you change the allocation strategy, the new strategy takes effect only after the scale set scales in or out. Existing VMs aren't affected until a scaling action occurs.
 
-When changing from `Prioritized (preview)` to another allocation strategy, you must first nullify the priority ranks associated with the VM sizes. This will be covered in more detail in the supporting code snippets. 
+When changing from `Prioritized (preview)` to another allocation strategy, you must first nullify the priority ranks associated with the VM sizes. 
 
 ### [Azure CLI](#tab/cli-1)
-Ensure you are using Azure CLI version `2.66.0` or later.
+Ensure you're using Azure CLI version `2.66.0` or later.
 
 #### Change the allocation strategy
 To update the allocation strategy, for example, to `CapacityOptimized`:
@@ -37,6 +37,9 @@ az vmss update \
 #### Change the VM sizes
 To update the VM sizes in the `skuProfile`, for example, to Standard_D2as_v4, Standard_D2as_v5, and Standard_D2s_v5:
 
+> [!NOTE]
+> When you update VM sizes, you must specify the complete list of sizes you want in the scale set. This operation replaces the entire list, not just adds or removes individual sizes.
+
 ```azurecli-interactive
 az vmss update \
   --resource-group {resourceGroupName} \
@@ -138,7 +141,7 @@ To update only the VM sizes:
 ---
 
 ## Enable instance mix on an existing scale set
-To enable instance mix on a scale set that does not already use it, specify the `skuProfile` properties. You must set:
+To enable instance mix on a scale set that doesn't already use it, specify the `skuProfile` properties. You must set:
 - `sku.name` to `"Mix"`
 - `sku.tier` to `null`
 - At least one value in `vmSizes` under `skuProfile`
@@ -155,7 +158,7 @@ az vmss update \
   --resource-group {resourceGroupName} \
   --set sku.name=Mix sku.tier=null \
   --skuprofile-vmsizes Standard_D2as_v4 Standard_D2s_v5 Standard_D2as_v5 \
-  --sku-allocat-strat capacityOptimized
+  --set skuProfile.allocationStrategy=capacityOptimized
 ```
 
 ### [REST API](#tab/arm-2)
@@ -188,5 +191,33 @@ In the request body, set `sku.name` to `"Mix"` and include the `skuProfile` with
 
 ---
 
+## Common update scenarios
+
+### Remove a specific VM size
+
+To remove a specific VM size from the instance mix configuration, specify the complete list of VM sizes you want to keep, excluding the size you want to remove.
+
+**Example**: Remove `Standard_D2as_v4` from a scale set that has `Standard_D2as_v4`, `Standard_D2s_v4`, `Standard_D2as_v5`, and `Standard_D2s_v5`:
+
+```azurecli-interactive
+az vmss update \
+  --resource-group {resourceGroupName} \
+  --name {scaleSetName} \
+  --skuprofile-vmsizes Standard_D2s_v4 Standard_D2as_v5 Standard_D2s_v5
+```
+
+### Add a specific VM size
+
+To add a new VM size to the instance mix configuration, specify the complete list of VM sizes including both existing and new sizes.
+
+**Example**: Add `Standard_D4s_v5` to a scale set that currently has `Standard_D2s_v4`, `Standard_D2as_v5`, and `Standard_D2s_v5`:
+
+```azurecli-interactive
+az vmss update \
+  --resource-group {resourceGroupName} \
+  --name {scaleSetName} \
+  --skuprofile-vmsizes Standard_D2s_v4 Standard_D2as_v5 Standard_D2s_v5 Standard_D4s_v5
+```
+
 ## Next steps
 Learn how to [troubleshoot](instance-mix-faq-troubleshooting.md) your instance mix-enabled scale set.

articles/virtual-machine-scale-sets/instance-mix-view.md

@@ -35,6 +35,21 @@ To display all properties in the `skuProfile`, run:
 az vmss show --resource-group <resourceGroupName> --name <scaleSetName> --query "skuProfile"
 ```
 
+**Example output:**
+```json
+{
+  "allocationStrategy": "CapacityOptimized",
+  "vmSizes": [
+    {
+      "name": "Standard_D4s_v5"
+    },
+    {
+      "name": "Standard_D4as_v5"
+    }
+  ]
+}
+```
+
 #### View VM sizes
 To display only the VM sizes, run:
 ```azurecli-interactive

articles/virtual-machines/constrained-vcpu.md

@@ -5,7 +5,7 @@ author: mattmcinnes
 ms.service: azure-virtual-machines
 ms.subservice: sizes
 ms.topic: concept-article
-ms.date: 03/18/2025
+ms.date: 10/16/2025
 ms.author: mattmcinnes
 ms.reviewer: mimckitt, archatc
 # Customer intent: "As a database administrator, I want to select virtual machine sizes with constrained vCPU counts, so that I can optimize licensing costs while maintaining necessary performance for my database workloads."
@@ -298,6 +298,43 @@ At this time, the VM pricing, remains the same as the original size. For more in
 | Standard_DS14-8_v2      | 8    | DS14_v2    |
 | Standard_DS14-4_v2      | 4    | DS14_v2    |
 
+
+#### [H-family sizes](#tab/family-H)
+
+| Size name               | Active vCPUs | Base size |
+|-------------------------|------|------------|
+| Standard_HB368rs_v5     | 368  | HB368rs_v5 | 
+| Standard_HB368_336rsv5  | 336  | HB368rs_v5 |
+| Standard_HB368_288rsv5  | 288  | HB368rs_v5 |
+| Standard_HB368-240rs_v5 | 240  | HB368rs_v5 |
+| Standard_HB368-192rs_v5 | 192  | HB368rs_v5 |
+| Standard_HB368-144rs_v5 | 144  | HB368rs_v5 |
+| Standard_HB368-96rs_v5  | 96   | HB368rs_v5 |
+| Standard_HB368-48rs_v5  | 48   | HB368rs_v5 |
+| Standard_HB176rs_v4     | 176  | HB176rs_v4 | 
+| Standard_HB176-144rs_v4 | 144  | HB176rs_v4 | 
+| Standard_HB176-96rs_v4  | 96   | HB176rs_v4 | 
+| Standard_HB176-48rs_v4  | 48   | HB176rs_v4 | 
+| Standard_HB176-24rs_v4  | 24   | HB176rs_v4 | 
+| Standard_HX176rs        | 176  | HX176rs    |
+| Standard_HX176-144rs    | 144  | HX176rs    |
+| Standard_HX176-96rs     | 96   | HX176rs    |
+| Standard_HX176-48rs     | 48   | HX176rs    |
+| Standard_HX176-24rs     | 24   | HX176rs    |
+| Standard_HB120rs_v3     | 120  | HB120rs_v3 |
+| Standard_HB120-96rs_v3  | 96   | HB120rs_v3 |
+| Standard_HB120-64rs_v3  | 64   | HB120rs_v3 |
+| Standard_HB120-32rs_v3  | 32   | HB120rs_v3 |
+| Standard_HB120-16rs_v3  | 16   | HB120rs_v3 |
+| Standard_HB120rs_v2     | 120  | HB120rs_v2 |
+| Standard_HB120-96rs_v2  | 96   | HB120rs_v2 |
+| Standard_HB120-64rs_v2  | 64   | HB120rs_v2 |
+| Standard_HB120-32rs_v2  | 32   | HB120rs_v2 |
+| Standard_HB120-16rs_v2  | 16   | HB120rs_v2 |
+| Standard_HC44rs         | 44   | HC44rs     | 
+| Standard_HC44-16rs      | 16   | HC44rs     | 
+| Standard_HC44-32rs      | 32   | HC44rs     |
+
 ---
 
 ## Other standard sizes

articles/virtual-machines/linux/azure-n-series-amd-gpu-driver-linux-installation-guide.md

@@ -109,8 +109,8 @@ sudo apt update
 sudo apt install "linux-headers-$(uname -r)" "linux-modules-extra-$(uname -r)"
 sudo apt install python3-setuptools python3-wheel
 sudo usermod -a -G render,video $LOGNAME
-wget https://repo.radeon.com/amdgpu-install/6.4.3/ubuntu/jammy/amdgpu-install_6.4.60403-1_all.deb
-sudo apt install ./amdgpu-install_6.4.60403-1_all.deb
+wget https://repo.radeon.com/amdgpu-install/7.0.1/ubuntu/jammy/amdgpu-install_7.0.1.70001-1_all.deb
+sudo apt install ./amdgpu-install_7.0.1.70001-1_all.deb
 sudo apt update
 sudo apt install amdgpu-dkms rocm
 ```