edit pass: azure-local-vms

ShawnJackson · ShawnJackson · commit 20829c052e4f · 2025-05-21T19:30:58.000-05:00
diff --git a/azure-local/concepts/compare-vm-management-capabilities.md b/azure-local/concepts/compare-vm-management-capabilities.md
@@ -1,5 +1,5 @@
 ---
-title: Compare management capabilities of VMs on Azure Local
+title: Compare Management Capabilities of VMs on Azure Local
 description: Learn about the kinds of virtual machines (VMs) that can run on Azure Local and compare their management capabilities.
 ms.topic: conceptual
 author: alkohli
@@ -11,101 +11,103 @@ ms.date: 03/18/2025
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes the types of virtual machines (VMs) available on Azure Local and compares their management capabilities in Azure.
+This article describes the types of virtual machines (VMs) available on Azure Local. It also compares their management capabilities in Azure.
 
 ## Types of VMs on Azure Local
 
-Here are the different types of VMs that you can run on your Azure Local system:
+You can run these types of VMs on your Azure Local system:
 
-- **Azure Local VMs enabled by Azure Arc:** Windows and Linux VMs hosted outside of Azure, on your corporate network, running on Azure Local.
-  - Are created using [Azure Local VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal), registered to [Azure Arc resource bridge](/azure/azure-arc/resource-bridge/overview), and have the [Connected Machine agent](/azure/azure-arc/servers/agent-overview) installed.
+- **Azure Local VMs enabled by Azure Arc**: Windows and Linux VMs hosted outside Azure, on your corporate network, running on Azure Local. These types of VMs:
+  - Are created through the [Azure Local VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal), are registered to an [Azure Arc resource bridge](/azure/azure-arc/resource-bridge/overview), and have the [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview) installed.
   - Offer extensive management capabilities in the Azure portal, second only to native Azure VMs.
-  - Through Azure Arc resource bridge, Azure Local VMs provide lifecycle management capabilities like starting, stopping, changing VM memory/vCPU, and adding or removing data disk and network interfaces.
-  - Through the Connected Machine agent, Azure Local VMs leverage Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
+  - Through an Azure Arc resource bridge, provide life-cycle management capabilities like starting, stopping, changing VM memory/vCPU, and adding or removing data disk and network interfaces.
+  - Through the Azure Connected Machine agent, use Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
   - Can be managed through Azure.
 
-- **[Arc-enabled servers](/azure/azure-arc/servers/overview):** Windows and Linux physical servers and virtual machines hosted outside of Azure, on your corporate network, or on other cloud providers with the Connected Machine agent installed.
-  - Arc-enabled servers run on Azure Local as virtual machines.
-  - Lack the lifecycle management capabilities that Azure Local VMs offer.
-  - Through the Connected Machine agent, Arc-enabled servers leverage Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
+- [Azure Arc-enabled servers](/azure/azure-arc/servers/overview): Windows and Linux physical servers and VMs hosted outside Azure, on your corporate network, or on other cloud providers with the Azure Connected Machine agent installed. These types of VMs:
+  - Run on Azure Local as virtual machines.
+  - Lack the life-cycle management capabilities that Azure Local VMs offer.
+  - Through the Azure Connected Machine agent, use Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
   - Can be managed through Azure.
 
-- **Unmanaged VMs:** Windows and Linux VMs created and hosted outside of Azure, on your corporate network, running on Azure Local.
+- **Unmanaged VMs**: Windows and Linux VMs created and hosted outside Azure, on your corporate network, running on Azure Local. These types of VMs:
   - Aren't connected to Azure.
   - Can't be managed through Azure.
 
+## Comparison of provisioning and management methods
+
 The following table compares the provisioning and management methods for the various types of VMs running on Azure Local:
 
-| VM provisioning and management methods | Azure Local VMs enabled by Azure Arc | Arc-enabled servers | Unmanaged VMs |
+| VM provisioning and management methods | Azure Local VMs enabled by Azure Arc | Azure Arc-enabled servers | Unmanaged VMs |
 | :---- | :---- | :---- | :---- |
