Skip to content

Commit 7288f81

Browse files
author
Manika Dhiman
committed
fixed build warnings
1 parent d765e97 commit 7288f81

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

azure-local/concepts/compare-vm-management-capabilities.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ This article describes the types of virtual machines (VMs) that can run on Azure
1717

1818
Here are the different types of VMs that you can run on your Azure Local system:
1919

20-
- **Arc VMs.** Windows and Linux VMs hosted in an on-premises Azure Local environment. These VMs are created using [Arc VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal), registered to [Arc Resource Bridge](.../azure/azure-arc/resource-bridge/overview), and have the [Azure Connected Machine agent](.../azure/azure-arc/servers/agent-release-notes) installed. Arc VMs offer extensive management capabilities in the Azure portal, second only to native Azure VMs. They allow lifecycle management capabilities like starting, restarting, stopping, changing VM memory/vCPU, and adding or removing data disk and network interfaces with the help of Arc Resource Bridge. In addition, through the Arc Connected Machine agent, they can utilize Azure VM extensions like Defender for Cloud, Log Analytics, and Azure Monitor to help govern, protect, configure, and monitor VMs.
20+
- **Arc VMs.** Windows and Linux VMs hosted in an on-premises Azure Local environment. These VMs are created using [Arc VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal), registered to [Arc Resource Bridge](../azure/azure-arc/resource-bridge/overview), and have the [Azure Connected Machine agent](../azure/azure-arc/servers/agent-release-notes) installed. Arc VMs offer extensive management capabilities in the Azure portal, second only to native Azure VMs. They allow lifecycle management capabilities like starting, restarting, stopping, changing VM memory/vCPU, and adding or removing data disk and network interfaces with the help of Arc Resource Bridge. In addition, through the Arc Connected Machine agent, they can utilize Azure VM extensions like Defender for Cloud, Log Analytics, and Azure Monitor to help govern, protect, configure, and monitor VMs.
2121

22-
- **Arc-enabled servers.** Windows and Linux VMs running on Azure Local with the [Azure Connected Machine agent](.../azure/azure-arc/servers/agent-release-notes) installed. Like Arc VMs, these VMs can also utilize Azure VM extensions to help govern, protect, configure, and monitor VMs. However, they lack the lifecycle management capabilities that come with Arc VMs.
22+
- **Arc-enabled servers.** Windows and Linux VMs running on Azure Local with the [Azure Connected Machine agent](../azure/azure-arc/servers/agent-release-notes) installed. Like Arc VMs, these VMs can also utilize Azure VM extensions to help govern, protect, configure, and monitor VMs. However, they lack the lifecycle management capabilities that come with Arc VMs.
2323

2424
- **Non-arc VMs.** Windows and Linux machines created and hosted in an on-premises Azure Local environment, not connected to Azure. You can't manage non-Arc VMs through the Azure portal.
2525

@@ -30,10 +30,6 @@ The following table compares the provisioning and management methods for the var
3030
| Provisioning method | - (Recommended) [Arc VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Arc VMs using Azure CLI, Azure portal, or Azure Resource Manager 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 Hyper-V VMs as Arc VMs to Azure Local using the migration flow. | Virtual machines on your Azure Local system managed through Azure Arc. Connect these machines to Azure by installing the [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview) on each machine. For example, each Azure Local host machine is Arc-enabled, facilitating management from the Azure portal. | On-premises provisioning flow. Use local tools like [Windows Admin Center](../manage/vm.md#create-a-new-vm), [System Center Virtual Machine Manager (SCVMM)](/system-center/vmm/provision-vms), [PowerShell](../manage/vm-powershell.md#create-a-vm), and Failover Cluster Manager available in your on-premises environment.|
3131
| Management method | Via [the Azure portal](../manage/manage-arc-virtual-machines.md). | Via the Azure portal. 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. |
3232

33-
The following diagram compares the deployment flows for different VM types:
34-
35-
:::image type="content" source="media/compare-vm-management-capabilities/vm-lifecycle.png" alt-text="Diagram that compares the local and Arc VM deployment flows." lightbox="media/compare-vm-management-capabilities/vm-lifecycle.png" :::
36-
3733
## Compare VM management capabilities
3834

3935
The following table compares the management capabilities for Arc VMs, non-Arc VMs, and Arc-enabled servers across various operations and features available through the Azure portal:

0 commit comments

Comments
 (0)