Merge pull request #3627 from MicrosoftDocs/main638816296391944166sync_temp

learn-build-service-prod[bot] · web-flow · commit 9510d2d86ae5 · 2025-04-30T17:07:41.000Z
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -1316,6 +1316,11 @@
       "redirect_url": "/azure/azure-managed-lustre/client-install?pivots=ubuntu-22",
       "redirect_document_id": false
     },
+    {
+      "source_path": "azure-managed-lustre/install-ubuntu-24.md",
+      "redirect_url": "/azure/azure-managed-lustre/client-install?pivots=ubuntu-24",
+      "redirect_document_id": false
+    },
     {
       "source_path": "azure-stack/hci/get-started.md",
       "redirect_url": "/azure-stack/hci/manage/monitor-cluster",
diff --git a/azure-local/deploy/deployment-arc-register-configurator-app.md b/azure-local/deploy/deployment-arc-register-configurator-app.md
@@ -4,7 +4,7 @@ description: Learn how to use the Configurator application to bootstrap and Arc
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 03/20/2025
+ms.date: 04/30/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.
 ---
@@ -95,7 +95,7 @@ Follow these steps to configure network settings and connect the machines to Azu
 
    1. Select **ON** to enable **Remote desktop** protocol. Remote desktop protocol is disabled by default.
 
-   1. Select **Public endpoint** or **Proxy server** as the connectivity method. If selecting a proxy server, provide the proxy URL and the bypass list.
+   1. Select **Public endpoint** or **Proxy server** as the connectivity method. If selecting a proxy server, provide the proxy URL and the bypass list. The bypass list is required and can be provided in a comma separated format.
 
    1. Select a time zone.
 
diff --git a/azure-local/includes/hci-registration-azure-prerequisites.md b/azure-local/includes/hci-registration-azure-prerequisites.md
@@ -3,7 +3,7 @@ author: alkohli
 ms.author: alkohli
 ms.service: azure-local
 ms.topic: include
-ms.date: 04/16/2025
+ms.date: 04/30/2025
 ms.reviewer: alkohli
 ms.lastreviewed: 03/20/2025
 ---
@@ -14,16 +14,16 @@ ms.lastreviewed: 03/20/2025
    Run the following [PowerShell commands](/azure/azure-resource-manager/management/resource-providers-and-types#azure-powershell) to register:
 
    ```powershell
-   Register-ResourceProvider -ProviderNamespace "Microsoft.HybridCompute" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.GuestConfiguration" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.HybridConnectivity" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.AzureStackHCI" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.Kubernetes" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.KubernetesConfiguration" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.ExtendedLocation" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.ResourceConnector" 
-   Register-ResourceProvider -ProviderNamespace "Microsoft.HybridContainerService"
-   Register-ResourceProvider -ProviderNamespace "Microsoft.Attestation"
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.HybridCompute" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.GuestConfiguration" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.HybridConnectivity" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.AzureStackHCI" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.Kubernetes" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.KubernetesConfiguration" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.ExtendedLocation" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.ResourceConnector" 
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.HybridContainerService"
+   Register-AzResourceProvider -ProviderNamespace "Microsoft.Attestation"
    ```
 
     > [!NOTE]
diff --git a/azure-local/manage/gpu-manage-via-partitioning.md b/azure-local/manage/gpu-manage-via-partitioning.md
@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 03/26/2025
+ms.date: 04/29/2025
 ---
 
 # Manage GPUs using partitioning (preview)
@@ -33,7 +33,7 @@ Consider the following limitations when using the GPU-P feature:
 
 - Partitions are autoassigned to the VMs. You can't choose a specific partition for a specific VM.
 
-- Currently, GPU partitioning on Azure Local doesn't support live migration of VMs. But VMs can be automatically restarted and placed where GPU resources are available if there's a failure.
+- GPU partitioning on Azure Local supports live migration. However, the host and VMs must be on NVIDIA virtual GPU software version 18 and later. For more information, see [Microsoft Azure Local - NVIDIA Docs](https://docs.nvidia.com/vgpu/18.0/grid-vgpu-release-notes-microsoft-azure-stack-hci/index.html).
 
 - You can partition your GPU using Azure Command-Line Interface (CLI). We recommend that you use Azure CLI to configure and assign GPU partitions. You must manually ensure that the homogeneous configuration is maintained for GPUs across all the machines in your system.
 
@@ -43,7 +43,7 @@ Consider the following limitations when using the GPU-P feature:
 
 ## Attach a GPU during Azure Local VM creation
 
-Follow the steps outlined in [Create Azure Local virtual machines](create-arc-virtual-machines.md?tabs=azurecli) and utilize the additional hardware profile details to add GPU to your create process. Run the following:
+Follow the steps outlined in [Create Azure Local virtual machines](create-arc-virtual-machines.md?tabs=azurecli) and utilize the extra hardware profile details to add GPU to your create process. Run the following:
 
 ```azurecli
 az stack-hci-vm create --name $vmName --resource-group $resource_group --admin-username $userName --admin-password $password --computer-name $computerName --image $imageName --location $location --authentication-type all --nics $nicName --custom-location $customLocationID --hardware-profile memory-mb="8192" processors="4" --storage-path-id $storagePathId --gpus GpuP
@@ -65,7 +65,7 @@ You can specify the partition size in the command, as shown below. Partition siz
 az stack-hci-vm gpu attach --resource-group "test-rg" --custom-location "test-location" --vm-name "test-vm" --gpus GpuP
 ```
 
-After attaching the GPU partition, the output will show the full VM details. You can confirm the GPUs were attached by reviewing the hardware profile `virtualMachineGPUs` section. The output will look as follows:
+After attaching the GPU partition, the output shows the full VM details. You can confirm the GPUs were attached by reviewing the hardware profile `virtualMachineGPUs` section. The output looks as follows:
 
 ```azurecli
 "properties":{
@@ -89,7 +89,7 @@ Use the following CLI command to detach the GPU:
 az stack-hci-vm gpu detach --resource-group "test-rg" --custom-location "test-location" --vm-name "test-vm" --gpus GpuP
 ```
 
-After detaching the GPU partition, the output will show the full VM details. You can confirm the GPUs were detached by reviewing the hardware profile `virtualMachineGPUs`. The output will look as follows:
+After detaching the GPU partition, the output shows the full VM details. You can confirm the GPUs were detached by reviewing the hardware profile `virtualMachineGPUs`. The output looks as follows:
 
 ```azurecli
 "properties":{
diff --git a/azure-local/release-information-23h2.md b/azure-local/release-information-23h2.md
@@ -55,7 +55,7 @@ Follow these guidelines to update to each release within your current release tr
   |--------------------------------------|-------------------|
   | Nov 2024                             | 2411 --> 2411.1   |
   | December 2024 or later               | 2411.1 --> 2411.2 |
-  | February 2024                        | 2411.2 --> 2411.3 |
+  | February 2025                        | 2411.2 --> 2411.3 |
 
 - To keep your Azure Local instance in a supported state, you have up to six months to install updates. For example, if you're running the 2408 feature build, update to a later build within six months.
 
@@ -83,7 +83,7 @@ Starting in 2504, we offer two releases. One release provides the path to upgrad
 
 |Version| OS Build |Security update| What's new | Known issues |
 |------|-------|---------------|------------|--------------|
-| 12.2504.1001.20 <br><br> Availability date: 2025-04-23 | 26100.3775 | [April OS security update](security-update/security-update.md?view=azloc-2504&preserve-view=true) | [Features and improvements](./whats-new.md?view=azloc-2504&preserve-view=true#features-and-improvements-in-2504) | [Known issues](./known-issues.md?view=azloc-2504&preserve-view=true) | 
+| 12.2504.1001.20 <br><br> Availability date: 2025-04-29 | 26100.3775 | [April OS security update](security-update/security-update.md?view=azloc-2504&preserve-view=true) | [Features and improvements](./whats-new.md?view=azloc-2504&preserve-view=true#features-and-improvements-in-2504) | [Known issues](./known-issues.md?view=azloc-2504&preserve-view=true) |
 
 ---
 
diff --git a/azure-local/security-update/security-update.md b/azure-local/security-update/security-update.md
@@ -20,12 +20,10 @@ This article describes the OS security updates for Azure Local that were release
 
 For the 2504 release of Azure Local, Microsoft released two security updates: one for existing deployments and another for new deployments. The following table provides information about different deployment types, their corresponding security updates, and OS builds:
 
-
 | Deployment type  | Security update  | OS build  | Release date |
 |---------|---------|---------|---------|
 | Existing deployments    | KB5055527         | 25398.1551         | April 12, 2025        |
-| New deployments    | KB5055523         | 26100.3775         | April 30, 2025         |
-
+| New deployments    | KB5055523         | 26100.3775         | April 12, 2025         |
 
 # [Existing deployments](#tab/existing-deployments)
 
diff --git a/azure-local/whats-new.md b/azure-local/whats-new.md
@@ -40,19 +40,21 @@ This release has the following features and improvements:
 - **Registration and deployment changes**:
     - Starting with this release, you can download a specific version of Azure Local software instead of just the latest version. For each upcoming release, you can choose from up to last six supported versions. For more information, see [Download Azure Local software](./deploy/download-23h2-software.md).
     - The error logging in the registration script is enhanced.
+    - Proxy bypass list is now mandatory if a proxy configuration is specified.
 
 - **Security changes**: The Dynamic Root of Trust for Measurement (DRTM) is enabled by default for all new 2504 deployments running OS version **21600.3775**. For more information, see [Security features for Azure Local](./concepts/security-features.md#security-features-for-azure-local).
 
 - **Azure Local VM changes**:
     - **Data disk expansion**: With this release, you can expand the size of a data disk attached to an Azure Local VM. For more information, see [Expand the size of a data disk attached to an Azure Local VM](./manage/manage-arc-virtual-machine-resources.md).
+    - **Live VM migration with GPU partitioning (GPU-P)**: You can now live migrate VMs with GPU-P. These VMs must be on the latest NVIDIA virtual GPU v18 drivers to enable live migration with GPU-P. For more information, see [Microsoft Azure Local - NVIDIA Docs](https://docs.nvidia.com/vgpu/18.0/grid-vgpu-release-notes-microsoft-azure-stack-hci/index.html).
     - **Documentation changes**: An article describing a [Comparison of the management capabilities of VMs on Azure](./concepts/compare-vm-management-capabilities.md) was released recently.
 
 - **Update improvements**:
     - Improved reliability when downloading updates.
     - Added a health check to ensure failover cluster nodes are healthy before starting the update.
     - Simplified the Azure portal experience for viewing the progress and history of update runs.
 
--**Add and repair node changes**:
+- **Add and repair node changes**:
     - For Microsoft images, download the OS image matching the solution version of your existing cluster. See the [Release table](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) for the correct version. For OEM images, contact your Original Equipment Manufacturer (OEM).
 
 - **OEM license changes**:
@@ -69,6 +71,8 @@ This release has the following features and improvements:
 
 - **Archival of Azure Local, version 22H2 documentation**: The documentation for version 22H2 will be archived by May 31, 2025 and will be available in the [Azure previous versions documentation](/previous-versions/azure/) for reference. The archived documentation isn't updated and isn't supported.
 
+- **Observability changes**: You can now automatically collect, analyze, and debug Azure services crashes with the crash dump collection feature in Azure Local. For more information, see [Crash dump collection](./concepts/observability.md#crash-dump-collection).
+
 ::: moniker-end
 
 ::: moniker range="=azloc-2503"
diff --git a/azure-managed-lustre/client-install.md b/azure-managed-lustre/client-install.md
@@ -5,7 +5,7 @@ ms.topic: how-to
 author: pauljewellmsft
 ms.author: pauljewell
 ms.reviewer: dsundarraj
-ms.date: 01/10/2025
+ms.date: 04/29/2025
 zone_pivot_groups: select-os
 
 ---
@@ -89,11 +89,11 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    rpm --import https://packages.microsoft.com/keys/microsoft.asc
-   
+
    DISTRIB_CODENAME=el8
-   
+
    REPO_PATH=/etc/yum.repos.d/amlfs.repo
    echo -e "[amlfs]" > ${REPO_PATH}
    echo -e "name=Azure Lustre Packages" >> ${REPO_PATH}
@@ -125,11 +125,11 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    rpm --import https://packages.microsoft.com/keys/microsoft.asc
-   
+
    DISTRIB_CODENAME=el7
-   
+
    REPO_PATH=/etc/yum.repos.d/amlfs.repo
    echo -e "[amlfs]" > ${REPO_PATH}
    echo -e "name=Azure Lustre Packages" >> ${REPO_PATH}
@@ -160,11 +160,11 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    rpm --import https://packages.microsoft.com/keys/microsoft.asc
-   
+
    DISTRIB_CODENAME=el8
-   
+
    REPO_PATH=/etc/yum.repos.d/amlfs.repo
    echo -e "[amlfs]" > ${REPO_PATH}
    echo -e "name=Azure Lustre Packages" >> ${REPO_PATH}
@@ -195,11 +195,11 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    rpm --import https://packages.microsoft.com/keys/microsoft.asc
-   
+
    DISTRIB_CODENAME=el9
-   
+
    REPO_PATH=/etc/yum.repos.d/amlfs.repo
    echo -e "[amlfs]" > ${REPO_PATH}
    echo -e "name=Azure Lustre Packages" >> ${REPO_PATH}
@@ -241,12 +241,12 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    apt update && apt install -y ca-certificates curl apt-transport-https lsb-release gnupg
    source /etc/lsb-release
    echo "deb [arch=amd64] https://packages.microsoft.com/repos/amlfs-${DISTRIB_CODENAME}/ ${DISTRIB_CODENAME} main" | tee /etc/apt/sources.list.d/amlfs.list
    curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null
-   
+
    apt update
    ```
 
@@ -271,12 +271,12 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    apt update && apt install -y ca-certificates curl apt-transport-https lsb-release gnupg
    source /etc/lsb-release
    echo "deb [arch=amd64] https://packages.microsoft.com/repos/amlfs-${DISTRIB_CODENAME}/ ${DISTRIB_CODENAME} main" | tee /etc/apt/sources.list.d/amlfs.list
    curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null
-   
+
    apt update
    ```
 
@@ -322,7 +322,7 @@ This article shows how to install the client package to set up client VMs runnin
 1. Remove any kernels newer than the one mentioned in the LTS metapackage.
 
    ```bash
-   sudo apt remove linux-image-5.15.0-1053-azure
+   sudo apt remove linux-image-6.8.0-1027-azure
    ```
 
    You receive a warning about removing the kernels, but these steps work if you're following them on a newly provisioned host. If you have concerns, consult Ubuntu documentation on configuring kernels to ensure that they can start after a restart.
@@ -340,12 +340,12 @@ This article shows how to install the client package to set up client VMs runnin
    ```bash
    #!/bin/bash
    set -ex
-   
+
    apt update && apt install -y ca-certificates curl apt-transport-https lsb-release gnupg
    source /etc/lsb-release
    echo "deb [arch=amd64] https://packages.microsoft.com/repos/amlfs-${DISTRIB_CODENAME}/ ${DISTRIB_CODENAME} main" | tee /etc/apt/sources.list.d/amlfs.list
    curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null
-   
+
    apt update
    ```
 
@@ -363,6 +363,75 @@ This article shows how to install the client package to set up client VMs runnin
 
 ::: zone-end
 
+::: zone pivot="ubuntu-24"
+
+> [!IMPORTANT]
+> The Azure Marketplace image for the Ubuntu 24.04 LTS release uses the Hardware Enablement (HWE) kernel by default. However, HWE kernels are supported only for six-month periods, and Lustre support for these kernels is often not available when they're released. We recommend that you switch to the LTS kernel because it gives you more stability and it maintains a kernel version that's supported with the Lustre client.
+
+1. Install the LTS kernel metapackage:
+
+   ```bash
+   sudo apt update && sudo apt install linux-image-azure-lts-24.04
+   ```
+
+1. Remove the default (HWE) kernel metapackage. The response to the following command also asks you to remove the `linux-azure` metapackage.
+
+   ```bash
+   sudo apt remove linux-image-azure
+   ```
+
+1. List installed kernels and see which one the LTS metapackage supplies:
+
+   ```bash
+   apt list --installed linux-image*
+   ```
+
+   Newly provisioned hosts have two kernels, and older hosts might have more. Compare the version that the LTS metapackage provides against the other installed kernels.
+
+1. Remove any kernels newer than the one mentioned in the LTS metapackage.
+
+   ```bash
+   sudo apt remove linux-image-6.11.0-1013-azure
+   ```
+
+   You receive a warning about removing the kernels, but these steps work if you're following them on a newly provisioned host. If you have concerns, consult Ubuntu documentation on configuring kernels to ensure that they can start after a restart.
+
+1. List installed kernels again to verify that you don't have kernels newer than the one mentioned in the LTS metapackage:
+
+   ```bash
+   apt list --installed linux-image*
+   ```
+
+1. Restart to load the LTS kernel.
+
+1. Install and configure the Azure Managed Lustre repository for the APT package manager. Create the following script and name it `repo.bash`:
+
+   ```bash
+    #!/bin/bash
+    set -ex
+
+    apt update && apt install -y ca-certificates curl apt-transport-https lsb-release gnupg
+    source /etc/lsb-release
+    echo "deb [arch=amd64] https://packages.microsoft.com/repos/amlfs-${DISTRIB_CODENAME}/ ${DISTRIB_CODENAME} main" | tee /etc/apt/sources.list.d/amlfs.list
+    curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null
+
+    apt update
+   ```
+
+1. Run the script as a superuser:
+
+   ```bash
+   sudo bash repo.bash
+   ```
+
+1. Install the metapackage that matches your running kernel.
+
+    The following command installs a metapackage that keeps the version of Lustre aligned with the installed kernel. For this alignment to work, you must use `apt full-upgrade` instead of `apt upgrade` when updating your system.
+
+   [!INCLUDE [client-install-version-ubunt-24](./includes/client-install-version-ubuntu-24.md)]
+
+::: zone-end
+
 ## Related content
 
 - [Connect clients to an Azure Managed Lustre file system](connect-clients.md)
diff --git a/azure-managed-lustre/client-upgrade.md b/azure-managed-lustre/client-upgrade.md
diff --git a/azure-managed-lustre/includes/client-install-version-ubuntu-24.md b/azure-managed-lustre/includes/client-install-version-ubuntu-24.md
diff --git a/azure-managed-lustre/includes/client-upgrade-version-ubuntu-24.md b/azure-managed-lustre/includes/client-upgrade-version-ubuntu-24.md
diff --git a/azure-stack/zone-pivot-groups.yml b/azure-stack/zone-pivot-groups.yml
