Sync release-local-2506 with main

Sync release-local-2506 with main

Author: sethmanheim

AKS-Arc/ssh-connect-to-windows-and-linux-worker-nodes.md

@@ -1,12 +1,12 @@
 ---
 title: Connect to Windows or Linux worker nodes with SSH
 description: Learn how to use SSH to connect to Windows or Linux worker nodes in an AKS Arc cluster.
-ms.date: 01/10/2025
+ms.date: 07/02/2025
 ms.topic: how-to
 author: sethmanheim
 ms.author: sethm
 ms.reviewer: leslielin
-ms.lastreviewed: 01/10/2025
+ms.lastreviewed: 07/02/2025
 ---
 
 # Connect to Windows or Linux worker nodes with SSH
@@ -17,6 +17,28 @@ During your AKS Arc cluster's lifecycle, you might need to directly access clust
 
 This article explains how to use SSH to connect to both Windows and Linux nodes.
 
+## Prerequisites
+
+### **Install the Kubernetes CLI**
+
+You can use the Kubernetes CLI, [**kubectl**](https://kubernetes.io/docs/reference/kubectl/), to connect to your Kubernetes cluster. If you use Azure Cloud Shell, **kubectl** is already installed. If you run the commands locally, you can use the Azure CLI or Azure PowerShell to install **kubectl**.
+
+### [Azure CLI](#tab/azure-cli)
+
+* Install **kubectl** locally using the [`az aks install-cli`](/cli/azure/aks?view=azure-cli-latest&preserve-view=true#az-aks-install-cli) command:
+
+  ```azurecli-interactive
+  az aks install-cli
+  ```
+
+### [Azure PowerShell](#tab/azure-powershell)
+
+* Install **kubectl** locally using the [`Install-AzAksCliTool`](/powershell/module/az.aks/install-azaksclitool?view=azps-14.2.0&preserve-view=true) cmdlet:
+
+  ```azurepowershell-interactive
+  Install-AzAksCliTool
+  ```
+
 ## Use SSH to connect to worker nodes
 
 1. To access the Kubernetes cluster with the specified permissions, you must retrieve the certificate-based admin **kubeconfig** file using the [az aksarc get-credentials](/cli/azure/aksarc#az-aksarc-get-credentials) command. For more information, see [Retrieve certificate-based admin kubeconfig](retrieve-admin-kubeconfig.md):
@@ -28,7 +50,7 @@ This article explains how to use SSH to connect to both Windows and Linux nodes.
 1. Run **kubectl get** to obtain the node's IP address and capture its IP value in order to sign in to a Windows or Linux worker node using SSH:
 
    ```azurecli
-   kubectl --kubeconfig /path/to/aks-cluster-kubeconfig get nodes -o wide |
+   kubectl --kubeconfig /path/to/aks-cluster-kubeconfig get nodes -o wide
    ```
 
 1. Run `ssh` to connect to a worker node:

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

@@ -12,7 +12,7 @@ ms.service: azure-local
 
 ::: moniker range=">=azloc-24111"
 
-Applies to: Azure Local 2411.1 and later
+Applies to: Azure Local 2411, 2503 and 2504 new deployments. Starting with 2505, there is no need to configure the proxy manually anymore. Please refer to [Deploy with Arc gateway via Arc script](deployment-azure-arc-gateway-configure-via-script.md) if you are using an enterprise proxy, or refer to [Deploy with Arc gateway without proxy](deployment-azure-arc-gateway-use-without-proxy.md) if you don't use an enterprise proxy.
 
 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.
 

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

@@ -10,9 +10,9 @@ ms.service: azure-local
 
 # Configure Arc proxy via registration script for Azure gateway on Azure Local (preview)
 
-::: moniker range=">=azloc-24111"
+::: moniker range=">=azloc-2505"
 
-Applies to: Azure Local 2411.1 and later
+Applies to: Azure Local 2505 and later
 
 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.
 
@@ -24,7 +24,7 @@ Using this method, you don't need to configure the Arc proxy across WinInet, Win
 
 Make sure the following prerequisites are met before proceeding:
 
-- You've access to an Azure Local instance running release 2411.1 or later. Prior versions do not support this scenario.
+- You've access to an Azure Local instance running release 2505 or later. Prior versions do not support this scenario.
 
 - 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).
 
@@ -34,8 +34,7 @@ You need the proxy and the ArcGatewayID from Azure to run the registration scrip
 
 ## Step 2: Register new machines in Azure Arc
 
-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.
+To register version 2505 or later Azure Local machines in Azure Arc, you run the initialization script by passing the `ArcGatewayID`, `Proxy server`, and `Proxy bypass list` parameters. During the bootstrap configuration you will be required to authenticate with your credentials using the device code.
 
 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:
 
@@ -46,9 +45,6 @@ $Subscription = "yoursubscription"
 #Define the resource group where you want to register your server as Arc device.
 $RG = "yourresourcegroupname" 
 
-#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" 
 
@@ -64,17 +60,8 @@ $ArcgwId = "/subscriptions/yourarcgatewayid/resourceGroups/yourresourcegroupname
 
 $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 
-
-#Get the Access Token and Account ID for the registration 
-$ARMtoken = (Get-AzAccessToken).Token 
-
-#Get the Account ID for the registration 
-$id = (Get-AzContext).Account.Id 
-
 #Invoke the registration script with Proxy and ArcgatewayID 
-Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region australiaeast -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id -Proxy $ProxyServer -ArcGatewayID $ArcgwId -ProxyBypass $ProxyBypassList 
+Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -Region australiaeast -Cloud "AzureCloud" -Proxy $ProxyServer -ArcGatewayID $ArcgwId -ProxyBypass $ProxyBypassList 
 ```
 
 ## Step 3: Verify that the setup succeeded

azure-local/deploy/deployment-azure-arc-gateway-use-without-proxy.md

@@ -10,9 +10,9 @@ ms.service: azure-local
 
 # Use Azure Arc gateway without a proxy on Azure Local (preview)
 
-::: moniker range=">=azloc-24111"
+::: moniker range=">=azloc-2505"
 
-> Applies to: Azure Local 2411.1 and later
+> Applies to: Azure Local 2505 and later
 
 After creating the Arc gateway resource in your Azure subscription, you can enable the new Arc gateway preview features on your Azure Local. This article details how to use Azure gateway for Azure Local instances without a proxy.
 
@@ -44,23 +44,11 @@ $Subscription = "yoursubscription"
 #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 server as Arc device.
-$Tenant = "yourtenant"
- 
 #Define the Arc gateway resource ID from Azure
 $ArcgwId = "/subscriptions/yourarcgatewayid/resourceGroups/yourresourcegroupname/providers/Microsoft.HybridCompute/gateways/yourarcgatewayname"
 
-#Connect to your Azure account and Subscription
-Connect-AzAccount -SubscriptionId $Subscription -TenantId $Tenant -DeviceCode
-
-#Get the Access Token and Account ID for the registration
-$ARMtoken = (Get-AzAccessToken).Token
-
-#Get the Account ID for the registration
-$id = (Get-AzContext).Account.Id
-
 #Invoke the registration script with Proxy and ArcgatewayID
-Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region australiaeast -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id -ArcGatewayID $ArcgwId
+Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -Region australiaeast -Cloud "AzureCloud" -ArcGatewayID $ArcgwId
 ```
 
 ## Step 3: Start Azure Local cloud deployment

azure-local/manage/gpu-manage-via-partitioning.md

@@ -39,7 +39,7 @@ Consider the following limitations when using the GPU-P feature:
 
 ## Prerequisites
 
-- See [Prepare GPUs for Azure Local](./gpu-manage-via-partitioning.md) for requirements and to prepare your Azure Local VMs, and to ensure that your GPUs are prepared and partitioned.
+- See [Prepare GPUs for Azure Local](gpu-preparation.md) for requirements and to prepare your Azure Local VMs, and to ensure that your GPUs are prepared and partitioned.
 
 ## Attach a GPU during Azure Local VM creation
 

azure-local/manage/media/troubleshoot-arc-enabled-vms/temporary-paging-file-1.png

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Local Virtual Machines enabled by Azure Arc
 description: Learn how to troubleshoot issues you experience with Azure Local Virtual Machines (VMs).
 author: alkohli
 ms.topic: how-to
-ms.date: 05/29/2025
+ms.date: 06/16/2025
 ms.author: alkohli
 ms.reviewer: vlakshmanan
 ms.service: azure-local
@@ -162,8 +162,31 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
         }
 ```
 
+## "Windows created a temporary paging file" message appears at startup
 
+**Error:**
+
+When you deploy an Azure Local VM using the SQL Server 2022 on Windows Server 2022 Azure marketplace images (Standard or Enterprise), you might see the following warning at startup:
+
+*Windows created a temporary paging file...*
+
+**Resolution:**
+
+To resolve this issue, follow these steps:
+
+1. Select **OK** on the warning popup. Or, go to **System Properties** > **Advanced** > **Performance** > **Settings** to open the **Performance Options** window.
+1. In the **Performance Options** window, select **Change** under the **Virtual memory** section.
+
+    :::image type="content" source="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-1.png" alt-text="Screenshot of the Performance Options window highlighting the Change button." lightbox="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-1.png":::
+
+1. In the **Virtual Memory** window, select **System managed size**.  Also ensure that the **Automatically manage paging file size for all drives** checkbox is cleared.
+
+    :::image type="content" source="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-2.png" alt-text="Screenshot of the Virtual Memory window showing options to configure the paging file size for each drive." lightbox="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-2.png":::
+
+1. Select **Set**, then select **OK** to apply the changes.
+
+1. Restart the VM. After the restart, the warning message should no longer appear.
 
 ## Next steps
 
-- [Azure Local VM management FAQs](./azure-arc-vms-faq.yml)
+- [Azure Local VM management FAQs](./azure-arc-vms-faq.yml)

azure-local/manage/media/troubleshoot-arc-enabled-vms/temporary-paging-file-2.png

@@ -1,14 +1,14 @@
 ---
-title: What's New for Azure Migrate on Azure Local
+title: What's new for Azure Migrate to Azure Local
 description: Learn about new features for Azure Migrate on Azure Local.
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 06/27/2025
+ms.date: 07/02/2025
 ms.service: azure-local
 ---
 
-# What's new for VM migration on Azure Local
+# What's new for Azure Migrate to Azure Local
 
 This article lists the various features and improvements that are available in VM migration to Azure Local.
 
@@ -17,10 +17,10 @@ This article lists the various features and improvements that are available in V
 
 This release includes these features and improvements:
 
-- Improved service error messages, recommended actions, and [troubleshooting guidance](./migrate-troubleshoot.md).
-- Fixed a bug that shows `Not Found` errors for missing Azure Local resources.
-- Updated appliance error messages to correctly identify which migrate appliance is unresponsive.
-- Enabled static IP migrations to support multiple IP pools on a single logical network.
+- **Improved error messaging** - Improved service error messaging, recommended actions, and [troubleshooting guidance](./migrate-troubleshoot.md).
+- **Bug fix for missing resources** – Fixed bug to surface `NotFound` errors for missing Azure Local resources.
+- **Appliance error improvements** – Updated appliance error messages to correctly identify which migrate appliance is unresponsive.
+- **Static IP support enhancements** – Enabled static IP migrations to support multiple IP pools on a single logical network.
 
 
 ## April 2025

azure-local/manage/troubleshoot-arc-enabled-vms.md

@@ -18,6 +18,8 @@
         items:
         - name: 2501
           items:
+          - name: Hotfix 1.2501.1.47
+            href: hotfix-1-2501-1-47.md
           - name: Hotfix 1.2501.1.40
             href: hotfix-1-2501-1-40.md
         - name: 2408