Sync release-aks-ee-feb with main

Sync release-aks-ee-feb with main

Author: sethmanheim

adaptive-cloud/index.yml

@@ -328,8 +328,6 @@ additionalContent:
       # Cards
       - title: Azure Stack 
         links:
-          - url: /azure-stack/asdk
-            text: Azure Stack development kit
           - url: /azure-stack/hci/guided-quick-deploy-eval
             text: Azure Stack HCI evaluation guide
           - url: https://www.youtube.com/watch?v=to8D7Xl9SU8

azure-local/concepts/security-features.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 03/04/2025
+ms.date: 03/06/2025
 ---
 
 # Security features for Azure Local
@@ -160,7 +160,10 @@ Azure Local comes with Microsoft Defender Antivirus enabled and configured by de
 
 Although we recommend using Microsoft Defender Antivirus for Azure Local, if you prefer non-Microsoft antivirus and security software, **we advise selecting one that your Independent Software Vendor (ISV) has validated for Azure Local** to minimize potential functionality issues.
 
-For more information, see [Microsoft Defender Antivirus compatibility with other security products](/defender-endpoint/microsoft-defender-antivirus-compatibility).
+For more information, see:
+
+- [Microsoft Defender Antivirus compatibility with other security products](/defender-endpoint/microsoft-defender-antivirus-compatibility).
+- [Microsoft Defender Antivirus and non-Microsoft antivirus solutions without Defender for Endpoint](/defender-endpoint/defender-antivirus-compatibility-without-mde).
 
 In the rare instance that you experience any functionality issues with Azure Local using non-Microsoft antivirus software, you can exclude the following paths:
 
@@ -186,7 +189,6 @@ With the basic Defender for Cloud plan, you get recommendations on how to improv
 For more information, see:
 
 - [Manage system security with Microsoft Defender for Cloud (preview)](../manage/manage-security-with-defender-for-cloud.md).
-- [Microsoft Defender Antivirus and non-Microsoft antivirus solutions without Defender for Endpoint](/defender-endpoint/defender-antivirus-compatibility-without-mde).
 
 ## Next steps
 

azure-local/known-issues.md

@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
 description: Read about the known issues and fixed issues in Azure Local.
 author: alkohli
 ms.topic: conceptual
-ms.date: 01/28/2025
+ms.date: 03/06/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -306,6 +306,7 @@ The following table lists the known issues in this release:
 
 |Feature  |Issue  |Workaround  |
 |---------|---------|---------|
+| Azure Migrate | Migration of Gen 1 (non-sysprep) VMs using Azure Migrate fails with the error: *Failed to clean up seed ISO disk from the file system for VM*. |Contact Microsoft Support to apply a patch that resolves the VM failures associated with this issue.  |
 | Security vulnerability <!--ADO--> |Microsoft has identified a security vulnerability that could expose the local admin credentials used during the creation of Arc VMs on Azure Local to non-admin users on the VM and on the hosts. <br> Arc VMs running on releases prior to Azure Local 2411 release are vulnerable.  |To identify the Arc VMs that require this change and to change the account passwords, see detailed instructions in: [Security vulnerability for Arc VMs on Azure Local](https://aka.ms/CVE-2024-49060).|
 | Deployment <!--30273426--><br>Upgrade |If the timezone is not set to UTC before you deploy Azure Local, an *ArcOperationTimeOut* error occurs during validation. The following error message is displayed: *OperationTimeOut, No updates received from device for operation.*   |Depending on your scenario, choose one of the following workarounds for this issue: <br><br> **Scenario 1.** Before you start the deployment, make sure that the timezone is set to UTC. <br><br>Connect to each of the Azure Local nodes and change the timezone to UTC. <br><br> Run the following command: `Set-TimeZone -Id "UTC"`. <br><br> **Scenario 2.** If you started the deployment without setting the UTC timezone and received the error mentioned in the validation phase, follow these steps:<br><br> 1. Connect to each Azure Local node. Change the time zone to UTC with `Set-TimeZone -Id "UTC"`. Reboot the nodes.<br><br> 2. After the nodes have restarted, go to the Azure Local resource in Azure portal. Start the validation again to resolve the issue and continue with the deployment or upgrade.<br><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-0.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).|

