Sync release-aks-ee-feb with main

Sync release-aks-ee-feb with main

Author: sethmanheim

azure-local/concepts/firewall-requirements.md

@@ -4,7 +4,7 @@ description: This topic provides guidance on firewall requirements for the Azure
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 02/14/2025
+ms.date: 01/08/2025
 ---
 
 # Firewall requirements for Azure Local
@@ -56,8 +56,8 @@ For a consolidated list of endpoints for Canada Central that includes Azure Loca
 For a consolidated list of endpoints for India Central that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
 - [Required endpoints in India Central for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/IndiaCentralEndpoints/IndiaCentral-hci-endpoints.md)
 
-For a consolidated list of endpoints for SouthEast Asia that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
-- [Required endpoints in SouthEast Asia for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/SouthEastAsiaEndpoints/southeastasia-hci-endpoints.md)
+For a consolidated list of endpoints for Southeast Asia that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
+- [Required endpoints in Southeast Asia for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/SouthEastAsiaEndpoints/southeastasia-hci-endpoints.md)
 
 For a consolidated list of endpoints for Japan East that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
 - [Required endpoints in Japan East for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/JapanEastEndpoints/japaneast-hci-endpoints.md)

azure-local/concepts/single-server-clusters.md

@@ -58,6 +58,14 @@ The following table compares attributes of a single-node cluster to multi-node c
 |[Azure Stack HCI: Stretch cluster support](../concepts/stretched-clusters.md) | No | Yes |
 |[Use Graphics Processing Units (GPUs) with clustered VMs](/windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm?pivots=azure-stack-hci&toc=/azure-stack/hci/toc.json&bc=/azure-stack/breadcrumb/toc.json)  | Yes | Yes |
 
+
+## Storage resiliency
+
+|# machines  |Volume resiliency |
+|---------|---------|
+|Single machine    |Two-way mirror         |
+ 
+
 ## Known issues
 
 The following table describes currently known issues for single-node clusters. This list is subject to change as other items are identified, check back for updates.

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

@@ -61,6 +61,15 @@ $ProxyServer = "http://x.x.x.x:port"
 
 $ArcgwId = "/subscriptions/yoursubscription/resourceGroups/yourresourcegroupname/providers/Microsoft.HybridCompute/gateways/yourarcgatewayname" 
 
+#Define the bypass list for the proxy. Use comma to separate each item from the list.  
+# Use "localhost" instead of <local> 
+# Use specific IPs such as 127.0.0.1 without mask 
+# Use * for subnets allowlisting. 192.168.1.* for /24 exclusions. Use 192.168.*.* for /16 exclusions. 
+# 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,machine1,machine2,machine3,machine4,machine5,192.168.*.*,AzureLocal-1" 
+
 #Connect to your Azure account and subscription 
 
 Connect-AzAccount -SubscriptionId $Subscription -TenantId $Tenant -DeviceCode 
