From e228f899a113089cd597deb241358c85248a6c24 Mon Sep 17 00:00:00 2001 From: Kerim Hanif <26774526+kerimhanif@users.noreply.github.com> Date: Wed, 15 Apr 2026 12:21:14 -0700 Subject: [PATCH 1/3] Edited Notes section: Changed the third bullet and added the forth bullet --- azure-local/manage/virtual-machine-operations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/azure-local/manage/virtual-machine-operations.md b/azure-local/manage/virtual-machine-operations.md index 923c1dd136..b6e6256d29 100644 --- a/azure-local/manage/virtual-machine-operations.md +++ b/azure-local/manage/virtual-machine-operations.md @@ -27,7 +27,8 @@ When IT admins manage Azure Local VMs by using the same local tools and scripts > > - We recommend that you use the Azure portal or the 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](#local-tools) later in this article. > - Though the supported operations for local tools don't affect the management of Azure Local VMs, the changes aren't reflected in the Azure portal. -> - Only the following operations update the state of an Azure Local VM in the portal, when you perform them by using local tools: change the power state (start or stop a VM) resulting from the power cycle operation. +> - When performed using local tools, only a VM power state change (start or stop) resulting from a power cycle operation updates the Azure Local VM state in the Azure portal. +> - Any tool, regardless of where its control plane resides, is considered a local tool if it executes commands locally (for example, the Windows Admin Center extension in the Azure portal). ## Supported VM operations From 59c760d7b7af41f342c869dfd1eb94e340a530ab Mon Sep 17 00:00:00 2001 From: Kerim Hanif <26774526+kerimhanif@users.noreply.github.com> Date: Mon, 4 May 2026 15:23:21 -0700 Subject: [PATCH 2/3] Update azure-local/manage/virtual-machine-operations.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- azure-local/manage/virtual-machine-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/azure-local/manage/virtual-machine-operations.md b/azure-local/manage/virtual-machine-operations.md index b6e6256d29..52a06ee4ac 100644 --- a/azure-local/manage/virtual-machine-operations.md +++ b/azure-local/manage/virtual-machine-operations.md @@ -27,7 +27,7 @@ When IT admins manage Azure Local VMs by using the same local tools and scripts > > - We recommend that you use the Azure portal or the 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](#local-tools) later in this article. > - Though the supported operations for local tools don't affect the management of Azure Local VMs, the changes aren't reflected in the Azure portal. -> - When performed using local tools, only a VM power state change (start or stop) resulting from a power cycle operation updates the Azure Local VM state in the Azure portal. +> - When performed using local tools, only a VM power state change (start or stop) updates the Azure Local VM state in the Azure portal. > - Any tool, regardless of where its control plane resides, is considered a local tool if it executes commands locally (for example, the Windows Admin Center extension in the Azure portal). ## Supported VM operations From 28c625ca815e0531d616c65a43d351a16e75be14 Mon Sep 17 00:00:00 2001 From: Kerim Hanif <26774526+kerimhanif@users.noreply.github.com> Date: Mon, 4 May 2026 15:23:37 -0700 Subject: [PATCH 3/3] Update azure-local/manage/virtual-machine-operations.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- azure-local/manage/virtual-machine-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/azure-local/manage/virtual-machine-operations.md b/azure-local/manage/virtual-machine-operations.md index 52a06ee4ac..1fbcf6b1b6 100644 --- a/azure-local/manage/virtual-machine-operations.md +++ b/azure-local/manage/virtual-machine-operations.md @@ -28,7 +28,7 @@ When IT admins manage Azure Local VMs by using the same local tools and scripts > - We recommend that you use the Azure portal or the 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](#local-tools) later in this article. > - Though the supported operations for local tools don't affect the management of Azure Local VMs, the changes aren't reflected in the Azure portal. > - When performed using local tools, only a VM power state change (start or stop) updates the Azure Local VM state in the Azure portal. -> - Any tool, regardless of where its control plane resides, is considered a local tool if it executes commands locally (for example, the Windows Admin Center extension in the Azure portal). +> - A tool is considered a local tool when the management action runs in a local execution context on or against the local host or cluster, rather than through the Azure control plane. For example, the Windows Admin Center extension can be surfaced in the Azure portal, but operations it executes locally are treated as local-tool operations. ## Supported VM operations