azure-local/manage/azure-site-recovery.md

@@ -36,10 +36,6 @@ In the current implementation of Azure Site Recovery integration with Azure Loca
 
 ## Overall workflow
 
-The following diagram illustrates the overall workflow of Azure Site Recovery working with Azure Local.
-
-:::image type="content" source="media/azure-site-recovery/site-recovery-workflow.png" alt-text="Illustration describing Azure Site Recovery and Azure Local workflow." lightbox="media/azure-site-recovery/site-recovery-workflow.png":::
-
 Here are the main steps that occur when using Site Recovery with an Azure Local:
 
 1. Start with a registered Azure Local on which you enable Azure Site Recovery.
@@ -60,9 +56,9 @@ The following table lists the scenarios that are supported for Azure Site Recove
 
 | **Azure Local VM details** | **Failover**      | **Failback**                                   |
 |--------------------------------|-------------------|------------------------------------------------|
-| Windows Gen 1                  | Failover to Azure | Failback on same or different host as failover |
-| Windows Gen 2                  | Failover to Azure | Failback on same or different host as failover |
-| Linux Gen 1                    | Failover to Azure | Failback on same or different host as failover |
+| Windows Gen 1                  | Failover to Azure | Failback on same host as failover |
+| Windows Gen 2                  | Failover to Azure | Failback on same host as failover |
+| Linux Gen 1                    | Failover to Azure | Failback on same host as failover |
 
 > [!NOTE]
 > If an Azure Local VM is deleted after a failover, manual intervention is needed to fail back to the same or a different host..
