Merge pull request #18495 from alkohli/ki06

Add KI to 2506

Author: prmerger-automator[bot]

azure-local/known-issues.md

@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
 description: Read about the known issues and fixed issues in Azure Local.
 author: alkohli
 ms.topic: conceptual
-ms.date: 07/18/2025
+ms.date: 07/21/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -46,6 +46,7 @@ The following table lists the fixed issues in this release:
 |---------|---------|---------|
 | Update <!--33470082--> |  Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` |  |
 | Upgrade <!--33417006-->| The upgrade banner is currently available for users using the Azure Government cloud. However, the environment checker fails, suggesting that Azure Government clouds are not supported. | |
+|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. |  |
 
 
 ## Known issues
@@ -134,6 +135,7 @@ The following table lists the known issues in this release:
 | Update <!--33470082--> |  Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/SolutionUpdate-UpdateFOD.md). |
 | Deployment <!--33471589--> |  After Azure portal deployment, SConfig network settings shows the error: `Set-SCfNetworksetting : Cannot bind argument to parameter 'Value' because it is null.` | There's no known workaround in this release. |
 | Update <!--33448368--> |  Cluster-Aware Updating runs might fail with the error:<br>`Type 'SBEPartnerConfirmCauDone' of Role 'SBE' raised an exception:<br>SBE_MsftCIOnlyCommon_CommonForTesting_4.2.2504.16: ErrorID: SBE-CAU-RUNNING-AFTER-DONE -- CAU run is still in progress when it should be done. See https://aka.ms/AzureLocal/SBE/CauHelp for help. Review full Get-CauRun output it identify if it is progressing or stuck. Wait for it to complete if progressing.` | Wait for CAU run to complete (wait for `Get-CauRun` to report `RunNotInProgress`) and resume the update. |
+|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#resource-deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
 
 ## Known issues from previous releases
 

azure-local/manage/troubleshoot-arc-enabled-vms.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Local Virtual Machines enabled by Azure Arc
 description: Learn how to troubleshoot issues you experience with Azure Local Virtual Machines (VMs).
 author: alkohli
 ms.topic: how-to
-ms.date: 06/16/2025
+ms.date: 07/21/2025
 ms.author: alkohli
 ms.reviewer: vlakshmanan
 ms.service: azure-local
@@ -15,7 +15,6 @@ ms.service: azure-local
 
 This article describes how to collect logs and troubleshoot issues with Azure Local Virtual Machines (VMs) enabled by Azure Arc. It also lists the current limitations and known issues with Azure Local VM management, along with recommended resolutions.
 
-
 ## Property isn't supported for this operation
 
 **Error:**
@@ -187,6 +186,63 @@ To resolve this issue, follow these steps:
 
 1. Restart the VM. After the restart, the warning message should no longer appear.
 
+## Resource deployment failure due to insufficient disk space on the first storage path
+
+**Error:**
+
+`The system failed to create <Azure resource name>: There is not enough space on the disk.`
+
+**Cause:**
+
+If no storage path is specified during deployment, resources are automatically placed on the first storage path, even when additional storage paths are available on the cluster. This can lead to insufficient disk space on the first storage path, even when other storage paths still have available capacity.
+
+**Resolution:**
+
+When creating a VM, data disk, or image, choose a storage path manually.
+
+# [Azure portal](#tab/azure-portal)
+
+In the Azure portal, when creating a VM, attaching data disks, or creating an image, select the **Choose manually** option for the storage path. Then, select a storage path from the available list to avoid automatic placement on the first storage path.
+
+# [CLI](#tab/cli)
+
+To specify a storage path when creating a VM, data disk, or image, use the `--storage-path-id` parameter with the `az stack-hci-vm create`, `az stack-hci-vm disk create`, or `az stack-hci-vm image create` command.
+
+# [ARM template](#tab/arm-template)
+
+To define a storage path for a VM configuration, add `vmConfigStoragePathId` to the `storageProfile` section of the VM resource:
+
+```json
+"storageProfile": {
+ "vmConfigStoragePathId": "Insert ARM ID of specified storage path"
+}
+```
+
+If using an ARM template that creates multiple VMs in one deployment:
+
+1. Define a parameter for the storage path IDs:
+
+    ```json
+    "parameters": {
+     "storagePathIds": {
+       "type": "array",
+       "metadata": {
+         "description": "List of storage path resource IDs to cycle through for VM placement."
+       }
+     }
+    }
+    ```
+
+1. Add `vmConfigStoragePathId` to the `storageProfile`section of the VM resource:
+
+    ```json
+    "storageProfile": {
+     "vmConfigStoragePathId": "[parameters('storagePathIds')[mod(copyIndex(), length(parameters('storagePathIds')))]]"
+    }
+    ```
+
+---
+
 ## Next steps
 
 - [Azure Local VM management FAQs](./azure-arc-vms-faq.yml)