Merge pull request #2658 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-21 23:00 UTC

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

articles/container-instances/container-instances-standby-pool-create.md

@@ -206,24 +206,28 @@ Create a standby pool and associate it with a container group profile using [az
 
 ```azurecli-interactive
 az standby-container-group-pool create \
-   --resource-group myResourceGroup \
-   --location WestCentralUS \
-   --name myStandbyPool \
-   --max-ready-capacity 20 \
-   --refill-policy always \
-   --container-profile-id "/subscriptions/{subscriptionId}/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroupProfiles/mycontainergroupprofile"
+  --resource-group myResourceGroup \
+  --location westcentralus \
+  --name myStandbyPool \
+  --max-ready-capacity 20 \
+  --refill-policy always \
+  --container-group-profile-id "/subscriptions/{subscriptionId}/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroupProfiles/mycontainergroupprofile" \
+  --container-group-profile-revision 1
+
 ```
 ### [PowerShell](#tab/powershell)
 Create a standby pool and associate it with a container group profile using [New-AzStandbyContainerGroupPool](/powershell/module/az.standbypool/new-AzStandbyContainerGroupPool).
 
 ```azurepowershell-interactive
 New-AzStandbyContainerGroupPool `
-   -ResourceGroup myResourceGroup `
-   -Location "WestCentralUS" `
+   -ResourceGroupName myResourceGroup `
+   -Location "westcentralus" `
    -Name myStandbyPool `
    -MaxReadyCapacity 20 `
-   -RefillPolicy always `
-   -ContainerProfileId "/subscriptions/{subscriptionId}/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroupProfiles/mycontainergroupprofile"
+   -RefillPolicy "always" `
+   -ContainerGroupProfileId "/subscriptions/{subscriptionId}/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroupProfiles/mycontainergroupprofile" `
+   -ContainerGroupProfileRevision 1
+
 ```
 
 ### [ARM template](#tab/template)
@@ -236,42 +240,51 @@ Create a standby pool and associate it with a container group profile. Create a
     "contentVersion": "1.0.0.0",
     "parameters": {
         "location": {
-           "type": "string",
-           "defaultValue": "West Central US"    
+            "type": "string",
+            "defaultValue": "West Central US"
         },
         "name": {
-           "type": "string",
-           "defaultValue": "myStandbyPool"
+            "type": "string",
+            "defaultValue": "myStandbyPool"
+        },
+        "maxReadyCapacity": {
+            "type": "int",
+            "defaultValue": 10
         },
-        "maxReadyCapacity" : {
-           "type": "int",
-           "defaultValue": 10
+        "refillPolicy": {
+            "type": "string",
+            "defaultValue": "always"
         },
-        "refillPolicy" : {
-           "type": "string",
-           "defaultValue": "always"
+        "containerGroupProfileId": {
+            "type": "string",
+            "defaultValue": "/subscriptions/{SubscriptionID}/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroupProfiles/mycontainergroupprofile"
         },
-        "containerGroupProfile" : {
-           "type": "string",
-           "defaultValue": "/subscriptions/{SubscriptionID}/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroupProfiles/mycontainergroupprofile"
+        "containerGroupProfileRevision": {
+            "type": "int",
+            "defaultValue": 1
         }
     },
-    "resources": [ 
+    "resources": [
         {
             "type": "Microsoft.StandbyPool/standbyContainerGroupPools",
             "apiVersion": "2025-03-01",
             "name": "[parameters('name')]",
             "location": "[parameters('location')]",
             "properties": {
-               "elasticityProfile": {
-                   "maxReadyCapacity": "[parameters('maxReadyCapacity')]",
-                   "refillPolicy": "[parameters('refillPolicy')]"
-               },
-               "containerGroupProfile": "[parameters('containerGroupProfile')]"
+                "elasticityProfile": {
+                    "maxReadyCapacity": "[parameters('maxReadyCapacity')]",
+                    "refillPolicy": "[parameters('refillPolicy')]"
+                },
+                "containerGroupProperties": {
+                    "containerGroupProfile": {
+                        "id": "[parameters('containerGroupProfileId')]",
+                        "revision": "[parameters('containerGroupProfileRevision')]"
+                    }
+                }
             }
         }
     ]
-   }
+}
 
 ```
 

articles/virtual-machines/TOC.yml

@@ -538,6 +538,8 @@
          href: ./sizes/gpu-accelerated/ncast4v3-series.md
        - name: NC_A100_v4 series
          href: ./sizes/gpu-accelerated/nca100v4-series.md
+       - name: NC_RTXPRO6000BSE_v6 series
+         href: ./sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-series.md
      - name: ND family
        items:
        - name: Overview

articles/virtual-machines/linux/run-command.md

@@ -114,7 +114,7 @@ You can use one of the [built-in roles](/azure/role-based-access-control/built-i
 
 ## Action Run Command Linux troubleshooting
 
-When troubleshooting action run command for Linux environments, refer to the *handler* log file typically located in the following directory: `/var/log/azure/run-command-handler/handler.log` for further details.
+When troubleshooting action run command for Linux environments, refer to the *handler* log file typically located in the following directory: `/var/log/azure/run-command/handler.log` for further details.
 
 ### Known issues
 The Linux action run command logs have a few notable differences compared to the action run command Windows logs:

articles/virtual-machines/sizes/gpu-accelerated/includes/nc-rtxpro6000-bse-v6-series-specs.md

@@ -0,0 +1,20 @@
+---
+title: NC_RTXPRO6000BSE_v6 series specs include
+description: Include file containing specifications of NC_RTXPRO6000BSE_v6-series VM sizes.
+author: mattmcinnes
+ms.topic: include
+ms.service: azure-virtual-machines
+ms.subservice: sizes
+ms.date: 11/21/2025
+ms.author: mattmcinnes
+ms.reviewer: mattmcinnes
+ms.custom: include file
+---
+| Part | Quantity <br><sup>Count Units | Specs <br><sup>SKU ID, Performance Units, etc.  |
+|---|---|---|
+| Processor      | 32 - 320 vCPUs       | Intel Xeon Granite Rapids-AP [x86-64]                   |
+| Memory         | 128 - 1280 GiB          |  High-speed DDR5  |
+| Local Storage  | 1 Disk         | 256 - 2048 GiB               |
+| Remote Storage | 16 Disks    |                   |
+| Network        | 6 - 8 NICs          | 25000 - 200000 Mbps              |
+| Accelerators   | 0.25 - 2              | Nvidia RTX PRO 6000 Blackwell Server Edition GPU (96GB)|

articles/virtual-machines/sizes/gpu-accelerated/includes/nc-rtxpro6000-bse-v6-series-summary.md

@@ -0,0 +1,22 @@
+---
+title: NC_RTXPRO6000BSE_v6-series summary include file
+description: Include file for NC_RTXPRO6000BSE_v6-series summary
+author: mattmcinnes
+ms.topic: include
+ms.service: azure-virtual-machines
+ms.subservice: sizes
+ms.date: 11/21/2025
+ms.author: mattmcinnes
+ms.reviewer: mattmcinnes
+ms.custom: include file
+---
+These NC RTX PRO 6000 BSE v6 VMs are powered by NVIDIA RTX PRO 6000 Blackwell Server Edition GPUs, each featuring 96 GB of ultra-fast GDDR7 memory and the latest Blackwell architecture to enable breakthrough performance in multimodal AI, physical AI, and high-fidelity graphics. The VM host is equipped with Intel Granite Rapids CPUs, providing all-core turbo frequency of up to 4.2 GHz to handle demanding pre- and post-processing steps efficiently. These VMs are ideal for converged AI and visual computing workloads, such as:
+
+- Real-time digital twin and NVIDIA Omniverse simulation.
+- LLM Inference and RAG (Retrieval-Augmented Generation) for models under 70B parameters.
+- High-fidelity 3D rendering, product design, and video streaming.
+- GPU-accelerated desktop virtualization (VDI) with NVIDIA RTX Virtual Workstation.
+- Scientific visualization and High-Performance Computing (HPC) using FP32.
+- Agentic AI application development and deployment.
+
+Sign up to Participate in [NCv6 Public Preview](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR9s7orOb3OJJnwABCNj_8JdUMzlLSzJFTTdRRE8yU0UxWFFYQlpYV1hDVy4u) !