Merge pull request #17374 from LouisBerner/v-loberner-ado-407927-local-vm-mgmt-rebranding-1

JamesJBarnett · web-flow · commit d6c095c3f82d · 2025-03-20T20:01:01.000-07:00
Updated with rebranding changes.
diff --git a/azure-local/TOC.yml b/azure-local/TOC.yml
@@ -253,7 +253,7 @@ items:
       href: manage/connect-arc-vm-using-ssh.md
     - name: Manage Arc VMs
       href: manage/manage-arc-virtual-machines.md
-    - name: Manage Arc VM resources
+    - name: Manage Azure Local VM resources
       href: manage/manage-arc-virtual-machine-resources.md 
     - name: Manage VM extensions
       href: manage/virtual-machine-manage-extension.md
@@ -268,7 +268,7 @@ items:
       - name: Extended Security Updates (ESUs)
         href: manage/azure-benefits-esu.md
    
-    - name: Collect log files for Azure Arc VM
+    - name: Collect log files for Azure Local VM
       href: manage/collect-log-files-arc-enabled-vms.md 
     - name: Troubleshoot
       href: manage/troubleshoot-arc-enabled-vms.md
@@ -277,7 +277,7 @@ items:
 
   - name: Trusted launch for Arc VMs
     items: 
-      - name: What is Trusted launch for Arc VMs?
+      - name: What is Trusted launch for Azure Local VMs?
         href: manage/trusted-launch-vm-overview.md
       - name: Automatic virtual TPM state transfer
         href: manage/trusted-launch-automatic-state-transfer.md
diff --git a/azure-local/manage/assign-vm-rbac-roles.md b/azure-local/manage/assign-vm-rbac-roles.md
@@ -1,18 +1,18 @@
 ---
-title: Use builtin RBAC roles for Arc VM management on Azure Local
-description: Learn how to use RBAC builtin roles for Arc VM management on Azure Local.
+title: Use builtin RBAC roles for Azure Local VM to manage Azure Local VMs enabled by Azure Arc
+description: Learn how to use RBAC builtin roles to manage Azure Local VMs enabled by Azure Arc.
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 11/15/2024
+ms.date: 03/20/2025
 ---
 
-# Use Role-based Access Control to manage Azure Local virtual machines 
+# Use Role-based Access Control to manage Azure Local VMs enabled by Azure Arc 
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 
-This article describes how to use the Role-based Access Control (RBAC) to control access to Arc virtual machines (VMs) running on Azure Local.
+This article describes how to use the Role-based Access Control (RBAC) to control access to Azure Local virtual machines (VMs) enabled by Azure Arc.
 
 You can use the builtin RBAC roles to control access to VMs and VM resources such as virtual disks, network interfaces, VM images, logical networks and storage paths. You can assign these roles to users, groups, service principals and managed identities.
 
@@ -26,14 +26,12 @@ To control access to VMs and VM resources on Azure Local, you can use the follow
 
 Here's a table that describes the VM actions granted by each role for the VMs and the various VM resources. The VM resources are referred to resources required to create a VM and include virtual disks, network interfaces, VM images, logical networks, and storage paths:
 
-
 | Builtin role | VMs | VM resources |
 |--|--|--|
 | Azure Stack HCI Administrator | Create, list, delete VMs<br><br> Start, stop, restart VMs | Create, list, delete all VM resources including logical networks, VM images, and storage paths |
 | Azure Stack HCI VM Contributor | Create, list, delete VMs<br><br> Start, stop, restart VMs | Create, list, delete all VM resources except logical networks, VM images, and storage paths |
 | Azure Stack HCI VM Reader | List all VMs | List all VM resources |
 
- 
 ## Prerequisites
 
 Before you begin, make sure to complete the following prerequisites:
@@ -44,18 +42,17 @@ Before you begin, make sure to complete the following prerequisites:
 
 ## Assign RBAC roles to users
 
-You can assign RBAC roles to user via the Azure portal. Follow these steps to assign RBAC roles to users:
+You can assign RBAC roles to users via the Azure portal. Follow these steps to assign RBAC roles to users:
 
 1. In the Azure portal, search for the scope to grant access to, for example, search for subscriptions, resource groups, or a specific resource. In this example, we use the subscription in which your Azure Local is deployed.
 
