Merge pull request #3543 from MicrosoftDocs/main638767261054225302sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

AKS-Arc/cluster-architecture.md

@@ -2,11 +2,12 @@
 title: AKS Arc and workload cluster architecture
 description: Learn about AKS Arc and workload cluster architecture.
 ms.topic: overview
-ms.date: 05/29/2024
+ms.date: 02/28/2025
 author: sethmanheim
 ms.author: sethm 
 ms.reviewer: rbaziwane
 ms.lastreviewed: 05/29/2024
+ms.custom: references_regions
 
 ---
 
@@ -76,6 +77,10 @@ AKS is now part of Azure Local starting from version 23H2. The lifecycle managem
 
 For more information, see the [Update overview for Azure Local, version 23H2](/azure-stack/hci/update/about-updates-23h2).
 
+## Region availability
+
+AKS on Azure Local is supported in the same regions in which Azure Local is available. For more information about supported Azure regions, see [System requirements for Azure Local](/azure/azure-local/concepts/system-requirements-23h2#azure-requirements).
+
 ## Next steps
 
 - [What's new in AKS on Azure Local](aks-overview.md)

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/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/monitor-single-23h2.md

@@ -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 |