Merge branch 'vmoob' of https://github.com/alkohli/azure-stack-docs-pr into 2oob

Author: alkohli

azure-local/TOC.yml

@@ -213,6 +213,8 @@ items:
       href: manage/azure-arc-vm-management-overview.md
     - name: Compare VM management capabilities
       href: concepts/compare-vm-management-capabilities.md
+    - name: Supported operations for Arc VMs
+      href: manage/virtual-machine-operations.md
     - name: Review prerequisites
       href: manage/azure-arc-vm-management-prerequisites.md
     - name: Assign RBAC role

azure-local/manage/virtual-machine-operations.md

@@ -0,0 +1,123 @@
+---
+title: Supported operations for Arc Virtual Machines on Azure Local 
+description: Learn the supported VM operations for Azure Arc VMs on Azure Local.
+author: alkohli
+ms.author: alkohli
+ms.topic: how-to
+ms.service: azure-local
+ms.date: 03/05/2025
+---
+
+# Supported operations for Azure Local virtual machines 
+
+[!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
+
+This article discusses the most common operations for Azure Local virtual machines (VMs) enabled by Azure Arc and identifies the operations that are supported, and the ones that you need to avoid to prevent complications.
+
+## Overview
+
+Azure Local can host various types of VMs including Arc-enabled servers, unmanaged VMs, and VMs enabled by Azure Arc. When comparing these options, the Azure Local VMs enabled by Azure Arc provide the highest level of management capabilities in Azure portal, second only to [native Azure VMs](/azure/azure-local/concepts/compare-vm-management-capabilities).
+
+While the architecture of Azure Local VMs is designed to be managed by the Azure control plane, these VMs can also be managed by on-premises local tools. These tools include System Center Virtual Machine Manager (SCVMM), Failover Cluster Manager, Hyper-V Manager, and Windows Admin Center. Many customers have used these tools for years to manage their on-premises VMs.
+
+If IT admins manage Azure Local VMs using the same tools and scripts as those for on-premises VMs, this will result in synchronization issues between the Azure Local VMs and the portal. Only the following operations when performed using local tools will update the state of the Azure Local VM in the portal: Changing the size of VM memory, vCPU count, change the power state status (Start/Stop VM) resulting from power cycle operation.
+
+> [!NOTE]
+> We recommend that you use the Azure portal or Azure CLI to manage Azure Local VMs. Use the local tools only if these operations are included in the list of [Supported operations for local tools](#using-local-tools).
+
+## Supported operations
+
+The supported operations can be performed via multiple interfaces.
+
+### Using Azure portal or Azure CLI
+
+> [!IMPORTANT]
+> Make sure to perform these VM operations only via the Azure portal or Azure CLI (and not via the local tools).
+
+- Restart.
+- Stop.
+- Delete.
+- Add network interface.
+- Delete network interface.
+- Enable and use Windows Admin Center (for read-only).
+- Add data diskM.
+- Delete data disk.
+- Change CPU cores.
+- Change memory.
+- Add extensions.
+- Delete extensions.
+- Enable guest management.
+- Connect via SSH.
+
+### Using Azure CLI
+
+> [!IMPORTANT]
+> Make sure to perform these operations only via the Azure CLI (and not via the local tools).
+
+- Pause VM.
+- Save VM state.
+- Attach GPU.
+- Detach GPU.
+
+### Using local tools
+
+The following VM operations are supported only using the local tools such as Windows Admin Center, Hyper-V Manager, Failover Cluster Manager, and SCVMM. These operations are performed either on the VM itself or on the cluster/node. 
+
+> [!IMPORTANT]
+> These changes will not be reflected in the portal. 
+
+#### VM-level operations
+
+- Rename a VM inside the guest operating system.
+- Rename a VM on local tools.
+- Change IP address of network adapter.
+- Enable/change VLAN ID per network adapter.
+- Change MAC address of network adapter.
+- Enable/disable MAC address spoofing per network adapter.
+- Processor compatibility mode configuration.
+- Processor Non-Uniform Memory Access (NUMA) topology configuration.
+- Processor VM reserve, limit, and weight.
+- Enable Quality of Service (QoS) management per disk.
+- Add a Small Computer System Interface (SCSI) controller and move an existing data disk to another SCSI controller.
+- Remove a SCSI controller.
+- Add/remove DVD drive.
+- Configure dynamic memory.
+- Change VM boot order.
+- Enable/disable integration services.
+- Change automatic start action.
+- Change automatic stop action.
+- Enable secure boot of Generation 2 VM.
+
+#### Cluster or node-level operations
+
+- Connect to VM.
+- Quick migrate a VM to another node in the same cluster.
+- Live migrate a VM to another node in the same cluster.
+- Change default location of VM files.
+- Change automatic balancing of VMs in the cluster.
+- Change the Hyper-V MAC address range on the node.
+
+#### Operations supported only via Network ATC PowerShell cmdlets
+
+The following VM operations are supported only using the Network ATC PowerShell cmdlets. For more information, see [Customize cluster network settings](./manage-network-atc.md#customize-cluster-network-settings).
+
+- Enable/disable single root input/output virtualization (SR-IOV) per network interface.
+- Configure the number of simultaneous live migrations of a cluster.
+- Configure the number of simultaneous storage live migrations of a cluster.
+- Add/remove/change order of host network for live migration of a cluster.
+
+## Unsupported VM operations
+
+The following VM operations aren't supported.
+
+> [!IMPORTANT]
+> These operations can't be performed using Azure portal, Azure CLI, or local tools. Performing these operations can lead to synchronization issues between the Azure Local VMs and the portal.
+
+- Live migrate a VM from one cluster to another.
+- Checkpoint a VM (standard or production).
+- Change the type of the disk (static/dynamic/VHD/VHDX).
+
+
+## Related content
+
+- [Manage Arc VMs](manage-arc-virtual-machines.md)