-| Provisioning method |  [Azure Local VMs provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Azure Local VMs using Azure CLI, Azure portal, or Azure Resource Manager (ARM) template. Using ARM templates, you can also automate VM provisioning in a secure cloud environment. <br><br> [Azure Migrate flow](../migrate/migration-azure-migrate-overview.md). Migrate existing VMware and Hyper-V VMs to Azure Local using the migration flow. | Connect these machines to Azure by [deploying the Connected Machine agent](/azure/azure-arc/servers/deployment-options) | On-premises provisioning flow. Use local tools like Failover Cluster Manager available in your on-premises environment, or use [Windows Admin Center](../manage/vm.md#create-a-new-vm), [System Center Virtual Machine Manager (SCVMM)](/system-center/vmm/provision-vms), or [PowerShell](../manage/vm-powershell.md#create-a-vm).|
+| Provisioning method |  [Azure Local VMs provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Azure Local VMs using Azure CLI, Azure portal, or Azure Resource Manager (ARM) template. Using ARM templates, you can also automate VM provisioning in a secure cloud environment. <br><br> [Azure Migrate flow](../migrate/migration-azure-migrate-overview.md). Migrate existing VMware and Hyper-V VMs to Azure Local using the migration flow. | Connect these machines to Azure by [deploying the Azure Connected Machine agent](/azure/azure-arc/servers/deployment-options) | On-premises provisioning flow. Use local tools like Failover Cluster Manager available in your on-premises environment, or use [Windows Admin Center](../manage/vm.md#create-a-new-vm), [System Center Virtual Machine Manager (SCVMM)](/system-center/vmm/provision-vms), or [PowerShell](../manage/vm-powershell.md#create-a-vm).|
 | Management method | [Via Azure](../manage/manage-arc-virtual-machines.md). | Via Azure. See [Management and monitoring for Azure Arc-enabled servers](/azure/cloud-adoption-framework/scenarios/hybrid/arc-enabled-servers/eslz-management-and-monitoring-arc-server). | Via the local tools. Manage these VMs through the management consoles of the same local tools used for their creation. |
 
 > [!NOTE]
-> Currently, conversion of an Arc-enabled server or unmanaged VM to an Azure Local VM isn't supported.
+> Currently, conversion of an Azure Arc-enabled server or unmanaged VM to an Azure Local VM isn't supported.
+
+## Comparison of VM management capabilities
 
-## Compare VM management capabilities
+The following table compares the management capabilities for Azure Local VMs, Azure Arc-enabled servers, and unmanaged VMs across various operations and features available through the Azure portal:
 
-The following table compares the management capabilities for Azure Local VMs, Arc-enabled servers, and unmanaged VMs across various operations and features available through the Azure portal:
+Keep in mind the following information when comparing VM management capabilities:
 
-> [!IMPORTANT]
-> Keep in mind the following information when comparing VM management capabilities:
->- Microsoft Product Terms for your program override this section. For more information, see [Microsoft Azure Product Terms](https://www.microsoft.com/licensing/#products) and select your program to show the terms.
->- Some services, even if included in Azure Hybrid Benefits, may incur operational costs, such as storing log data. For more information, see [Azure Pricing calculator](https://azure.microsoft.com/pricing/calculator/).
->- Some key features are part of the Windows Server Management enabled by Azure Arc experience. For more information, see [Windows Server Management enabled by Azure Arc](/azure/azure-arc/servers/windows-server-management-overview?tabs=portal).
+- Microsoft Product Terms for your program override this section. For more information, see [Microsoft Azure Product Terms](https://www.microsoft.com/licensing/#products) and select your program to show the terms.
+- Some services, even if included in Azure Hybrid Benefits, may incur operational costs, such as storing log data. For more information, see [Azure Pricing calculator](https://azure.microsoft.com/pricing/calculator/).
+- Some key features are part of the Windows Server Management enabled by Azure Arc experience. For more information, see [Windows Server Management enabled by Azure Arc](/azure/azure-arc/servers/windows-server-management-overview?tabs=portal).
 
-|Azure VM management capability|Azure Local VMs enabled by Azure Arc | Arc-enabled servers | Unmanaged VMs |
+|Azure VM management capability|Azure Local VMs enabled by Azure Arc | Azure Arc-enabled servers | Unmanaged VMs |
 |:-----|:-----:|:-----:|:-----:|
 | **Settings** |
-| - Start|✅|❌|❌|
-| - Restart |✅|❌|❌|
-| - Stop |✅|❌|❌|
-| - Delete |✅|✅|❌|
-| - Save State (CLI) |✅|❌|❌|
-| - Pause (CLI) |✅|❌|❌|
-| - GPU configuration (CLI) |✅|❌|❌|
-| - Add network interface |✅|❌|❌|
-| - Connect with SSH |✅|✅|❌|
-| - Add a new data disk |✅|❌|❌|
-| - Change vCPU count |✅|❌|❌|
-| - Change Memory amount |✅|❌|❌|
-| - Change Min memory |✅|❌|❌|
-| - Change Max memory |✅|❌|❌|
+| Start|✅|❌|❌|
+| Restart |✅|❌|❌|
+| Stop |✅|❌|❌|
+| Delete |✅|✅|❌|
+| Save State (CLI) |✅|❌|❌|
+| Pause (CLI) |✅|❌|❌|
+| GPU configuration (CLI) |✅|❌|❌|
+| Add network interface |✅|❌|❌|
+| Connect with SSH |✅|✅|❌|
+| Add a new data disk |✅|❌|❌|
+| Change vCPU count |✅|❌|❌|
+| Change Memory amount |✅|❌|❌|
+| Change Min memory |✅|❌|❌|
+| Change Max memory |✅|❌|❌|
 | **Operations** |
-| - Microsoft Defender for Cloud |✅|✅|❌|
-| - Security recommendations |✅|✅|❌|
-| - Extension Support |✅|✅|❌|
-| - Locks |✅|✅|❌|
-| - Policies (RBAC, compliance) |✅|✅|❌|
-| - Machine Configuration |✅|✅|❌|
-| - Automanage |✅|❌|❌|
-| - Run command |✅|✅|❌|
-| - SQL Server Configuration |✅|✅|❌|
-| - Azure Update Manager | ✅ <br>[3](#3) | ✅ <br>[1](#1) and [2](#2)  | ❌ |
-| - Inventory |✅|✅  <br>[1](#1) and [2](#2) |❌|
-| - Change tracking |✅|✅  <br>[1](#1) and [2](#2) |❌|
-| - Extended Security Updates | ✅ <br>[3](#3) | ✅ <br>[3](#3) | ❌ |
+| Microsoft Defender for Cloud |✅|✅|❌|
+| Security recommendations |✅|✅|❌|
+| Extension Support |✅|✅|❌|
+| Locks |✅|✅|❌|
+| Policies (RBAC, compliance) |✅|✅|❌|
+| Machine Configuration |✅|✅|❌|
+| Automanage |✅|❌|❌|
+| Run command |✅|✅|❌|
+| SQL Server Configuration |✅|✅|❌|
+| Azure Update Manager | ✅ <br>[3](#3) | ✅ <br>[1](#1) and [2](#2)  | ❌ |
+| Inventory |✅|✅  <br>[1](#1) and [2](#2) |❌|
+| Change tracking |✅|✅  <br>[1](#1) and [2](#2) |❌|
+| Extended Security Updates | ✅ <br>[3](#3) | ✅ <br>[3](#3) | ❌ |
 | **Windows management** |
-| - Windows Admin Center |❌|✅  <br>[1](#1) and [2](#2) |❌|
-| - Best Practices Assessment |❌|✅  <br>[1](#1) and [2](#2) |❌|
+| Windows Admin Center |❌|✅  <br>[1](#1) and [2](#2) |❌|
+| Best Practices Assessment |❌|✅  <br>[1](#1) and [2](#2) |❌|
 | **Monitoring** |
-| - Azure Monitor |✅|✅|❌|
-| - Insights|✅|✅|❌|
-| - Logs |✅|✅|❌|
-| - Alerts |✅|❌|❌|
-| - Workbooks |❌|✅|❌|
+| Azure Monitor |✅|✅|❌|
+| Insights|✅|✅|❌|
+| Logs |✅|✅|❌|
+| Alerts |✅|❌|❌|
+| Workbooks |❌|✅|❌|
 | **Automation** |
-| - CLI/PS |✅|✅|❌|
-| - Tasks |✅|✅|❌|
-| - Export template |✅|❌|❌|
-| - Resource health |❌ <br>(Use Alerts) |✅|❌|
+| CLI/PS |✅|✅|❌|
+| Tasks |✅|✅|❌|
+| Export template |✅|❌|❌|
+| Resource health |❌ <br>(Use Alerts) |✅|❌|
 
 <a name="1"></a>1: At additional costs.
 
 <a name="2"></a>2: Included as part of Windows Server and SQL Server management capabilities enabled by Azure Arc. For more information, see [Azure Hybrid Benefits for Windows Server](/windows-server/get-started/azure-hybrid-benefit?tabs=azure).
 
 <a name="3"></a>3: Included for VMs running on Azure and Azure Local instances.
 
-## Next steps
+## Related content
 
-- Review [Azure Local VM management prerequisites](../manage/azure-arc-vm-management-prerequisites.md).
+- [Review prerequisites for Azure Local VMs enabled by Azure Arc](../manage/azure-arc-vm-management-prerequisites.md).
diff --git a/azure-local/manage/azure-arc-vms-faq.yml b/azure-local/manage/azure-arc-vms-faq.yml
@@ -1,6 +1,6 @@
 ### YamlMime:FAQ
 metadata:
-  title: Azure Local VMs enabled by Azure Arc FAQ 
+  title: Azure Local VMs Enabled by Azure Arc FAQ 
   description: The Azure Local VM management FAQ provides information on questions related to Azure Local.
   ms.topic: faq
   author: alkohli
diff --git a/azure-local/manage/virtual-machine-operations.md b/azure-local/manage/virtual-machine-operations.md
@@ -1,5 +1,5 @@
 ---
-title: Supported operations for Azure Local virtual machines (VMs) enabled by Azure Arc
+title: Supported Operations for Azure Local Virtual Machines (VMs) Enabled by Azure Arc
 description: Learn the supported virtual machine (VM) operations for Azure Local VMs enabled by Azure Arc.
 author: alkohli
 ms.author: alkohli
@@ -23,6 +23,7 @@ While Azure Local VMs are designed to be managed through the Azure control plane
 When IT admins manage Azure Local VMs using the same tools and scripts as those for on-premises VMs, it can result in synchronization errors or more severe problems between the Azure Local VMs and the portal.
 
 > [!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).
 > - Though the operations listed under [Supported operations for local tools](#using-local-tools) don't affect the management of Azure Local VMs, the changes aren't reflected in the Azure portal.
 > - Only the following operations when performed using local tools 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 the power cycle operation.
@@ -63,7 +64,7 @@ The supported operations can be performed via multiple interfaces.
 
 ### 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. 
+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 aren't reflected in the portal.
@@ -120,8 +121,6 @@ The following VM operations aren't supported.
 - Live migrate a VM from one cluster to another.
 - Change the type of disk (static/dynamic/VHD/VHDX).
 
-
-
 ## Related content
 
 - [Manage Arc VMs](manage-arc-virtual-machines.md)
