Skip to content

Commit ff2d923

Browse files
committed
Updated with rebranding changes.
1 parent e901fdc commit ff2d923

File tree

3 files changed

+30
-31
lines changed

3 files changed

+30
-31
lines changed

azure-local/manage/collect-log-files-arc-enabled-vms.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
2-
title: Collect log files for Azure Arc VMs on Azure Local
3-
description: Learn how to collect log files for an Azure Arc VMs on Azure Local.
2+
title: Collect log files for Azure Local VMs enabled by Azure Arc
3+
description: Learn how to collect log files for an Azure Local VM enabled by Azure Arc.
44
author: alkohli
55
ms.topic: how-to
6-
ms.date: 10/22/2024
6+
ms.date: 03/18/2025
77
ms.author: alkohli
88
ms.reviewer: vlakshmanan
99
ms.service: azure-local
1010
---
1111

12-
# Collect log files for Azure Arc VMs on Azure Local
12+
# Collect log files for Azure Local VMs enabled by Azure Arc
1313

1414
[!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
1515

16-
Collect logs and other files to identify and troubleshoot issues with Arc virtual machines (VMs) on your Azure Local instance.
16+
Collect logs and other files to identify and troubleshoot issues with Azure Local virtual machines (VMs) enabled by Azure Arc.
1717

1818
## Collect files when VM provisioning fails
1919

@@ -44,7 +44,7 @@ Examine these log files to investigate a VM provisioning failure:
4444

4545
## Collect guest logs
4646

47-
Collect guest logs to gather information on Arc VM issues before you contact Microsoft Support.
47+
Collect guest logs to gather information about issues with Azure Local VMs enabled by Azure Arc before you contact Microsoft Support.
4848

4949
### Logs inside the VM
5050

@@ -59,7 +59,7 @@ For more information, see [Active Directory domain join troubleshooting guidance
5959

6060
### MOC guest agent logs
6161

62-
MOC guest agent logs are useful when Arc VM provisioning fails with the following error:
62+
MOC guest agent logs are useful when provisioning fails on an Azure Local VM with the following error:
6363

6464
`Could not establish HyperV connection for VM ID...`
6565

azure-local/manage/manage-arc-virtual-machine-resources.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
---
2-
title: Manage Azure Arc VM Resources for Azure Local Virtual Machines
3-
description: Learn how to manage resource such as data disks and network interfaces on an Azure Arc VM.
2+
title: Manage Azure Local VM Resources for Azure Local Virtual Machines
3+
description: Learn how to manage resources such as data disks and network interfaces on an Azure Local VM.
44
author: alkohli
55
ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-local
8-
ms.date: 01/14/2025
8+
ms.date: 03/18/2025
99
---
1010

11-
# Manage resources for Azure Arc VMs on Azure Local
11+
# Manage resources for Azure Local VMs
1212

1313
[!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
1414

15-
After you deploy Azure Arc virtual machines (VMs), you might need to add or delete resources such as data disks and network interfaces. This article describes how to manage these VM resources for an Azure Arc VM running on your Azure Local instance.
15+
After you deploy Azure Local virtual machines (VMs), you might need to add or delete resources such as data disks and network interfaces. This article describes how to manage these VM resources for an Azure Local VM running on your Azure Local instance.
1616

1717
You can add or delete the resources by using the Azure portal. For the task of adding a data disk, you can also use the Azure CLI.
1818

1919
## Prerequisites
2020

21-
- Access to an Azure Local instance that's deployed and registered. You should have one or more Azure Arc VMs running on this system. For more information, see [Create Azure Arc virtual machines on Azure Local](./create-arc-virtual-machines.md).
21+
- Access to an Azure Local instance that's deployed and registered. You should have one or more Azure Local VMs running on this system. For more information, see [Create Azure Local virtual machines](./create-arc-virtual-machines.md).
2222

2323
## Add a data disk
2424

@@ -120,7 +120,7 @@ Follow these steps in the Azure portal for your Azure Local instance:
120120

121121
:::image type="content" source="./media/manage-arc-virtual-machine-resources/add-network-interface-3.png" alt-text="Screenshot of the Apply button on the Networking pane for a virtual machine." lightbox="./media/manage-arc-virtual-machine-resources/add-network-interface-3.png":::
122122

123-
1. You get a notification that the job for network interface creation started. After the network interface is created, it's attached to the Azure Arc VM.
123+
1. You get a notification that the job for network interface creation started. After the network interface is created, it's attached to the Azure Local VM.
124124

125125
:::image type="content" source="./media/manage-arc-virtual-machine-resources/add-network-interface-4.png" alt-text="Screenshot of the Notifications pane for network interface creation beside the Networking pane for a virtual machine." lightbox="./media/manage-arc-virtual-machine-resources/add-network-interface-4.png":::
126126

@@ -143,7 +143,7 @@ Follow these steps in the Azure portal for your Azure Local instance.
143143

144144
:::image type="content" source="./media/manage-arc-virtual-machine-resources/delete-network-interface-2.png" alt-text="Screenshot of the confirmation dialog for deleting a network interface." lightbox="./media/manage-arc-virtual-machine-resources/delete-network-interface-2.png":::
145145

146-
1. Select **Apply** to apply the changes. The network interface is dissociated from the Azure Arc VM.
146+
1. Select **Apply** to apply the changes. The network interface is dissociated from the Azure Local VM.
147147

148148
:::image type="content" source="./media/manage-arc-virtual-machine-resources/delete-network-interface-3.png" alt-text="Screenshot of the Apply button on the Networking pane for a VM." lightbox="./media/manage-arc-virtual-machine-resources/delete-network-interface-3.png":::
149149

@@ -153,4 +153,4 @@ Follow these steps in the Azure portal for your Azure Local instance.
153153

154154
## Related content
155155

156-
- [Manage VM extensions on Azure Local virtual machines](./virtual-machine-manage-extension.md)
156+
- [Manage VM extensions on Azure Local virtual machines](./virtual-machine-manage-extension.md).

azure-local/manage/trusted-launch-vm-overview.md

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,24 @@
11
---
2-
title: Overview for Trusted launch for Azure Arc VMs on Azure Local
3-
description: Learn about Trusted launch for Azure Arc VMs on Azure Local.
2+
title: Overview for Trusted launch for Azure Local VMs enabled by Azure Arc
3+
description: Learn about Trusted launch for Azure Local VMs enabled by Azure Arc.
44
ms.topic: conceptual
55
author: alkohli
66
ms.author: alkohli
77
ms.service: azure-local
8-
ms.date: 02/20/2025
8+
ms.date: 03/18/2025
99
---
1010

11-
# Introduction to Trusted launch for Azure Arc VMs on Azure Local
11+
# Introduction to Trusted launch for Azure Local VMs enabled by Azure Arc
1212

1313
[!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
1414

15-
This article introduces Trusted launch for Azure Arc virtual machines (VMs) on Azure Local. You can create a Trusted launch Arc VM using Azure portal or by using Azure Command-Line Interface (CLI).
16-
15+
This article introduces Trusted launch for Azure Local virtual machines (VMs). You can create a Trusted launch VM using Azure portal or by using Azure Command-Line Interface (CLI).
1716

1817
## Introduction
1918

20-
Trusted launch for Azure Arc VMs enables secure boot, installs a virtual Trusted Platform Module (vTPM) device, automatically transfers the vTPM state when the VM migrates or fails over to another machine within the system, and supports the ability to attest whether the VM started in a known good state.
19+
Trusted launch VMs enable secure boot, installs a virtual Trusted Platform Module (vTPM) device, automatically transfers the vTPM state when the VM migrates or fails over to another machine within the system, and supports the ability to attest whether the VM started in a known good state.
2120

22-
Trusted launch is a security type that can be specified when creating Arc VMs on Azure Local. For more information, see [Trusted launch for Azure Arc VMs on Azure Local](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/trusted-launch-for-azure-arc-vms-on-azure-stack-hci-version-23h2/ba-p/3978051).
21+
Trusted launch is a security type that can be specified when creating Azure Local VMs. For more information, see [Trusted launch for Azure Local VMs enabled by Azure Arc](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/trusted-launch-for-azure-arc-vms-on-azure-stack-hci-version-23h2/ba-p/3978051).
2322

2423
## Capabilities and benefits
2524

@@ -35,31 +34,31 @@ Trusted launch is a security type that can be specified when creating Arc VMs on
3534
3635
## Guidance
3736

38-
- IgvmAgent is a component that is installed on all machines in the Azure Local system. It enables support for isolated VMs such as Trusted launch Arc VMs for example.
37+
- IgvmAgent is a component that is installed on all machines in the Azure Local system. It enables support for isolated VMs like Trusted launch for Azure Local VMs, for example.
3938

40-
- As part of Trusted launch Arc VM creation, Hyper-V creates VM files at a default location on disk to store the VM state. By default, access to those VM files is restricted to host server administrators only. If you store those VM files in a different location, you must ensure that the location is access restricted to host server administrators only.
39+
- As part of Trusted launch for Azure Local VM creation, Hyper-V creates VM files at a default location on disk to store the VM state. By default, access to those VM files is restricted to host server administrators only. If you store those VM files in a different location, you must ensure that the location is access restricted to host server administrators only.
4140

4241
- VM live migration network traffic is not encrypted. We strongly recommend that you enable a network layer encryption technology such as IPsec to protect live migration network traffic.
4342

4443
<!--- VM live migration network traffic is not encrypted. We strongly recommend that you enable IPsec to protect live migration network traffic. For more information, see [Network Recommendations for a Hyper-V Cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn550728(v=ws.11)#How_to_isolate_the_network_traffic_on_a_Hyper-V_cluster).-->
4544

4645
## Guest operating system images
4746

48-
All Windows 11 images (excluding 24H2 Windows 11 SKUs) and Windows Server 2022 images from Azure Marketplace supported by Azure Arc VMs are supported. See [Create Azure Local VM image using Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace?tabs=azurecli) for a list of all supported Windows 11 images.
47+
All Windows 11 images (excluding 24H2 Windows 11 SKUs) and Windows Server 2022 images from Azure Marketplace supported by Azure Local VMs are supported. See [Create Azure Local VM enabled by Azure Arc image using Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace?tabs=azurecli) for a list of all supported Windows 11 images.
4948

5049
> [!NOTE]
5150
> VM guest images obtained outside of Azure Marketplace are not supported.
5251
5352
## Backup and disaster recovery considerations
5453

55-
When working with Trusted launch Arc VMs, make sure to understand the following key considerations and limitations related to backup and recovery:
54+
When working with Trusted launch for Azure Local VMs, make sure to understand the following key considerations and limitations related to backup and recovery:
5655

57-
- **Differences between Trusted launch Arc VMs and standard Arc VMs**: Unlike standard Azure Arc VMs, Trusted launch Arc VMs use a VM guest state protection key to protect the VM guest state, including the virtual TPM (vTPM) state, while at rest. The VM protection key is stored in a local key vault in the Azure Local system where the VM resides. Trusted launch Arc VMs store the VM guest state in two files: VM guest state and VM runtime state. To back up and restore a Trusted launch VM, a backup solution must back up and restore all the VM files, including guest state and the runtime state files, and additionally backup and restore the VM protection key.
56+
- **Differences between Trusted launch for Azure Local VMs and standard Azure Local VMs**: Unlike standard Azure Local VMs, Trusted launch for Azure Local VMs use a VM guest state protection key to protect the VM guest state, including the virtual TPM (vTPM) state, while at rest. The VM protection key is stored in a local key vault in the Azure Local system where the VM resides. Trusted launch for Azure Local VMs store the VM guest state in two files: VM guest state and VM runtime state. To back up and restore a Trusted launch VM, a backup solution must back up and restore all the VM files, including guest state and the runtime state files, and additionally backup and restore the VM protection key.
5857

59-
- **Backup and disaster recovery tooling support**: Currently, Trusted launch Arc VMs do not support any third-party or Microsoft-owned back up and disaster recovery tools, including but not limited to, Azure Backup, Azure Site Recovery, Veeam, and Commvault. If there arises a need to move a Trusted launch Arc TVM to an alternate cluster, see the manual process [Manual backup and recovery of Trusted launch Arc VMs](./trusted-launch-vm-import-key.md) to manage all the necessary files and VM protection key to ensure that the VM can be successfully restored.
58+
- **Backup and disaster recovery tooling support**: Currently, Trusted launch for Azure Local VMs do not support any third-party or Microsoft-owned back up and disaster recovery tools, including but not limited to, Azure Backup, Azure Site Recovery, Veeam, and Commvault. If there arises a need to move a Trusted launch for Azure Local TVM to an alternate cluster, see the manual process [Manual backup and recovery of Trusted launch for Azure Local VMs](./trusted-launch-vm-import-key.md) to manage all the necessary files and VM protection key to ensure that the VM can be successfully restored.
6059

6160
> [!NOTE]
62-
> Trusted launch Arc VMs restored on an alternate Azure Local system cannot be managed from the Azure control plane.
61+
> Trusted launch for Azure Local VMs restored on an alternate Azure Local system cannot be managed from the Azure control plane.
6362
6463
## Next steps
6564

0 commit comments

Comments
 (0)