Merge pull request #16333 from v-sissondan/arc-gateway

Arc gateway updates

Author: v-shils

azure-local/deploy/deployment-azure-arc-gateway-configure-manually.md

@@ -3,14 +3,14 @@ title: Configure Arc proxy manually for Azure gateway on Azure Local, version 24
 description: Learn how to configure Arc proxy manually for Azure gateway on Azure Local, version 2408 and 2408.1 (preview). 
 author: alkohli
 ms.topic: how-to
-ms.date: 10/15/2024
+ms.date: 11/18/2024
 ms.author: alkohli
 ms.service: azure-stack-hci
 ---
 
 # Configure Arc proxy manually for Azure gateway on Azure Local (preview)
 
-Applies to: Azure Local, version 23H2, release 2408.1 and 2408
+Applies to: Azure Local, version 23H2, release 2408, 2408.1, 2408.2, and 2411
 
 After creating the Arc gateway resource in your Azure subscription, you can enable the new Arc gateway preview features. This article details how to manually configure the Arc proxy before Arc registration.
 
@@ -20,86 +20,46 @@ After creating the Arc gateway resource in your Azure subscription, you can enab
 
 Make sure the following prerequisites are met before proceeding:
 
-- You’ve access to an Azure Local, version 23H2 system.
+- You’ve access to an Azure Local instance running version 23H2.
 
 - An Arc gateway resource created in the same subscription as used to deploy Azure Local. For more information, see [Create the Arc gateway resource in Azure](deployment-azure-arc-gateway-overview.md#create-the-arc-gateway-resource-in-azure).
 
-> [!Warning]
-> Only the standard ISO OS image available at https://aka.ms/PVenEREWEEW should be used to test the Arc gateway public preview on Azure Local, version 2408. Do not use the ISO image available in Azure portal.
-
-## Step 1: Manually configure the proxy on each node
+## Step 1: Manually configure the proxy
 
 If you need to configure the Arc proxy on your Azure Local machines before starting the Arc registration process, follow the instructions at [Configure proxy settings for Azure Local, version 23H2](../manage/configure-proxy-settings-23h2.md).
 
 Ensure that you configure the proxy and the bypass list for all the machines on your system.
 
 ## Step 2: Get the ArcGatewayID  
 
-You need the proxy and the Arc gateway ID (ArcGatewayID) from Azure to run the registration script on Azure Local machines. To get the ArcGatewayID, run the following `az connectedmachine gateway list` command from any computer that is not an Azure Local machine.
-
-Here's an example:
-
-```azurecli
-PS C:\> az connectedmachine gateway list 
-
-This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus 
-
-[ 
-  { 
-    "allowedFeatures": [ 
-      "*" 
-    ], 
-    "gatewayEndpoint": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx.gw.arc.azure.com", 
-    "gatewayId": "xxxxxxx-xxxx-xxx-xxxx-xxxxxxxxx", 
-    "gatewayType": "Public", 
-    "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/resourceGroups/yourresourcegroup/providers/Microsoft.HybridCompute/gateways/yourArcgateway", 
-    "location": "eastus", 
-    "name": " yourArcgateway", 
-    "provisioningState": "Succeeded", 
-    "resourceGroup": "yourresourcegroup", 
-    "type": "Microsoft.HybridCompute/gateways" 
-  } 
-] 
-```
+You need the proxy and the Arc gateway ID (ArcGatewayID) from Azure to run the registration script on Azure Local machines. You can find the Arc gateway ID on the Azure portal overview page of the resource.
 
 ## Step 3: Register new machines in Azure Arc
 
-You run the initialization script by passing the ArcGatewayID parameter and the proxy server parameters. Here's an example of how you should change the `Invoke-AzStackHciArcInitialization` parameters on the initialization script:
+To register new version 2408 or version 2411 machines in Azure Arc, you run the initialization script by passing the ArcGatewayID parameter and the proxy server parameters. Here's an example of how you should change the `Invoke-AzStackHciArcInitialization` parameters on the initialization script:
 
 ```azurecli
-#Install required PowerShell modules in your machine for registration 
-
-Install-Module Az.Accounts -RequiredVersion 2.13.2 
-
-Install-Module Az.Resources -RequiredVersion 6.12.0 
-
-Install-Module Az.ConnectedMachine -RequiredVersion 0.5.2 
-
-#Install Arc registration script from PSGallery  
-
-Install-Module AzsHCI.ARCinstaller 
-
-#Define the subscription where you want to register your machine as Arc device 
+#Define the subscription where you want to register your server as Arc device. 
 
-$Subscription = "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx" 
+$Subscription = "yoursubscription>" 
 
-#Define the resource group where you want to register your machine as Arc device 
+#Define the resource group where you want to register your server as Arc device.
 
 $RG = "yourresourcegroupname" 
 
-#Define the tenant you will use to register your machine as Arc device 
+#Define the tenant you will use to register your server as Arc device. 
 
-$Tenant = "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx" 
+$Tenant = "yourtenant" 
 
 #Define Proxy Server if necessary 
 
 $ProxyServer = "http://x.x.x.x:port" 
 
 #Define the Arc gateway resource ID from Azure 
 
-$ArcgwId = "/subscriptions/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx /resourceGroups/ yourresourcegroupname /providers/Microsoft.HybridCompute/gateways/yourarcgatewayname" 
+$ArcgwId = "/subscriptions/yoursubscription/resourceGroups/yourresourcegroupname/providers/Microsoft.HybridCompute/gateways/yourarcgatewayname" 
 
-#Connect to your Azure account and Subscription 
+#Connect to your Azure account and subscription 
 
 Connect-AzAccount -SubscriptionId $Subscription -TenantId $Tenant -DeviceCode 
 
@@ -126,7 +86,7 @@ Once the Azure Local machines are registered in Azure Arc and all the extensions
 
 ## Step 5: Verify that the setup succeeded
 
-Once the deployment validation starts, you can connect to the first Azure Local machine from your machine and open the Arc gateway log to monitor which endpoints are redirected to the Arc gateway and which ones continue using your firewall or proxy.
+Once the deployment validation starts, you can connect to the first Azure Local machine from your system and open the Arc gateway log to monitor which endpoints are redirected to the Arc gateway and which ones continue using your firewall or proxy.
 
 You can find the Arc gateway log at: *c:\programdata\AzureConnectedMAchineAgent\Log\arcproxy.log*.
 
@@ -136,7 +96,7 @@ To check the Arc agent configuration and verify that it is using the Arc gateway
 
 The result should show the following values:
 
-- **Agent version** is **1.45**.
+- **Agent version** is **1.45** or above.
 
 - **Agent Status** is **Connected**.
 

azure-local/deploy/deployment-azure-arc-gateway-configure-via-script.md

@@ -3,14 +3,14 @@ title: Configure Arc proxy via registration script for Azure gateway on Azure Lo
 description: Learn how to Configure Arc proxy via registration script for Azure gateway on Azure Local, version 2408 (preview). 
 author: alkohli
 ms.topic: how-to
-ms.date: 10/16/2024
+ms.date: 11/18/2024
 ms.author: alkohli
 ms.service: azure-stack-hci
 ---
 
 # Configure Arc proxy via registration script for Azure gateway on Azure Local (preview)
 
-Applies to: Azure Local, version 23H2, release 2408.1 and 2408
+Applies to: Azure Local, version 23H2, release 2408, 2408.1, 2408.2, and 2411
 
 After creating the Arc gateway resource in your Azure subscription, you can enable the new Arc gateway preview features. This article details how to configure the Arc proxy before Arc registration using a registration script for the Arc gateway on Azure Local.
 
@@ -26,63 +26,32 @@ Make sure the following prerequisites are met before proceeding:
 
 - An Arc gateway resource created in the same subscription as used to deploy Azure Local. For more information, see [Create the Arc gateway resource in Azure](deployment-azure-arc-gateway-overview.md#create-the-arc-gateway-resource-in-azure).
 
-> [!Warning]
-> Only the standard ISO OS image available at https://aka.ms/PVenEREWEEW should be used to test the Arc gateway public preview on Azure Local, version 2408. Do not use the ISO image available in Azure portal.
-
 ## Step 1: Get the ArcGatewayID  
 
-You need the proxy and the ArcGatewayID from Azure to run the registration script on Azure Local machine. To get the ArcGatewayID value, run the `az connectedmachine gateway list` command described previously. Do not run this command from any Azure Local machines:
-
-```azurecli
-PS C:\> az connectedmachine gateway list 
-This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus 
-[ 
-  { 
-    "allowedFeatures": [ 
-      "*" 
-    ], 
-    "gatewayEndpoint": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx.gw.arc.azure.com", 
-    "gatewayId": "xxxxxxx-xxxx-xxx-xxxx-xxxxxxxxx", 
-    "gatewayType": "Public", 
-    "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/resourceGroups/yourresourcegroup/providers/Microsoft.HybridCompute/gateways/yourArcgateway", 
-    "location": "eastus", 
-    "name": " yourArcgateway", 
-    "provisioningState": "Succeeded", 
-    "resourceGroup": "yourresourcegroup", 
-    "type": "Microsoft.HybridCompute/gateways" 
-  } 
-] 
-```
+You need the proxy and the ArcGatewayID from Azure to run the registration script on Azure Local machines. You can find the Arc gateway id on the Azure portal overview page of the resource.
 
-## Step 2: Register new Azure Local machines running version 2408
+## Step 2: Register new machines in Azure Arc
 
-You can run the initialization script by passing the `ArcGatewayID`, `Proxy server`, and `Proxy bypass list` parameters.
+To register new version 2408 or version 2411 machines in Azure Arc, you run
+the initialization script by passing the `ArcGatewayID`, `Proxy server`, and `Proxy bypass list` parameters.
 
 Here's an example of how you should change these parameters for the `Invoke-AzStackHciArcInitialization` initialization script. Once registration is completed, the Azure Local machines are registered in Azure Arc using the Arc gateway:
 
 ```azurecli
-#Install required PowerShell modules in your machine for registration 
-Install-Module Az.Accounts -RequiredVersion 2.13.2 
-Install-Module Az.Resources -RequiredVersion 6.12.0 
-Install-Module Az.ConnectedMachine -RequiredVersion 0.5.2 
-
-#Install Arc registration script from PSGallery  
-Install-Module AzsHCI.ARCinstaller 
-
-#Define the subscription where you want to register your machine as Arc device 
-$Subscription = "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx" 
+#Define the subscription where you want to register your server as Arc device.
+$Subscription = "yoursubscription" 
 
-#Define the resource group where you want to register your machine as Arc device 
+#Define the resource group where you want to register your server as Arc device.
 $RG = "yourresourcegroupname" 
 
-#Define the tenant to use to register your machine as Arc device 
-$Tenant = "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx" 
+#Define the tenant to use to register your server as Arc device. 
+$Tenant = "yourtenant" 
 
 #Define Proxy Server if necessary 
 $ProxyServer = "http://x.x.x.x:port" 
 
 #Define the Arc gateway resource ID from Azure 
-$ArcgwId = "/subscriptions/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx /resourceGroups/ yourresourcegroupname /providers/Microsoft.HybridCompute/gateways/yourarcgatewayname" 
+$ArcgwId = "/subscriptions/yourarcgatewayid/resourceGroups/yourresourcegroupname/providers/Microsoft.HybridCompute/gateways/yourarcgatewayname" 
 
 #Define the bypass list for the proxy. Use semicolon to separate each item from the list.  
 # Use "localhost" instead of <local> 
@@ -91,7 +60,7 @@ $ArcgwId = "/subscriptions/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx /resourceGroups/ yo
 # Append * for domain names exclusions like *.contoso.com 
 # DO NOT INCLUDE .svc on the list. The registration script takes care of Environment Variables configuration. 
 
-$ProxyBypassList = "localhost;127.0.0.1;*.contoso.com;Node1;Node2;Node3;Node4;Node5;192.168.*.*;HCI-cluster1"
+$ProxyBypassList = "localhost;127.0.0.1;*.contoso.com;machine1;machine2;machine3;machine4;machine5;192.168.*.*;AzureLocal-1" 
 
 #Connect to your Azure account and Subscription 
 Connect-AzAccount -SubscriptionId $Subscription -TenantId $Tenant -DeviceCode 
@@ -118,7 +87,7 @@ To check the Arc agent configuration and verify that it is using the gateway, ru
 
 The values displayed should be as follows:
 
-- **Agent version** is **1.45**.
+- **Agent version** is **1.45** or above.
 
 - **Agent Status** should show as **Connected**.