@@ -75,7 +84,7 @@ $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 
+Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region australiaeast -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id -Proxy $ProxyServer -ProxyBypass $ProxyBypassList  -ArcGatewayID $ArcgwId 
 ```
 
 ## Step 4: Start Azure Local cloud deployment

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

@@ -55,14 +55,14 @@ $ProxyServer = "http://x.x.x.x:port"
 #Define the Arc gateway resource ID from Azure 
 $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.  
+#Define the bypass list for the proxy. Use comma to separate each item from the list.  
 # Use "localhost" instead of <local> 
 # Use specific IPs such as 127.0.0.1 without mask 
 # Use * for subnets allowlisting. 192.168.1.* for /24 exclusions. Use 192.168.*.* for /16 exclusions. 
 # 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;machine1;machine2;machine3;machine4;machine5;192.168.*.*;AzureLocal-1" 
+$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 

azure-local/deploy/deployment-prep-active-directory.md

@@ -3,7 +3,7 @@ title: Prepare Active Directory for Azure Local, version 23H2 deployment
 description: Learn how to prepare Active Directory before you deploy Azure Local, version 23H2.
 author: alkohli
 ms.topic: how-to
-ms.date: 03/03/2025
+ms.date: 03/04/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -103,7 +103,7 @@ During the cloud deployment of Azure Local, the LCM user account is added to the
 
 We recommend that you follow these best practices for OU creation. These recommendations are automated when you use the `New-HciAdObjectsPreCreation` cmdlet to [Prepare Active Directory](#active-directory-preparation-module).
 
-- For each Azure Local instance, create an individual OU within Active Directory. This approach helps manage computer account, CNO, LCM user account, and physical machine computer accounts within the scope of a single OU for each instance.
+- For each Azure Local instance, create an individual OU within Active Directory. This approach helps manage the LCM user account, the computer accounts of the physical machines, and the cluster name object (CNO) within the scope of a single OU for each instance.
 - When deploying multiple instances at-scale, for easier management:
   - Create an OU under a single parent OU for each instance.
   - Enable the **Block Inheritance** option at both the parent OU and sub OU levels.

azure-local/manage/gpu-preparation.md

@@ -1,22 +1,19 @@
 ---
-title: Prepare GPUs for Azure Local (preview)
-description: Learn how to prepare GPUs for Azure Local (preview).
+title: Prepare GPUs for Azure Local instance
+description: Learn how to prepare GPUs for an Azure Local instance.
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
-ms.date: 01/21/2025
+ms.date: 03/03/2025
 ms.service: azure-local
 ---
 
-# Prepare GPUs for Azure Local (preview)
+# Prepare GPUs for Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
 This article describes how to prepare graphical processing units (GPUs) on your Azure Local instance for computation-intensive workloads running on Arc virtual machines (VMs) and AKS enabled by Azure Arc. GPUs are used for computation-intensive workloads such as machine learning and deep learning.
 
-> [!IMPORTANT]
-> This feature is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 ## Attaching GPUs on Azure Local
 

azure-local/manage/media/vm-activate/vm-activation-server.png

@@ -6,8 +6,7 @@ ms.author: alkohli
 ms.reviewer: saniyaislam
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 10/10/2024
-# zone_pivot_groups: hci-versions
+ms.date: 03/04/2025
 ---
 
 # Monitor a single Azure Local system with Insights
@@ -179,6 +178,8 @@ Once Insights is enabled, the following tables provide details about all resourc
 
 Provides health faults on a cluster.
 
+You can view health issues like unsupported hardware, unresponsive disk, bad block writes, detached drives, repair needs, exceeded CPU, memory and storage usage, and high latency. For a complete list of supported health faults, see [View Health Service faults](./health-service-faults.md).
+
 | Metric | Description | Unit | Example |
 |--|--|--|--|
 | Fault | A short description of health faults. On clicking the link, a side panel opens with more information. | No unit | PoolCapacityThresholdExceeded |
@@ -189,6 +190,8 @@ Provides health faults on a cluster.
 
 ### Nodes
 
+Provides health and performance information for the servers.
+
 | Metric | Description | Unit | Example |
 |--|--|--|--|
 | Nodes | The names of the nodes in the cluster. | No unit | VM-1 |

azure-local/manage/media/vm-activate/windows-server-subscription.png

@@ -7,7 +7,7 @@ ms.topic: how-to
 ms.service: azure-local
 ms.custom:
   - devx-track-azurecli
-ms.date: 12/10/2024
+ms.date: 03/04/2025
 ---
 
 # Create Azure Local VM image using Azure Marketplace images
@@ -26,13 +26,17 @@ Before you begin, make sure that the following prerequisites are completed.
 
 - Make sure you have the **Azure Connected Machine Resource Manager** role. For more information, see [Assign Azure roles](/azure/role-based-access-control/role-assignments-portal).
 
+- Make sure that your subscription is registered with the `Microsoft.EdgeMarketplace` resource provider. For more information, see [Register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider).
+
 - If using a client to connect to your Azure Local instance, see [Connect to the system remotely](./azure-arc-vm-management-prerequisites.md#connect-to-the-system-remotely).
 
 # [Azure portal](#tab/azureportal)
 
 - Make sure to review and [complete the prerequisites](./azure-arc-vm-management-prerequisites.md).
 
 - Make sure you have the **Azure Connected Machine Resource Manager** role. For more information, see [Assign Azure roles](/azure/role-based-access-control/role-assignments-portal).
+
+- Make sure that your subscription is registered with the `Microsoft.EdgeMarketplace` resource provider. For more information, see [Register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider).
 ---
 
 ## Add VM image from Azure Marketplace
@@ -98,8 +102,8 @@ Follow these steps to create a VM image using the Azure CLI.
 
     | Name | Publisher | Offer | SKU |
     |------|-----------|-------|------|
-    | Windows 11 Enterprise multi-session + Microsoft 365 | microsoftwindowsdesktop | office-365 | win11-23h2-avd-m365 |
-    | Windows 10 Enterprise multi-session + Microsoft 365  | microsoftwindowsdesktop | office-365 | win10-21h2-avd-m365<br>win10-22h2-avd-m365 |
+    | Windows 11 Enterprise multi-session + Microsoft 365 | microsoftwindowsdesktop | office-365 | win11-23h2-avd-m365 <br> win11-24h2-avd-m365 |
+    | Windows 10 Enterprise multi-session + Microsoft 365  | microsoftwindowsdesktop | office-365 | win10-21h2-avd-m365 |
     | Windows 11 Pro | microsoftwindowsdesktop | windows-11 | win11-23h2-pro |
     | Windows 11 Enterprise | microsoftwindowsdesktop | windows-11 | win11-22h2-ent<br>win11-23h2-ent<br>win11-24h2-ent |
     | Windows 11 Enterprise multi-session | microsoftwindowsdesktop | windows-11 | win11-22h2-avd<br>win11-23h2-avd<br>win11-24h2-avd |