Removed version 23H2 references

Author: alkohli

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: 01/02/2025
+ms.date: 02/14/2025
 ---
 
 # Firewall requirements for Azure Local
@@ -18,7 +18,7 @@ This article also describes how to optionally use a highly locked-down firewall
 If your network uses a proxy server for internet access, see [Configure proxy settings for Azure Local](../manage/configure-proxy-settings-23h2.md).
 
 > [!IMPORTANT]
-> Azure Express Route and Azure Private Link are not supported for Azure Local, version 23H2 or any of its components as it is not possible to access the public endpoints required for Azure Local, version 23H2.
+> Azure Express Route and Azure Private Link are not supported for Azure Local or any of its components as it is not possible to access the public endpoints required for Azure Local.
 
 ## Firewall requirements for outbound endpoints
 
@@ -37,33 +37,33 @@ As shown in the following diagram, Azure Local can access Azure using more than
 
 :::image type="content" source="./media/firewall-requirements/firewalls-diagram.png" alt-text="Diagram shows Azure Local accessing service tag endpoints through Port 443 (HTTPS) of firewalls." lightbox="./media/firewall-requirements/firewalls-diagram.png":::
 
-## Required firewall URLs for Azure Local, version 23H2 deployments
+## Required firewall URLs for Azure Local deployments
 
