Updated lists

alkohli · alkohli · commit 59a0ee625194 · 2025-03-20T13:34:08.000-07:00
diff --git a/azure-local/deploy/deployment-arc-register-configurator-app.md b/azure-local/deploy/deployment-arc-register-configurator-app.md
@@ -27,9 +27,9 @@ Before you begin, make sure that you complete the following prerequisites:
 
 [!INCLUDE [hci-registration-azure-local-machine-prerequisites](../includes/hci-registration-azure-local-machine-prerequisites.md)]
 
-1. Download the [Configurator App for Azure Local](https://aka.ms/ConfiguratorAppForHCI).
+- Download the [Configurator App for Azure Local](https://aka.ms/ConfiguratorAppForHCI).
 
-1. Note down:
+- Note down:
 
    - The serial number for each machine.
    - Local administrator credentials to sign into each machine.
@@ -38,7 +38,7 @@ Before you begin, make sure that you complete the following prerequisites:
 
 [!INCLUDE [hci-registration-azure-prerequisites](../includes/hci-registration-azure-prerequisites.md)]
 
-1. **Get Arc gateway ID**. Skip this step if you didn't set up Azure Arc gateway. If you [Set up an Azure Arc gateway](../deploy/deployment-azure-arc-gateway-overview.md#create-the-arc-gateway-resource-in-azure), get the resource ID of the Arc gateway. This is also referred to as the `ArcGatewayID`.
+- **Get Arc gateway ID**. Skip this step if you didn't set up Azure Arc gateway. If you [Set up an Azure Arc gateway](../deploy/deployment-azure-arc-gateway-overview.md#create-the-arc-gateway-resource-in-azure), get the resource ID of the Arc gateway. This is also referred to as the `ArcGatewayID`.
 
    1. To get the `ArcGatewayID`, run the following command:  
 
diff --git a/azure-local/includes/hci-registration-azure-local-machine-prerequisites.md b/azure-local/includes/hci-registration-azure-local-machine-prerequisites.md
@@ -8,8 +8,8 @@ ms.reviewer: alkohli
 ms.lastreviewed: 03/20/2025
 ---
 
-1. Complete [prerequisites and complete deployment checklist for your environment](../includes/../deploy/deployment-prerequisites.md).
-1. Prepare [Active Directory](../includes/../deploy/deployment-prep-active-directory.md) environment.
-1. Download the software and [Install the Azure Stack HCI operating system, version 23H2](../includes/../deploy/deployment-install-os.md) on each machine.
+- Complete [prerequisites and complete deployment checklist for your environment](../includes/../deploy/deployment-prerequisites.md).
+- Prepare [Active Directory](../includes/../deploy/deployment-prep-active-directory.md) environment.
+- Download the software and [Install the Azure Stack HCI operating system, version 23H2](../includes/../deploy/deployment-install-os.md) on each machine.
 
 
diff --git a/azure-local/includes/hci-registration-azure-prerequisites.md b/azure-local/includes/hci-registration-azure-prerequisites.md
@@ -9,7 +9,7 @@ ms.lastreviewed: 03/20/2025
 ---
 
 
-1. **Register required resource providers.** Make sure that your Azure subscription is registered against the required resource providers. To register, you must be an owner or contributor on your subscription. You can also ask an administrator to register.
+- **Register required resource providers.** Make sure that your Azure subscription is registered against the required resource providers. To register, you must be an owner or contributor on your subscription. You can also ask an administrator to register.
 
    Run the following [PowerShell commands](/azure/azure-resource-manager/management/resource-providers-and-types#azure-powershell) to register:
 
@@ -28,15 +28,15 @@ ms.lastreviewed: 03/20/2025
     > [!NOTE]
     > The assumption is that the person registering the Azure subscription with the resource providers is a different person than the one who is registering the Azure Local machines with Arc.
 
-1. **Create a resource group**. Follow the steps to [Create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal#create-resource-groups) where you want to register your machines. Make a note of the resource group name and the associated subscription ID.
+- **Create a resource group**. Follow the steps to [Create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal#create-resource-groups) where you want to register your machines. Make a note of the resource group name and the associated subscription ID.
 
-1. **Get the tenant ID**. Follow the steps in [Get the tenant ID of your Microsoft Entra tenant through the Azure portal](/azure/azure-portal/get-subscription-tenant-id):
+- **Get the tenant ID**. Follow the steps in [Get the tenant ID of your Microsoft Entra tenant through the Azure portal](/azure/azure-portal/get-subscription-tenant-id):
 
    1. In the Azure portal, go to **Microsoft Entra ID** > **Properties**.
 
    1. Scroll down to the Tenant ID section and copy the **Tenant ID** value to use later.
 
-1. **Verify permissions**. As you register machines as Arc resources, make sure that you're either the resource group owner or have the following permissions on the resource group where the machines are provisioned:
+- **Verify permissions**. As you register machines as Arc resources, make sure that you're either the resource group owner or have the following permissions on the resource group where the machines are provisioned:
 
    - `Azure Connected Machine Onboarding`.
    - `Azure Connected Machine Resource Administrator`.
@@ -51,7 +51,7 @@ ms.lastreviewed: 03/20/2025
 
    1. In the right-pane, go to **Role assignments**. Verify that you have `Azure Connected Machine Onboarding` and `Azure Connected Machine Resource Administrator` roles assigned.
 
-1. Check your Azure policies. Make sure that:
+- Check your Azure policies. Make sure that:
     - The Azure policies aren't blocking the installation of extensions.
     - The Azure policies aren't blocking the creation of certain resource types in a resource group.
     - The Azure policies aren't blocking the resource deployment in certain locations.
diff --git a/azure-local/known-issues.md b/azure-local/known-issues.md
@@ -66,17 +66,15 @@ The following table lists the known issues in this release:
 | Azure Local VMs <!--ADO--> | Unable to delete an Arc VM when one of the nodes are down.| Contact Microsoft Support if this issue occurs.|
 | Azure Local VMs <!--ADO--> | Checkpoints on Azure Local VMs cause sync issues between Azure Local VMs and Portal. | Remove any checkpoints on the VM. |
 
-|Feature  |Issue  |Workaround  |
-|---------|---------|---------|
-| Deployment | During the Azure Local deployment, `DeviceManagementExtension` fails to install when a proxy is configured. | Install previous `DeviceManangementExtension` version 1.2502.0.3012 when using a proxy. |
-| Operating system  | Restoring the registry using *RegBack* isn't supported on Azure Local. This operation can remove the Lifecycle Manager (LCM) and Microsoft On-premises Cloud (MOC) settings on your Azure Local instance, which can corrupt the solution.  | |
 
 ## Known issues from previous releases
 
 The following table lists the known issues from previous releases:
 
 |Feature  |Issue  |Workaround  |
 |---------|---------|---------|
+| Deployment | During the Azure Local deployment, `DeviceManagementExtension` fails to install when a proxy is configured. | Install previous `DeviceManangementExtension` version 1.2502.0.3012 when using a proxy. |
+| Operating system  | Restoring the registry using *RegBack* isn't supported on Azure Local. This operation can remove the Lifecycle Manager (LCM) and Microsoft On-premises Cloud (MOC) settings on your Azure Local instance, which can corrupt the solution.  | |
 | Update  | When monitoring update progress in the Azure Update Management portal, the progress might appear to not have updated for several hours. | Run `Get-SolutionUpdate` on one of the cluster nodes. If an update object is returned, the update might be taking longer than expected but it is progressing. If an update object is not returned, the update may be stalled. For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/Get-SolutionUpdate-GatewayTimeout.md).|
 | Deployment | Validation times out due to timestamp deserialization. | When deploying the operating system, select **English (United States)** as the installation language, as well as the time and currency format. <br> For detailed remediation steps, see the troubleshooting guide in the [Azure Local Supportability](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Deployment/Triggering-deployment-settings-validation-call-results-in-OperationTimeout-2411-1-and-LCM-Extension-2411-1.md) GitHub repository.|
 | Update <!--30345067--> | When updating from version 2408.2.7 to 2411.0.24, the update process could fail with the following error message: `Type 'CauPreRequisites' of Role 'CAU' raised an exception: Could not finish cau prerequisites due to error 'Cannot remove item C:\UpdateDistribution\<any_file_name>: Access to the path is denied.'` |For detailed steps on how to mitigate this issue, see [Azure Local Troubleshooting Guide for Update](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/mitigation-for-cannot-remove-c-update-distribution-with-access-denied.md).|
