Merge pull request #17599 from LouisBerner/v-loberner-ado-419022-rebranding-local-vm-management-1

Updates for Azure Local VM rebranding.

Author: prmerger-automator[bot]

azure-local/deploy/deployment-virtual.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.topic: how-to
-ms.date: 02/20/2025
+ms.date: 04/08/2025
 ---
 
 # Deploy a virtual Azure Local system
@@ -39,7 +39,7 @@ Before you begin, make sure that:
 
     | Component | Minimum |
     | ------------- | -------- |
-    | Processor| Intel VT-x or AMD-V, with support for nested virtualization. For more information, see [Does My Processor Support Intel® virtualization technology?](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html).
+    | Processor| Intel VT-x or AMD-V, with support for nested virtualization. For more information, see [Does My Processor Support Intel® virtualization technology?](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html)
     | Memory| The physical host must have a minimum of 32 GB RAM for single virtual node deployments. The virtual host VM should have at least 24 GB RAM.<br><br>The physical host must have a minimum of 64 GB RAM for two virtual node deployments. Each virtual host VM should have at least 24 GB RAM for deployment and 32 GB for applying updates.|
     | Host network adapters| A single network adapter.|
     | Storage| 1 TB Solid state drive (SSD). |
@@ -54,9 +54,9 @@ Before you begin, make sure that each virtual host system can dedicate the follo
 | vCPUs | Four cores. |
 | Memory | A minimum of 24 GB. |
 | Networking | At least two network adapters connected to internal network. MAC spoofing must be enabled. |
-| Boot disk | One disk to install the Azure Stack HCI operating system from ISO. At least 200 GB |
+| Boot disk | One disk to install the Azure Stack HCI operating system from ISO. At least 200 GB. |
 | Hard disks for Storage Spaces Direct | Four dynamic expanding disks. Maximum disk size is 1024 GB. |
-| Data disks | At least 127 GB each. The size must be the same for each disk |
+| Data disks | At least 127 GB each. The size must be the same for each disk. |
 | Time synchronization in integration  | Disabled. |
 
 > [!NOTE]
@@ -359,4 +359,4 @@ Repeat the process above for extra nodes if you plan to test multi-node deployme
 
 ## Next steps
 
-- [Register to Arc and assign permissions for deployment](deployment-arc-register-server-permissions.md)
+- [Register to Arc and assign permissions for deployment](deployment-arc-register-server-permissions.md).

azure-local/manage/collect-logs.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 11/11/2024
+ms.date: 04/08/2025
 ---
 
 # Collect diagnostic logs for Azure Local (preview)
@@ -627,4 +627,4 @@ When requested, share the following information with Microsoft Support. Get this
 
 ## Next steps
 
-- [Contact Microsoft Support](get-support.md)
+- [Contact Microsoft Support](get-support.md).

azure-local/manage/get-support.md

@@ -11,7 +11,7 @@ ms.date: 01/21/2025
 
 [!INCLUDE [hci-applies-to-23h2-22h2](../includes/hci-applies-to-23h2-22h2.md)]
 
-This topic provides guidance on how to get support for Azure Local. Azure Local follows the same support process as Azure. Enterprise customers can follow the process described in [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request). If you're a customer of a Cloud Solution Provider (CSP), contact your CSP for support.
+This article provides guidance on how to get support for Azure Local. Azure Local follows the same support process as Azure. Enterprise customers can follow the process described in [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request). If you're a customer of a Cloud Solution Provider (CSP), contact your CSP for support.
 
 Updates for Azure Local are released monthly to enhance customer experience. To keep your Azure Local instance in a supported state, you have up to six months to install updates, but we recommend installing updates as they are released. Microsoft provides monthly quality and security updates for each supported version of Azure Local and quarterly feature releases.
 

azure-local/manage/support-tools.md