-Starting with Azure Local, version 23H2, all the clusters automatically enables Azure Resource Bridge and AKS infrastructure and uses the Arc for Servers agent to connect to Azure control plane. Along with the list of HCI specific endpoints on the following table, the [Azure Resource Bridge on Azure Local](/azure/azure-arc/resource-bridge/network-requirements) endpoints, the [AKS on Azure Local](/azure/aks/hybrid/aks-hci-network-system-requirements#firewall-url-exceptions) endpoints and the [Azure Arc-enabled servers](/azure/azure-arc/servers/network-requirements) endpoints must be included in the allow list of your firewall.
+Starting with Azure Local, all the clusters automatically enables Azure Resource Bridge and AKS infrastructure and uses the Arc for Servers agent to connect to Azure control plane. Along with the list of HCI specific endpoints on the following table, the [Azure Resource Bridge on Azure Local](/azure/azure-arc/resource-bridge/network-requirements) endpoints, the [AKS on Azure Local](/azure/aks/hybrid/aks-hci-network-system-requirements#firewall-url-exceptions) endpoints and the [Azure Arc-enabled servers](/azure/azure-arc/servers/network-requirements) endpoints must be included in the allow list of your firewall.
 
 For a consolidated list of endpoints for East US that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
-- [Required endpoints in East US for Azure Local, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/EastUSendpoints/eastus-hci-endpoints.md)
+- [Required endpoints in East US for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/EastUSendpoints/eastus-hci-endpoints.md)
 
 For a consolidated list of endpoints for West Europe that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
-- [Required endpoints in West Europe for Azure Local, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/WestEuropeendpoints/westeurope-hci-endpoints.md)
+- [Required endpoints in West Europe for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/WestEuropeendpoints/westeurope-hci-endpoints.md)
 
 For a consolidated list of endpoints for Australia East that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
-- [Required endpoints in Australia East for Azure Local, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/AustraliaEastendpoints/AustraliaEast-hci-endpoints.md)
+- [Required endpoints in Australia East for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/AustraliaEastendpoints/AustraliaEast-hci-endpoints.md)
 
 For a consolidated list of endpoints for Canada Central that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
-- [Required endpoints in Canada Central for Azure Local, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/CanadaCentralEndpoints/canadacentral-hci-endpoints.md)
+- [Required endpoints in Canada Central for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/CanadaCentralEndpoints/canadacentral-hci-endpoints.md)
 
 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, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/IndiaCentralEndpoints/IndiaCentral-hci-endpoints.md)
+- [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, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/SouthEastAsiaEndpoints/southeastasia-hci-endpoints.md)
+- [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, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/JapanEastEndpoints/japaneast-hci-endpoints.md)
+- [Required endpoints in Japan East for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/JapanEastEndpoints/japaneast-hci-endpoints.md)
 
 For a consolidated list of endpoints for South Central US that includes Azure Local, Arc-enabled servers, ARB, and AKS, use:
-- [Required endpoints in South Central US for Azure Local, version 23H2](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/SouthCentralUSEndpoints/southcentralus-hci-endpoints.md)
+- [Required endpoints in South Central US for Azure Local](https://github.com/Azure/AzureStack-Tools/blob/master/HCI/SouthCentralUSEndpoints/southcentralus-hci-endpoints.md)
 
 ## Firewall requirements for additional Azure services
 
@@ -198,4 +198,5 @@ This section shows how to configure Microsoft Defender firewall to allow IP addr
 For more information, see also:
 
 - The Windows Firewall and WinRM 2.0 ports section of [Installation and configuration for Windows Remote Management](/windows/win32/winrm/installation-and-configuration-for-windows-remote-management#windows-firewall-and-winrm-20-ports)
-- See [About Azure Local, version 23H2 deployment](../deploy/deployment-introduction.md)
+- See [About Azure Local deployment](../deploy/deployment-introduction.md)
+````

azure-local/concepts/system-requirements-23h2.md

@@ -9,7 +9,7 @@ ms.custom: references_regions
 ms.date: 01/02/2025
 ---
 
-# System requirements for Azure Local, version 23H2
+# System requirements for Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
@@ -96,14 +96,14 @@ To ensure adequate support and diagnosability for large memory Azure Local insta
 
 In addition to Microsoft Azure Local updates, many OEMs also release regular updates for your Azure Local hardware, such as driver and firmware updates. To ensure that OEM package update notifications, reach your organization check with your OEM about their specific notification process.
 
-Before deploying Azure Local, version 23H2, ensure that your hardware is up to date by:
+Before deploying Azure Local, ensure that your hardware is up to date by:
 
 - Determining the current version of your Solution Builder Extension (SBE) package.
 - Finding the best method to download, install, and update your SBE package.
 
 ### OEM information
 
-This section contains OEM contact information and links to OEM Azure Local, version 23H2 reference material.
+This section contains OEM contact information and links to OEM Azure Local reference material.
 
 | Azure Local Solution provider | Solution platform  | How to configure BIOS settings | How to update firmware | How to update drivers | How to update the system after it's running |
 |-----------------------|--------------------|--------------------------------|------------------------|-----------------------|-----------------------------------------------|
@@ -117,11 +117,11 @@ For a comprehensive list of all OEM contact information, download the [Azure Loc
 
 ### BIOS setting
 
-Check with your OEM regarding the necessary generic BIOS settings for Azure Local, version 23H2. These settings may include hardware virtualization, TPM enabled, and secure core.
+Check with your OEM regarding the necessary generic BIOS settings for Azure Local. These settings may include hardware virtualization, TPM enabled, and secure core.
 
 ## Driver
 
-Check with your OEM regarding the necessary drivers that need to be installed for Azure Local, version 23H2. Additionally, your OEM can provide you with their preferred installation steps.
+Check with your OEM regarding the necessary drivers that need to be installed for Azure Local. Additionally, your OEM can provide you with their preferred installation steps.
 
 ### Driver installation steps
 
@@ -230,11 +230,11 @@ You should always follow the OEM's recommended installation steps. If the OEM's
 
 ## Firmware
 
-Check with your OEM regarding the necessary firmware that needs to be installed for Azure Local, version 23H2. Additionally, your OEM can provide you with their preferred installation steps.
+Check with your OEM regarding the necessary firmware that needs to be installed for Azure Local. Additionally, your OEM can provide you with their preferred installation steps.
 
 ## Drivers and firmware via the Windows Admin Center extension
 
-You should always follow the OEM's recommended installation steps. With Azure Local, version 23H2, Windows Admin Center plugins can be used to install drivers and firmware. For a comprehensive list of all OEM contact information, download the [Azure Local OEM Contact](https://github.com/Azure/AzureStack-Tools/raw/master/HCI/azure-stack-hci-oem-contact-and-material.xlsx) spreadsheet.
+You should always follow the OEM's recommended installation steps. With Azure Local, Windows Admin Center plugins can be used to install drivers and firmware. For a comprehensive list of all OEM contact information, download the [Azure Local OEM Contact](https://github.com/Azure/AzureStack-Tools/raw/master/HCI/azure-stack-hci-oem-contact-and-material.xlsx) spreadsheet.
 
 <!--|OEM    | Download link                                                    |
 |-------|------------------------------------------------------------------|

azure-local/concepts/system-requirements-small-23h2.md

@@ -9,7 +9,7 @@ ms.custom: references_regions
 ms.date: 02/06/2025
 ---
 
-# System requirements for small form factor deployments of Azure Local, version 23H2 (preview)
+# System requirements for small form factor deployments of Azure Local
 
 ::: moniker range=">=azloc-2411"
 

azure-local/manage/use-environment-checker.md

@@ -8,7 +8,7 @@ ms.service: azure-local
 ms.date: 12/27/2024
 ---
 
-# Evaluate the deployment readiness of your environment for Azure Local, version 23H2
+# Evaluate the deployment readiness of your environment for Azure Local
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 

azure-local/plan/cloud-deployment-network-considerations.md

@@ -8,11 +8,11 @@ ms.author: alkohli
 ms.reviewer: alkohli
 ---
 
-# Network considerations for cloud deployments of Azure Local, version 23H2
+# Network considerations for cloud deployments of Azure Local
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 
-This article discusses how to design and plan an Azure Local, version 23H2 system network for cloud deployment. Before you continue, familiarize yourself with the various [Azure Local networking patterns](../plan/choose-network-pattern.md) and available configurations.
+This article discusses how to design and plan an Azure Local system network for cloud deployment. Before you continue, familiarize yourself with the various [Azure Local networking patterns](../plan/choose-network-pattern.md) and available configurations.
 
 ## Network design framework
 
@@ -412,4 +412,4 @@ Here are the summarized considerations for network adapter configuration:
 
 ## Next steps
 
-- [About Azure Local, version 23H2 deployment](../deploy/deployment-introduction.md).
+- [About Azure Local deployment](../deploy/deployment-introduction.md).

azure-local/plan/configure-custom-settings-active-directory.md

@@ -9,11 +9,11 @@ ms.service: azure-local
 ms.custom: devx-track-azurepowershell
 ---
 
-# Custom Active Directory configuration for your Azure Local, version 23H2
+# Custom Active Directory configuration for your Azure Local instance
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes the permissions and the DNS records required for the Azure Local, version 23H2 deployment. The article also uses examples with detailed steps on how to manually assign permissions and create DNS records for your Active Directory environment.
+This article describes the permissions and the DNS records required for the Azure Local instance deployment. The article also uses examples with detailed steps on how to manually assign permissions and create DNS records for your Active Directory environment.
 
 The Azure Local solution is deployed in large Active Directories with established processes and tools for assigning permissions. Microsoft provides an [Active Directory preparation script](../deploy/deployment-prep-active-directory.md) that can be optionally used for the Azure Local deployment. The required permissions for Active Directory, the creation of the organizational unit, and blocking inheritance of GPOs - can all be also configured manually.
 
@@ -28,7 +28,7 @@ Here are some of the Active Directory requirements for the Azure Local deploymen
 
 - The user (also known as deployment user) requires the necessary permissions over the dedicated OU. The user can reside anywhere in the directory.
 
-- Blocking group policy inheritance is required to prevent any conflicts of settings coming from group policy objects. The new engine introduced with Azure Local, version 23H2 manages security defaults including the drift protection. For more information, see [Security features for Azure Local, version 23H2](../concepts/security-features.md).
+- Blocking group policy inheritance is required to prevent any conflicts of settings coming from group policy objects. The new engine introduced with Azure Local manages security defaults including the drift protection. For more information, see [Security features for Azure Local instance](../concepts/security-features.md).
 
 - Computer account objects and cluster CNO can be [precreated](/windows-server/failover-clustering/prestage-cluster-adds) using the deployment user as an alternative to the deployment itself creating them.
 
@@ -116,7 +116,7 @@ nslookup "machine name"
 
 A disjoint namespace occurs when the primary DNS suffix of one or more domain member computers doesn't match the DNS name of their Active Directory domain. For example, if a computer has a DNS name of corp.contoso.com but is part of an Active Directory domain called na.corp.contoso.com, it's using a disjoint namespace.
 
-Before deploying Azure Local, version 23H2, you must:
+Before deploying an Azure Local instance, you must:
 
 - Append the DNS suffix to the management adapter of every node.
 - Verify you can resolve the hostname to the FQDN of the Active Directory.
@@ -138,7 +138,7 @@ nslookup node1.na.corp.contoso.com
 ```
 
 > [!NOTE]
-> You cannot use group policies to configure the DNS suffix list with Azure Local, version 23H2.
+> You cannot use group policies to configure the DNS suffix list with Azure Local instance.
 
 ## Cluster aware updating (CAU)
 

azure-local/plan/network-patterns-overview.md

@@ -27,9 +27,9 @@ A deployment consists of single-node or multiple node systems (up to 16 machines
 
 The following highlights some considerations of using switchless configurations:
 
-- Storage switchless deployments in Azure Local, version 23H2 only support 1,2 or 3 nodes.
+- Storage switchless deployments in Azure Local only support 1,2 or 3 nodes.
 
-- Scale out operations on storage switchless deployments from Azure portal or ARM aren't supported in Azure Local, version 23H2 systems.  
+- Scale out operations on storage switchless deployments from Azure portal or ARM aren't supported in Azure Local systems.  
 
 - No switch is necessary for in-system (East-West) traffic; however, a physical switch is required for traffic outside the system (North-South).
 

azure-local/plan/three-node-switchless-two-switches-single-link.md

@@ -61,7 +61,7 @@ When deploying a three-node switchless configuration, Network ATC has the follow
 
 - `StorageAutoIP` parameter must be set to false, `Switchless` parameter must be set to true,  and you are responsible to specify the IPs on the ARM template used to deploy the Azure Local instance from Azure.
 
-- For Azure Local, version 23H2 cloud deployments:
+- For Azure Local cloud deployments:
 
     - Scale out storage switchless systems aren't supported.
 

azure-local/plan/three-node-switchless-two-switches-two-links.md

@@ -61,7 +61,7 @@ When deploying three nodes in a switchless configuration, Network ATC has the fo
 
 - `StorageAutoIP` parameter must be set to false, `Switchless` parameter must be set to true, and you are responsible to specify the IPs on the ARM template used to deploy the Azure Local instance from Azure.
 
-- For Azure Local, version 23H2 cloud deployments:
+- For Azure Local cloud deployments:
 
     - Scale out storage switchless systems aren't supported.
 

azure-local/plan/two-node-switched-converged.md

@@ -13,7 +13,7 @@ ms.date: 12/26/2024
 
 [!INCLUDE [includes](../includes/hci-applies-to-23h2-22h2.md)]
 
-In this article, you'll learn about the two-node storage switched, fully converged with two TOR switches network reference pattern that you can use to deploy your Azure Local solution. The information in this article will also help you determine if this configuration is viable for your deployment planning needs. This article is targeted towards the IT administrators who deploy and manage Azure Local in their datacenters.
+In this article, you'll learn about the two-node storage switched, fully converged with two TOR switches network reference pattern that you can use to deploy your Azure Local instance solution. The information in this article will also help you determine if this configuration is viable for your deployment planning needs. This article is targeted towards the IT administrators who deploy and manage Azure Local instance in their datacenters.
 
 For information on other network patterns, see [Azure Local network deployment patterns](choose-network-pattern.md).