Skip to content

Commit d06d304

Browse files
authored
Merge pull request #5 from kerimhanif/patch-11
Update virtual-machine-operations.md
2 parents 1ff531b + 22a2e65 commit d06d304

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

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

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Azure Local can host various types of VMs including Arc-enabled servers, unmanag
2020

2121
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.
2222

23-
If IT admins manage Azure Local VMs using the same tools and scripts as those for on-premises VMs, this could result in synchronization issues between the Azure Local VMs and the portal.
23+
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.
2424

2525
> [!NOTE]
2626
> 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).
@@ -61,12 +61,19 @@ The supported operations can be performed via multiple interfaces.
6161

6262
### Using local tools
6363

64-
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.
64+
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.
65+
66+
> [!IMPORTANT]
67+
> These changes will not be reflected in the portal.
6568
6669
#### VM-level operations
6770

68-
- Change MAC address of network interface.
69-
- Enable/disable MAC address spoofing per network interface.
71+
- Rename a VM inside the guest operating system.
72+
- Rename a VM on local tools.
73+
- Change IP address of network adapter.
74+
- Enable/change VLAN ID per network adapter.
75+
- Change MAC address of network adapter.
76+
- Enable/disable MAC address spoofing per network adapter.
7077
- Processor compatibility mode configuration.
7178
- Processor Non-Uniform Memory Access (NUMA) topology configuration.
7279
- Processor VM reserve, limit, and weight.
@@ -107,11 +114,8 @@ The following VM operations aren't supported.
107114
> 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.
108115
109116
- Live migrate a VM from one cluster to another.
110-
- Rename a VM.
111117
- Checkpoint a VM (standard or production).
112-
- Change disk type (static/dynamic) of a VM.
113-
- Change IP address of network interface.
114-
- Enable/change VLAN ID per network interface.
118+
- Change the type of the disk (static/dynamic/VHD/VHDX).
115119

116120

117121
## Related content

0 commit comments

Comments
 (0)