@@ -4,7 +4,7 @@ description: This article provides guidance on the Support Diagnostic Tool for A
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 02/18/2025
+ms.date: 04/09/2025
 ---
 
 # Use the Support Diagnostic Tool to troubleshoot Azure Local issues

azure-local/manage/troubleshoot-deployment.md

@@ -4,7 +4,7 @@ description: Learn how to troubleshoot the deployment validation failures for Az
 ms.topic: how-to
 ms.author: alkohli
 author: alkohli
-ms.date: 02/04/2025
+ms.date: 04/14/2025
 ---
 
 
@@ -17,7 +17,7 @@ This article provides guidance on how to troubleshoot deployment validation issu
 ## Error - deployment validation failure
 
 When deploying Azure Local via the Azure portal, you might encounter a deployment validation failure.
-The "Azure Local Network - Check network requirements" validation task fail with the following error:
+The "Azure Local Network - Check network requirements" validation task fails with the following error:
 
 ```
 Could not complete the operation. 400: Resource creation validation failed. Details:
@@ -46,19 +46,19 @@ The issue occurs for the following reason:
 
 The multi-step resolution process includes the following steps:
 
-- [Remove the lock from the seed node](#remove-the-lock-from-the-seed-node)
+- [Remove the lock from the first machine](#remove-the-lock-from-the-first-machine)
 - [Remove the validation error](#remove-the-validation-error)
 - [Clean up the Edge Device Azure Resource with incorrect VM switch information](#clean-up-the-edge-device-azure-resource-with-incorrect-vm-switch-information)
 - [Refresh the cloud data](#refresh-the-cloud-edgedevices-data)
 - [Restart the deployment via Azure portal](#restart-the-deployment-via-azure-portal)
-- [Recreate the lock on the seed node resource](#recreate-the-lock-on-the-seed-node-resource)
+- [Recreate the lock on the first machine](#recreate-the-lock-on-the-first-machine)
 
 > [!NOTE]
-> All the steps in this article need to be performed on the seed node.
+> All the steps in this article need to be performed on the first machine.
 
-### Remove the lock from the seed node
+### Remove the lock from the first machine
 
-Follow these steps to remove the lock from the seed node:
+Follow these steps to remove the lock from the first machine:
 
 1. To remove the lock, in the Azure portal, go to the object via the resource group or within Machines - Azure Arc.  
 1. In the left-pane, go to **Settings > Locks**.  You should see a lock named **DoNotDelete**. This is the automatic resource lock that is created when the node is onboarded.
@@ -83,7 +83,7 @@ Message: The scope '/subscriptions/<subid>/resourceGroups/<rgname>/providers/Mic
 
 With the lock removed, follow these steps to remove the validation error.
 
-1. Connect to the seed node. Run the following PowerShell command:
+1. Connect to the first machine. Run the following PowerShell command:
 
     ```PowerShell
     Get-VMSwitch
@@ -143,7 +143,7 @@ After the VM switch on the device is removed, clean up the Edge Device ARM resou
     `"switchName": "ConvergedSwitch(managementcompute)",`
     `"switchType": "External"`
 
-1. After confirming the `show` command worked by outputting the `edgeDevices` data, and likely confirming the `"switchDetails"`, it is time to `delete` the resource from ARM so it can be refreshed appropriately from the seed node.
+1. After confirming the `show` command worked by outputting the `edgeDevices` data, and likely confirming the `"switchDetails"`, it is time to `delete` the resource from ARM so it can be refreshed appropriately from the first machine.
 
     > [!NOTE]
     > Deleting the `edgeDevices` data is a safe action to perform, but it should only be performed when explicitly stated. Do not perform this action unless advised to do so.
@@ -182,7 +182,7 @@ With the ARM resource and all the unintentional VM switches removed, refresh the
 
 Follow these steps to refresh the cloud data:
 