@@ -243,6 +239,7 @@ Here's a list of known issues and the associated workarounds in this release:
 | 1. | When you register Azure Site Recovery with a system, a machine fails to install Azure Site Recovery or register to the Azure Site Recovery service.  | In this instance, your VMs may not be protected. Verify that all machines in the system are registered in the Azure portal by going to the **Recovery Services vault** \> **Jobs** \> **Site Recovery Jobs**. |
 | 2. | Azure Site Recovery agent fails to install. No error details are seen at the system or machine levels in the Azure Local portal. | When the Azure Site Recovery agent installation fails, it is because of the one of the following reasons:  <br><br> - Installation fails as Hyper-V isn't set up on the host. </br><br> - The Hyper-V host is already associated to a Hyper-V site and you're trying to install the extension with a different Hyper-V site. </br>  |
 | 3. | Azure Site Recovery agent fails to install. Error message of "Microsoft Azure Site Recovery Provider installation has failed with exit code - 1." appears in the portal with the failed installation. | The installation fails when WDAC is enforced. <br><br> - Setting WDAC to "Audit" mode will allow the installation to complete.  To set the WDAC mode to be Audit, you can follow the instructions in [Manage WDAC settings with PowerShell](/azure-stack/hci/manage/manage-wdac#manage-wdac-settings-with-powershell) |
+| 4. | Failback of an Arc VM to an alternate cluster fails. | Failback of an Arc VM to an alternate cluster is not supported |
 
 ## Next steps
 

azure-local/update/about-updates-23h2.md

@@ -82,7 +82,9 @@ Solution updates managed by this feature contain new versions of the Azure Stack
 This solution is the recommended way to update your Azure Local.
 
 > [!NOTE]
-> Customer workloads aren't covered by this update solution.
+
+> - Azure Local update includes updates for all components, including Azure CLI, PowerShell, and any extensions. Microsoft does not support out of band updates for individual components. The out of band updates could lead to incompatibility with Application Control for Windows.
+> - Customer workloads aren't covered by this update solution.
 
 ## User interfaces for updates
 

azure-local/upgrade/about-upgrades-23h2.md

@@ -3,7 +3,7 @@ title: About Azure Local upgrade to version 23H2
 description: Learn how to upgrade from Azure Local, version 22H2 to Azure Local, version 23H2.
 author: alkohli
 ms.topic: conceptual
-ms.date: 02/03/2025
+ms.date: 02/28/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -15,17 +15,17 @@ ms.service: azure-local
 
 [!INCLUDE [azure-local-banner-23h2](../includes/azure-local-banner-23h2.md)]
 
-This article provides an overview of upgrading Azure Local, version 22H2 to version 23H2.
+This article provides an overview of upgrading Azure Local, version 22H2 to Azure Local 2311.2.
 
-Throughout this article, we refer to Azure Local, version 23H2 as the *new* version and Azure Local, version 22H2 as the *old* version.
+Throughout this article, we refer to Azure Local 2311.2 as the *new* version and Azure Local, version 22H2 as the *old* version.
 
 [!INCLUDE [end-of-service-22H2](../includes/end-of-service-22h2.md)]
 
-## About Azure Local, version 23H2
+## About Azure Local 2311.2
 
-The latest version of Azure Local, version 23H2, integrates the Azure Arc infrastructure that provisions and manages the workloads such as Arc VMs, Azure Kubernetes Services, and Azure Virtual Desktop. For more information, see [What's new in Azure Local, version 23H2](../whats-new.md#features-and-improvements-in-2311).
+Azure Local 2311.2 integrates the Azure Arc infrastructure that provisions and manages the workloads such as Arc VMs, Azure Kubernetes Services, and Azure Virtual Desktop. For more information, see [What's new in Azure Local](../whats-new.md#features-and-improvements-in-2311).
 
-With version 23H2, Azure Local evolved from a cloud-connected operating system (OS) to an Arc-enabled solution. The OS forms the base layer of this solution, with the Arc and the Orchestrator (also known as the Lifecycle Manager) components layered on top. These components are packaged together into a solution that follows an [Infrastructure as code (IaC)](/devops/deliver/what-is-infrastructure-as-code) model.
+Starting with version 2311.2, Azure Local has evolved from a cloud-connected operating system (OS) to an Arc-enabled solution. The OS forms the base layer of this solution, with the Arc and the Orchestrator (also known as the Lifecycle Manager) components layered on top. These components are packaged together into a solution that follows an [Infrastructure as code (IaC)](/devops/deliver/what-is-infrastructure-as-code) model.
 
 - This IaC model takes a set of input parameters that are specific to each customer and environment.
 - The lifecycle manager then orchestrates the desired state across all the layers to meet the desired state and version.
@@ -38,7 +38,7 @@ The following diagram illustrates the components of the new version of Azure Loc
 
 An upgrade is a whole new version of software that represents a significant change or major improvement. An update, on the other hand, is a process of applying a set of changes to the software to improve its performance, security, or stability.
 
-Azure Local, version 23H2, is a new version of the solution with a multitude of new capabilities. To move from Azure Local, version 22H2 to version 23H2, you need to upgrade your existing system. On the other hand, to ensure that you have the most recent features and security improvements for your current version of Azure Local, you would need to update your existing system.
+Azure Local 2311.2 is the latest version of the solution, offering a multitude of new capabilities. To transition from the *old* version of Azure Local to the *new* version, you need to upgrade your existing system. On the other hand, to ensure that you have the most recent features and security improvements for your current version of Azure Local, you would need to update your existing system.
 
 ## High-level steps for Azure Local upgrade
 
@@ -63,24 +63,23 @@ The following diagram illustrates the Azure Local upgrade process:
 
 > [!IMPORTANT]
 > - Consult your hardware OEM before you upgrade Azure Local. Validate that your OEM supports the version and the upgrade.
-> - Upgrading your Azure Local from version 22H2 is only supported for regions where Azure Local, version 23H2 is available. For more information, see [Azure Local region availability](../concepts/system-requirements-23h2.md#azure-requirements).
-> - Use of 3rd party tools to install upgrades is not supported.
+> - Upgrading your Azure Local from the *old* version is supported only for regions where Azure Local 2311.2 is available. For more information, see [Azure Local region availability](../concepts/system-requirements-23h2.md#azure-requirements).
+> - Use of 3rd party tools to install upgrades isn't supported.
 
 Azure Local upgrade supports the following services and workloads:
 
-
-|Workload/Configuration  |Currently supported  |
-|---------|---------|
-| Azure Kubernetes (AKS) on Azure Local     | See notes <br> Kubernetes versions are incompatible between Azure Local, version 22H2, and version 23H2. <br> Remove AKS and all the settings from AKS enabled by Azure Arc before you apply the solution upgrade.        |
-| Arc VMs on Azure Local     | See notes <br> Preview versions of Arc VMs can't be upgraded.        |
-| Stretched clusters on Azure Local     | Yes <br> You must upgrade to Azure Stack HCI Operating System, version 23H2 to maintain your cluster in a supported state. <br> The solution upgrade isn't applicable for stretched clusters.      |
-| System Center Virtual Machine Manager (SCVMM)    | Yes <br> If your Azure Local instance running version 22H2 is managed by SCVMM 2025, the OS upgrade is supported.          |
-| Azure Local, version 22H2SP    | No <br> This upgrade process isn't supported for upgrading from Azure Local, version 22H2 Supplemental Package clusters.        |
-
+| Workload/Configuration | Currently supported |
+|--|--|
+| Azure Kubernetes (AKS) on Azure Local | See notes <br> Kubernetes versions are incompatible between the *old* and *new* Azure Local versions. <br> Remove AKS and all the settings from AKS enabled by Azure Arc before you apply the solution upgrade. |
+| Arc VMs on Azure Local | See notes <br> Preview versions of Arc VMs can't be upgraded. |
+| Stretched clusters on Azure Local | Yes <br> You must upgrade to Azure Stack HCI OS, version 23H2 to maintain your cluster in a supported state. <br> The solution upgrade isn't applicable for stretched clusters. |
+| System Center Virtual Machine Manager (SCVMM) | Yes <br> If your Azure Local instance running version 22H2 is managed by SCVMM 2025, the OS upgrade is supported. |
+| Azure Local, version 22H2SP | No <br> This upgrade process isn't supported for upgrading from Azure Local, version 22H2 Supplemental Package clusters. |
 
 ## Next steps
 
-Choose one of the following options to upgrade your Azure Local, version 22H2 to Azure Local, version 23H2:
+Choose one of the following options to upgrade your Azure Local system from the *old* to the *new* version:
+
 - [Use PowerShell](./upgrade-22h2-to-23h2-powershell.md).
 - [Use Windows Admin Center](./upgrade-22h2-to-23h2-windows-admin-center.md).
 - [Use other methods](./upgrade-22h2-to-23h2-other-methods.md).

azure-local/upgrade/install-enable-network-atc.md

@@ -5,7 +5,7 @@ author: ronmiab
 ms.author: robess
 ms.topic: how-to
 ms.reviewer: alkohli
-ms.date: 10/22/2024
+ms.date: 02/28/2025
 ms.service: azure-local
 #Customer intent: As a Senior Content Developer, I want to provide customers with content and steps to help them successfully install and enable Network ATC on their existing Azure Local, version 22H2 instance.
 ---
@@ -195,7 +195,7 @@ In this example, there are three intents that are managed across machines.
 
 The `Get-NetIntentStatus` command shows the deployment status of the requested intents. The result returns one object per intent for each machine in the system. For example, if you have a three-node system with two intents, you should see six objects, each with their own status, returned by the command.
 
-To verify your machines's successful deployment of the intents submitted in step 5, run the following command:
+To verify your machine's successful deployment of the intents submitted in step 5, run the following command:
 
 ```powershell
 Get-NetIntentStatus -Name <IntentName>

azure-local/upgrade/install-solution-upgrade.md

@@ -3,7 +3,7 @@ title: Install solution upgrade on Azure Local
 description: Learn how to install the solution upgrade on your Azure Local instance.
 author: alkohli
 ms.topic: how-to
-ms.date: 02/14/2025
+ms.date: 02/28/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -18,7 +18,7 @@ ms.service: azure-local
 
 This article describes how to install the solution upgrade on your Azure Local instance after the operating system (OS) was upgraded from version 22H2 to version 23H2.
 
-Throughout this article, we refer to OS version 23H2 as the new version and version 22H2 as the old version.
+Throughout this article, we refer to OS version 23H2 as the *new* version and version 22H2 as the *old* version.
 
 > [!IMPORTANT]
 > While the OS upgrade is generally available, the solution upgrade will have a phased rollout.