You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/concepts/compare-vm-management-capabilities.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ You can run these types of VMs on your Azure Local system:
20
20
-**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:
21
21
- 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.
22
22
- Offer extensive management capabilities in the Azure portal, second only to native Azure VMs.
23
-
- 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.
23
+
- Through an Azure Arc resource bridge, provide life-cycle management capabilities like starting, stopping, changing VM memory or vCPU, and adding or removing data disk and network interfaces.
24
24
- 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.
25
25
- Can be managed through Azure.
26
26
@@ -34,14 +34,12 @@ You can run these types of VMs on your Azure Local system:
34
34
- Aren't connected to Azure.
35
35
- Can't be managed through Azure.
36
36
37
-
## Comparison of provisioning and management methods
38
-
39
37
The following table compares the provisioning and management methods for the various types of VMs running on Azure Local:
40
38
41
-
|Provisioning method vs. management method| Azure Local VMs enabled by Azure Arc | Azure Arc-enabled servers | Unmanaged VMs |
39
+
|Method| Azure Local VMs enabled by Azure Arc | Azure Arc-enabled servers | Unmanaged VMs |
42
40
| :---- | :---- | :---- | :---- |
43
-
| Provisioning method |[Azure Local VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Azure Local VMs by using the Azure CLI, the Azure portal, or an Azure Resource Manager template (ARM template). By 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 by 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](/system-center/vmm/provision-vms), or [PowerShell](../manage/vm-powershell.md#create-a-vm).|
44
-
| 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 that you used for their creation. |
41
+
| Provisioning |[Azure Local VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Azure Local VMs by using the Azure CLI, the Azure portal, or an Azure Resource Manager template (ARM template). By 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 by 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](/system-center/vmm/provision-vms), or [PowerShell](../manage/vm-powershell.md#create-a-vm).|
42
+
| Management |[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 that you used for their creation. |
45
43
46
44
> [!NOTE]
47
45
> Currently, conversion of an Azure Arc-enabled server or an unmanaged VM to an Azure Local VM isn't supported.
@@ -53,7 +51,7 @@ The following table compares the management capabilities for Azure Local VMs, Az
53
51
Keep in mind the following information when you're comparing VM management capabilities:
54
52
55
53
- Azure product terms for your program override this section. For more information, see [Understand, choose, and manage your Microsoft licenses](https://www.microsoft.com/licensing/#products) and select your program.
56
-
- Some services, even if they're included in Azure Hybrid Benefit, might incur operational costs such as storing log data. For more information, see the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
54
+
- Some services, even if they're included in Azure Hybrid Benefit, might incur operational costs for activities like storing log data. For more information, see the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
57
55
- Some key features are part of the experience of Windows Server Management enabled by Azure Arc. For more information, see [Windows Server Management enabled by Azure Arc](/azure/azure-arc/servers/windows-server-management-overview?tabs=portal).
58
56
59
57
|Azure VM management capability|Azure Local VMs enabled by Azure Arc | Azure Arc-enabled servers | Unmanaged VMs |
@@ -102,7 +100,7 @@ Keep in mind the following information when you're comparing VM management capab
102
100
| Export template |✅|❌|❌|
103
101
| Resource health |❌ <br>(Use Alerts) |✅|❌|
104
102
105
-
<aname="1"></a>1: At additional costs.
103
+
<aname="1"></a>1: At additional cost.
106
104
107
105
<aname="2"></a>2: Included as part of Windows Server and SQL Server management capabilities enabled by Azure Arc. For more information, see [Azure Hybrid Benefit for Windows Server](/windows-server/get-started/azure-hybrid-benefit?tabs=azure).
Copy file name to clipboardExpand all lines: azure-local/manage/azure-arc-vms-faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ sections:
56
56
Software-defined networking (SDN) is currently not supported for VMs created from the Azure portal. For more information on using SDN in Azure Local, see the [technical reference for SDN in Azure Local](sdn-technical-reference.md).
57
57
58
58
- question: |
59
-
How can I perform live migration of Azure Local virtual machines?
59
+
How can I perform live migration of Azure Local VMs?
60
60
answer: |
61
61
Live migration of Azure Local VMs is supported via on-premises tools like [Failover Cluster Manager](/windows-server/manage/windows-admin-center/use/manage-failover-clusters#adding-a-failover-cluster-to-windows-admin-center) or [Windows Admin Center](/windows-server/manage/windows-admin-center/use/manage-virtual-machines#live-migrate-a-virtual-machine-to-another-cluster-node). Live migration of VM storage is not supported.
62
62
@@ -87,7 +87,7 @@ sections:
87
87
- question: |
88
88
If I delete a gallery image, are all the deployed VMs also deleted?
89
89
answer: |
90
-
Deleting a gallery image doesn't affect the VMs that you created by using that image. It just removes the image name from the VM details.
90
+
Deleting a gallery image removes the image name from VM details. It doesn't affect the VMs that you created by using the image.
91
91
92
92
- question: |
93
93
If I delete Azure Arc resource bridge, are the VMs also deleted?
Copy file name to clipboardExpand all lines: azure-local/manage/virtual-machine-operations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ When IT admins manage Azure Local VMs by using the same tools and scripts as tho
26
26
>
27
27
> - 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.
28
28
> - 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.
29
-
> - Only the following operations update the state of the Azure Local VM in the portal (when you perform them by using local tools): change the size of VM memory, change the vCPU count, or change the power state status (start/stop a VM) resulting from the power cycle operation.
29
+
> - 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 size of VM memory, change the vCPU count, or change the power state (start or stop a VM) resulting from the power cycle operation.
30
30
31
-
## Supported operations for VMs
31
+
## Supported VM operations
32
32
33
33
You can use multiple interfaces to perform supported operations for VMs.
0 commit comments