KI for 2506

Author: ManikaDhiman

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/02/2025
+ms.date: 07/18/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -68,6 +68,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-->| VMs and VHDs with no storage path specified during deployment are landing only on the first storage path of the cluster. | Create VMs and VHDs 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#vms-and-vhds-deployed-without-a-specified-storage-path-landing-only-on-the-first-storage-path-in-the-cluster). |
 
 ## 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/18/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.
 
+## VMs and VHDs deployed without a specified storage path landing only on the first storage path in the cluster
+
+**Error:**
+
+The system failed to create `[REDACTED]`: There is not enough space on the disk.
+
+**Cause:**
+
+This error can occur due to a known issue in Azure Local 2506 where VMs and VHDs with no storage path specified during deployment are landing only on the first storage path of the cluster. Over time, this can lead to that path becoming full, preventing new deployments and potentially causing existing VMs to enter a paused-critical state due to disk I/O failures.
+
+**Resolution:**
+
+When creating a VM or VHD, choose a storage path manually:
+
+# [Azure portal](#tab/azure-portal)
+
+When creating a VM in the Azure portal, select the **Choose manually** option for storage path and then select a storage path from the available list.
+
+When attaching data disks to the VM, select the **Choose manually** option for storage path allocation method and then select a storage path from the available list.
+
+# [CLI](#tab/cli)
+
+To specify a storage path when creating a VM or VHD, use the `--storage-path-id` parameter with the `az stack-hci-vm create` or `az stack-hci-vm disk 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)