Revert changes to main-config app, docfx, KI

Author: Manika Dhiman

azure-local/deploy/deployment-arc-register-configurator-app.md

@@ -4,7 +4,7 @@ description: Learn how to use the Configurator app to bootstrap and quickly regi
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 05/23/2025
+ms.date: 05/22/2025
 ms.service: azure-local
 #CustomerIntent: As an IT Pro, I want to bootstrap and Arc register Azure Local machines via the Arc registration script.
 ---
@@ -28,6 +28,7 @@ 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)]
 
 - Download the [Configurator App for Azure Local](https://aka.ms/ConfiguratorAppForHCI).
+
 - Note down:
 
    - The serial number for each machine.
@@ -150,7 +151,7 @@ Follow these steps to configure network settings and connect the machines to Azu
 
 1. On the resource group used to bootstrap, you should see your Arc-enabled machines. In this example, you see a single machine.
 
-   :::image type="content" source="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png" alt-text="Screenshot that shows the Azure Arc agent Arc-enabled servers in Azure portal for Azure Local." lightbox="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png":::
+   :::image type="content" source="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png" alt-text="Screenshot that shows the Azure Arc agent Arc-enabled servers in Azure portal for Azure Local ." lightbox="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png":::
 
 ## Troubleshooting
 
@@ -193,11 +194,11 @@ Here's a table that describes the diagnostic tests:
 
 ### Collect a Support log package from the app
 
-A Support log package is composed of all the relevant logs that can help Microsoft Support troubleshoot any machine issues. You can generate a Support package via the app.
+A Support package is composed of all the relevant logs that can help Microsoft Support troubleshoot any machine issues. You can generate a Support package via the app.
 
 #### Download the Support log package
 
-Follow these steps to collect and download a Support log package:
+Follow these steps to collect and download a Support package:
 
 1. Select the help icon in the top-right corner of the app to open the **Support + troubleshooting** pane. Select **Create** to begin support package collection. The package collection could take several minutes.
 
@@ -207,25 +208,38 @@ Follow these steps to collect and download a Support log package:
 
 #### Upload the Support log package
 
-> [!IMPORTANT]
-> - Make sure to run the Configurator app as an administrator to upload the Support log package.
-> - Uploading the Support log package to Microsoft can take up to 20 minutes. Make sure to leave the app open and running to complete this process.
-
-Collect a Support log package before you upload it. Follow these steps to upload the Support log package to Microsoft:
+>[!IMPORTANT]
+> Uploading the Support package to Microsoft can take up to 20 minutes. Make sure to leave the app open and running to complete this process.
 
+Follow these steps to upload the Support package to Microsoft:
 1. Select the help icon in the top-right corner of the app to open the **Support + troubleshooting** pane. Select **Upload** to upload the Support package to Microsoft.
 
    :::image type="content" source="media/deployment-arc-register-configurator-app/upload-support-package-1.png" alt-text="Screenshot that shows the Support and troubleshooting pane with Upload package selected." lightbox="media/deployment-arc-register-configurator-app/upload-support-package-1.png":::
 
-1. Provide the required information in the **Upload Support package to Microsoft** dialog:
+1. Provide the required information in the **Upload Support package** dialog:
 
    :::image type="content" source="media/deployment-arc-register-configurator-app/upload-support-package-2.png" alt-text="Screenshot that shows the Upload Support Package dialog filled out." lightbox="media/deployment-arc-register-configurator-app/upload-support-package-2.png":::
 
-   The fields in the dialog are prepopulated with the information you provided during [Step 1: Configure the network and connect to Azure](#step-1-configure-the-network-and-connect-to-azure). You can modify the fields as needed.
+    1. The **Cloud type** is populated automatically as `Azure`.
+   
+    1. Enter a **Subscription ID** to register the machine.
+
+    1. Provide a **Resource group** name. This resource group contains the machine and system resources that you create.
+
+    1. Specify the **Region** where you want to create the resources. The region should be the same as the region where you want to deploy the Azure Local instance.
+
+       > [!IMPORTANT]
+       > Specify the region with spaces removed. For example, specify the East US region as `EastUS`.
+
+    1. Provide a **Tenant ID**. The tenant ID is the directory ID of your Microsoft Entra tenant. To get the tenant ID, see [Find your Microsoft Entra tenant](/azure/azure-portal/get-subscription-tenant-id).
+
+    1. If you set up an Azure Arc gateway, specify the Arc gateway ID. This is the resource ID of the Arc gateway that you set up. For more information, see [About Azure Arc gateways](./deployment-azure-arc-gateway-overview.md).
 
+       > [!IMPORTANT]
+       > Make sure to verify all the inputs before you proceed. Any incorrect inputs here might result in an upload failure.
 
-   1. Select **Begin upload** to upload the Support package.
-   1. Authenticate in the browser with the same account that you used to sign in to register with Azure Arc. The upload process might take several minutes. Leave the app open and running until the upload is complete.
+   1. Select **Upload** to upload the Support package.
+   1. Authenticate in the browser with the same account that you used to sign in to the Configurator app. The upload process might take several minutes.
 
        :::image type="content" source="media/deployment-arc-register-configurator-app/upload-support-package-3.png" alt-text="Screenshot that shows the Support and troubleshooting pane with Upload selected and authentication guidance." lightbox="media/deployment-arc-register-configurator-app/upload-support-package-3.png":::
 
@@ -243,4 +257,4 @@ If you have more than one version of the app installed, when you try to open the
 
 - After your machines are registered with Azure Arc, proceed to deploy your Azure Local system via one of the following options:
     - [Deploy via Azure portal](./deploy-via-portal.md).
-    - [Deploy via ARM template](./deployment-azure-resource-manager-template.md).
+    - [Deploy via ARM template](./deployment-azure-resource-manager-template.md).

azure-local/docfx.json

@@ -86,14 +86,14 @@
     },
     "fileMetadata": {
       "monikerRange": {
-      "./*.md": ">=azloc-24111 || =azloc-previous",
-      "./*.yml": ">=azloc-24111 || =azloc-previous"
+      "./*.md": ">=azloc-2411 || =azloc-previous",
+      "./*.yml": ">=azloc-2411 || =azloc-previous"
       }
     },
     "template": [],
     "groups": {
       "version-azlocal": {
-        "moniker_range": ">=azloc-24111 || =azloc-previous",
+        "moniker_range": ">=azloc-2411 || =azloc-previous",
         "dest": "azure-local"
       }
     }

azure-local/known-issues.md

@@ -344,7 +344,7 @@ The following table lists the known issues from previous releases:
 
 ::: moniker-end
 
-::: moniker range="=azloc-previous"
+::: moniker range="=azloc-2411"
 
 ## Known issues for version 2411
 
@@ -397,6 +397,10 @@ The following table lists the known issues from previous releases:
 | Update | When updating the Azure Local instance via the Azure Update Manager, the update progress and results may not be visible in the Azure portal.| To work around this issue, on each node, add the following registry key (no value needed):<br><br>`New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Services\HciCloudManagementSvc\Parameters" -force`</br><br> Then on one of the nodes, restart the Cloud Management cluster group. </br><br>`Stop-ClusterGroup "Cloud Management"`</br><br>`Start-ClusterGroup "Cloud Management"`</br><br> This won't fully remediate the issue as the progress details may still not be displayed for a duration of the update process. To get the latest update details, you can [Retrieve the update progress with PowerShell](./update/update-via-powershell-23h2.md#step-6-track-update-progress). |
 | Update <!--26659432--> |In some cases, `SolutionUpdate` commands could fail if run after the `Send-DiagnosticData` command.  | Make sure to close the PowerShell session used for `Send-DiagnosticData`. Open a new PowerShell session and use it for `SolutionUpdate` commands.|
 
+::: moniker-end
+
+::: moniker range="=azloc-previous"
+
 ## Known issues for version 2408.2
 
 This software release maps to software version number **2408.2.7**.
@@ -1206,4 +1210,4 @@ Here are the known issues from previous releases:
 
 ## Next steps
 
-- Read the [Deployment overview](./deploy/deployment-introduction.md).
+- Read the [Deployment overview](./deploy/deployment-introduction.md).