-
-1. Go to your subscription and then go to **Access control (IAM) > Role assignments**. From the top command bar, select **+ Add** and then select **Add role assignment**.
+1. Go to your subscription and then go to **Access control (IAM)** > **Role assignments**. From the top command bar, select **+ Add** and then select **Add role assignment**.
 
     If you don't have permissions to assign roles, the **Add role assignment** option is disabled.
 
     :::image type="content" source="./media/assign-vm-rbac-roles/add-role-assignment-1.png" alt-text="Screenshot showing RBAC role assignment in Azure portal for your Azure Local." lightbox="./media/assign-vm-rbac-roles/add-role-assignment-1.png":::
 
-1. On the **Role** tab, select an RBAC role to assign and choose from one of the following builtin roles:
+1. On the **Role** tab, select an RBAC role to assign and select one of the following builtin roles:
 
     - **Azure Stack HCI Administrator**
     - **Azure Stack HCI VM Contributor**
@@ -71,7 +68,7 @@ You can assign RBAC roles to user via the Azure portal. Follow these steps to as
 
     :::image type="content" source="./media/assign-vm-rbac-roles/add-role-assignment-4.png" alt-text="Screenshot showing Review + assign tab during role assignment in Azure portal for your Azure Local instance." lightbox="./media/assign-vm-rbac-roles/add-role-assignment-4.png":::
 
-1. Verify the role assignment. Go to **Access control (IAM) > Check access > View my access**. You should see the role assignment.
+1. Verify the role assignment. Go to **Access control (IAM)** > **Check access** > **View my access**. You should see the role assignment.
 
     :::image type="content" source="./media/assign-vm-rbac-roles/add-role-assignment-5.png" alt-text="Screenshot showing newly assigned role in Azure portal for your Azure Local instance." lightbox="./media/assign-vm-rbac-roles/add-role-assignment-5.png":::
 
diff --git a/azure-local/manage/collect-log-files-arc-enabled-vms.md b/azure-local/manage/collect-log-files-arc-enabled-vms.md
@@ -1,19 +1,19 @@
 ---
-title: Collect log files for Azure Arc VMs on Azure Local
-description: Learn how to collect log files for an Azure Arc VMs on Azure Local. 
+title: Collect log files for Azure Local VMs enabled by Azure Arc
+description: Learn how to collect log files for an Azure Local VM enabled by Azure Arc. 
 author: alkohli
 ms.topic: how-to
-ms.date: 10/22/2024
+ms.date: 03/20/2025
 ms.author: alkohli
 ms.reviewer: vlakshmanan
 ms.service: azure-local
 ---
 
-# Collect log files for Azure Arc VMs on Azure Local
+# Collect log files for Azure Local VMs enabled by Azure Arc
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 
-Collect logs and other files to identify and troubleshoot issues with Arc virtual machines (VMs) on your Azure Local instance.
+Collect logs and other files to identify and troubleshoot issues with Azure Local virtual machines (VMs) enabled by Azure Arc.
 
 ## Collect files when VM provisioning fails
 
@@ -44,7 +44,7 @@ Examine these log files to investigate a VM provisioning failure:
 
 ## Collect guest logs
 
-Collect guest logs to gather information on Arc VM issues before you contact Microsoft Support.
+Collect guest logs to gather information about issues with Azure Local VMs before you contact Microsoft Support.
 
 ### Logs inside the VM
 