-1. Restart the `DeviceManagementService` on the seed node. Run the following PowerShell command:
+1. Restart the `DeviceManagementService` on the first machine. Run the following PowerShell command:
 
    ```PowerShell
     Restart-Service DeviceManagementService
@@ -211,9 +211,9 @@ Follow these steps in the Azure portal:
 
 1. If no other validation issues occur, start the deployment.
 
-### Recreate the lock on the seed node resource
+### Recreate the lock on the first machine
 
-After the mitigation is complete, we strongly recommend that you recreate the lock on the resource.
+After the mitigation is complete, we strongly recommend that you recreate the lock on the first machine.
 
 Follow these steps to recreate the lock:
 

azure-local/manage/troubleshoot-sdn-deployment.md

@@ -4,20 +4,20 @@ description: Learn how to troubleshoot the deployment of Software Defined Networ
 ms.topic: how-to
 ms.author: alkohli
 author: alkohli
-ms.date: 01/16/2025
+ms.date: 04/11/2025
 ---
 
 # Troubleshoot Software Defined Networking deployment in Azure Local via Windows Admin Center
 
 > Applies to: Azure Local 2311.2 and later; Windows Server 2022, Windows Server 2019
 
-This article provides guidance on how to troubleshoot issues that you may encounter while deploying the SDN components using Windows Admin Center. Use this guidance to troubleshoot the issues before creating a support ticket. This article also provides instructions on how to collect logs after successfully troubleshooting the issues to help diagnose the cause of deployment failure.
+This article provides guidance on how to troubleshoot issues that you may encounter while deploying the Software Defined Networking (SDN) components using Windows Admin Center. Use this guidance to troubleshoot the issues before creating a support ticket. This article also provides instructions on how to collect logs after successfully troubleshooting the issues to help diagnose the cause of deployment failure.
 
 ## Troubleshoot timeout error
 
 If the deployment of virtual machines (VM) for the various SDN components, including Network Controller, Software Load Balancer, or Gateway times out, you see the following error:
 
-*....is not ready after the 1800 second timeout.*
+*....isn't ready after the 1,800 second timeout.*
 
 You may see this message in Windows Admin Center during the deployment of Network Controller, Software Load Balancer, or Gateway.
 
@@ -31,7 +31,7 @@ To identify and troubleshoot the cause of the failure in your SDN deployment thr
 
 - [Verify connectivity to the SDN URI or SDN cluster](#verify-connectivity-to-the-sdn-uri-or-sdn-cluster).
 
-After you've completed these checks and resolved any identified issues through troubleshooting, proceed with deploying SDN again. We also recommend [collecting logs](#collect-logs-for-sdn-components) to determine why the deployment of an SDN VM had failed.
+After you've completed these checks and resolved any identified issues through troubleshooting, proceed with deploying SDN again. We also recommend [collecting logs](#collect-logs-for-sdn-components) to determine why the deployment of an SDN VM failed.
 
 ### Download the correct VHDX file
 
@@ -61,7 +61,7 @@ Follow these steps to verify connectivity of the management network VLAN:
 
 ### Ensure that Windows Defender and firewall policies permit WinRM connectivity
 
-You must enable Windows Remote Management (WinRM) and PowerShell remoting to start configuration on the Network Controller VMs that have been deployed. If this is not done, a timeout error occurs.
+You must enable Windows Remote Management (WinRM) and PowerShell remoting to start configuration on the Network Controller VMs that deployed. If this isn't done, a timeout error occurs.
 
 To verify or enable WinRM and PowerShell remoting, perform these steps:
 
@@ -127,7 +127,7 @@ After enabling dynamic DNS, you may be able to move the `SDNAPI` microservice by
 
 ## Collect logs for SDN components
 
-After successfully troubleshooting the deployment issue, we recommend collecting logs to determine why the deployment of an SDN VM had failed.
+After successfully troubleshooting the deployment issue, we recommend collecting logs to determine why the deployment of an SDN VM failed.
 
 Follow these steps to collect guest logs for the SDN VM: