Merge pull request #3259 from MicrosoftDocs/main638584738650658595sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

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

azure-stack/hci/known-issues-2405-2.md

@@ -40,6 +40,7 @@ Here are the fixed issues in this release:
 | Updates <!--28351655-->|In this release, an issue that caused an inability to view or start new updates due to the update service crashing on servers in a bad state, was fixed.    ||
 | Updates <!--28351665-->|In this release, the update service was improved to prevent flooding of actions on the cluster.   ||
 | Updates <!--28509688-->|In this release, a health check was added to prevent updates when adding or removing servers fails.   ||
+| Arc VM management <!--10325529-->|In earlier releases, any power state change operation of a VM such as start stop, save, and pause, would initially return the state of the VM as running and eventually display the correct state after a refresh 30+ seconds later. In this release, the power state change operation only returns after the VM state is changed to the expected one.   ||
 
 ## Known issues in this release
 

azure-stack/hci/whats-new.md

@@ -27,13 +27,20 @@ The 2405 release train includes the following releases:
 
 This is primarily a bug fix release with a few improvements.
 
+- Arc VM management improvements: Starting this release, followiing improvements were made to the Arc VM management experience:
+
+  - You can now view and delete VM network interfaces from the Azure portal.
+  - You can view **Connected devices** for logical networks. In the Azure portal, you can go to the logical network and then go to **Settings > Connected devices** to view the connected devices.
+  - Deletion of logical networks is blocked if connected devices are present. When you try to delete a logical network from the Azure portal that has connected devices, you'll see a warning message: *Cannot delete logical network because it is currently in use*. Delete all the resources under **Connected Devices** setting before you delete the logical network.
+  - From this release onwards, a new URL needs to be added to the allowlist for `stack-hci-vm` Azure CLI installation. The URL has changed from: `https://hciarcvmsstorage.blob.core.windows.net/cli-extension/stack_hci_vm-{version}-py3-none-any.whl` to: `https://hciarcvmsstorage.z13.web.core.windows.net/cli-extensions/stack_hci_vm-{version}-py3-none-any.whl`. For more information, see [Azure Stack HCI firewall requirements](./concepts/firewall-requirements.md).
+  
 - **Update health checks**: Starting this release, a new health check was added and the update service was improved. Additionally, the update service now supports the ability to view or start new updates when the service crashes on servers. Also, multiple issues for health checks related to Azure Update Manager and Solution Builder Extension Update were fixed.
 
-    For more information, see [Fixed issues in 2405.2](./known-issues-2405-2.md#fixed-issues).
+  For more information, see [Fixed issues in 2405.2](./known-issues-2405-2.md#fixed-issues).
 
 - **Azure Stack HCI OEM license**: Starting this release, we are introducing the Azure Stack HCI OEM license designed for Azure Stack HCI hardware including the Azure Stack HCI Premier Solutions, Integrated systems, and Validated Nodes. This license remains valid for the lifetime of the hardware, covers up to 16 cores, and includes three essential services for your cloud infrastructure.
 
-    <!--For more information, see [Azure Stack HCI OEM license overview](../azure-stack-hci-oem-license.md) and [Azure Stack HCI OEM license and billing FAQ](../azure-stack-hci-license-billing.yml).-->
+  For more information, see [Azure Stack HCI OEM license overview](./azure-stack-hci-oem-license.md) and [Azure Stack HCI OEM license and billing FAQ](./azure-stack-hci-license-billing.yml).
 
 ## Features and improvements in 2405.1