@@ -59,7 +59,7 @@ For more information, see [Active Directory domain join troubleshooting guidance
 
 ### MOC guest agent logs
 
-MOC guest agent logs are useful when Arc VM provisioning fails with the following error:
+MOC guest agent logs are useful when provisioning on an Azure Local VM fails with the following error:
 
 `Could not establish HyperV connection for VM ID...`
 
diff --git a/azure-local/manage/manage-arc-virtual-machine-resources.md b/azure-local/manage/manage-arc-virtual-machine-resources.md
@@ -1,24 +1,24 @@
 ---
-title: Manage Azure Arc VM Resources for Azure Local Virtual Machines
-description: Learn how to manage resource such as data disks and network interfaces on an Azure Arc VM.
+title: Manage resources for Azure Local VMs enabled by Azure Arc
+description: Learn how to manage resources like data disks and network interfaces on an Azure Local VM enabled by Azure Arc.
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 01/14/2025
+ms.date: 03/18/2025
 ---
 
-# Manage resources for Azure Arc VMs on Azure Local
+# Manage resources for Azure Local VMs enabled by Azure Arc
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 
-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.
+After you deploy Azure Local virtual machines (VMs) enabled by Azure Arc, 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.
 
 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.
 
 ## Prerequisites
 
-- 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).
+- 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 an Azure Local VM enabled by Azure Arc](./create-arc-virtual-machines.md).
 
 ## Add a data disk
 
@@ -120,7 +120,7 @@ Follow these steps in the Azure portal for your Azure Local instance:
 
    :::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":::
 
-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.
+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.
 
    :::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":::
 
@@ -143,7 +143,7 @@ Follow these steps in the Azure portal for your Azure Local instance.
 
     :::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":::
 
-1. Select **Apply** to apply the changes. The network interface is dissociated from the Azure Arc VM.
+1. Select **Apply** to apply the changes. The network interface is dissociated from the Azure Local VM.
 
    :::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":::
 
@@ -153,4 +153,4 @@ Follow these steps in the Azure portal for your Azure Local instance.
 
 ## Related content
 
-- [Manage VM extensions on Azure Local virtual machines](./virtual-machine-manage-extension.md)
+- [Manage VM extensions on Azure Local virtual machines](./virtual-machine-manage-extension.md).
diff --git a/azure-local/manage/trusted-launch-vm-overview.md b/azure-local/manage/trusted-launch-vm-overview.md
@@ -1,25 +1,24 @@
 ---
-title: Overview for Trusted launch for Azure Arc VMs on Azure Local
-description: Learn about Trusted launch for Azure Arc VMs on Azure Local.
+title: Overview for Trusted launch for Azure Local VMs enabled by Azure Arc
+description: Learn about Trusted launch for Azure Local VMs enabled by Azure Arc.
 ms.topic: conceptual
 author: alkohli
 ms.author: alkohli
 ms.service: azure-local
-ms.date: 02/20/2025
+ms.date: 03/20/2025
 ---
 
-# Introduction to Trusted launch for Azure Arc VMs on Azure Local
+# Introduction to Trusted launch for Azure Local VMs enabled by Azure Arc
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-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).
-
+This article introduces Trusted launch for Azure Local virtual machines (VMs) enabled by Azure Arc. You can create a Trusted launch for an Azure Local VM using the Azure portal or by using Azure Command-Line Interface (CLI).
 
 ## Introduction
 
-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.
+Trusted launch for Azure Local 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.
 
-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).
+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).
 
 ## Capabilities and benefits
 
@@ -35,32 +34,32 @@ Trusted launch is a security type that can be specified when creating Arc VMs on
 
 ## Guidance
 
-- 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.
+- 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.
 
-- 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.
+- 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.
 
 - 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.
 
 <!--- 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).-->
 
 ## Guest operating system images
 
-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.
+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 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.
 
 > [!NOTE]
 > VM guest images obtained outside of Azure Marketplace are not supported.
 
 ## Backup and disaster recovery considerations
 
-When working with Trusted launch Arc VMs, make sure to understand the following key considerations and limitations related to backup and recovery:
+When working with Trusted launch for Azure Local VMs, make sure to understand the following key considerations and limitations related to backup and recovery:
 
-- **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.
+- **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.
 
-- **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.  
+- **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.  
 
 > [!NOTE]
-> Trusted launch Arc VMs restored on an alternate Azure Local system cannot be managed from the Azure control plane.
+> Trusted launch for Azure Local VMs restored on an alternate Azure Local system cannot be managed from the Azure control plane.
 
 ## Next steps
 
-- [Create Trusted launch VMs](create-arc-virtual-machines.md).
+- [Create Trusted launch for Azure Local VMs](create-arc-virtual-machines.md).
