Merge pull request #16890 from MicrosoftDocs/main

01/30/2025 PM Publishing

Author: v-alje

azure-local/concepts/billing.md

@@ -5,7 +5,7 @@ author: jasongerend
 ms.author: jgerend
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 11/01/2024
+ms.date: 01/28/2025
 ---
 
 # Azure Local billing and payment
@@ -39,7 +39,7 @@ To manually upload core data to Azure, use the **`Sync-AzureStackHCI`** cmdlet.
 
 ## FAQ
 
-- If I already have an Azure subscription, can I use it for Azure Local **Yes**
+- If I already have an Azure subscription, can I use it for Azure Local? **Yes**
 - If my organization's finance department already approved spending on Azure, does that cover Azure Local? **Yes**
 - If I have an Azure commitment to spend, can I use that toward Azure Local? **Yes**
 - If I have Azure credits (for example, for students, or awarded as a prize) can I use that toward Azure Local? **Yes**

azure-local/manage/add-server.md

@@ -4,10 +4,10 @@ description: Learn how to manage capacity on your Azure Local, version 23H2 syst
 ms.topic: article
 author: alkohli
 ms.author: alkohli
-ms.date: 12/18/2024
+ms.date: 01/28/2025
 ---
 
-# Add a node on Azure Local, version 23H2
+# Add a node on Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
@@ -96,7 +96,7 @@ Make sure that you have reviewed and completed the [prerequisites](#prerequisite
 
 On the new node that you plan to add, follow these steps.
 
-1. Install the operating system and required drivers on the new node that you plan to add. Follow the steps in [Install the Azure Local Operating System, version 23H2](../deploy/deployment-install-os.md).
+1. Install the operating system and required drivers on the new node that you plan to add. Follow the steps in [Install the Azure Stack HCI Operating System, version 23H2](../deploy/deployment-install-os.md).
 
 2. Register the node with Arc. Follow the steps in [Register with Arc and set up permissions](../deploy/deployment-arc-register-server-permissions.md).
 

azure-local/manage/configure-network-security-groups-with-tags.md

@@ -7,7 +7,7 @@ ms.topic: article
 author: alkohli
 ms.subservice: 
 zone_pivot_groups: windows-os
-ms.date: 11/13/2024
+ms.date: 01/28/2025
 ---
 
 # Configure network security groups with tags in Windows Admin Center

azure-local/manage/manage-default-network-access-policies-virtual-machines-23h2.md

@@ -7,10 +7,10 @@ ms.topic: article
 author: alkohli
 ms.service: azure-local
 zone_pivot_groups: windows-os
-ms.date: 11/13/2024
+ms.date: 01/28/2025
 ---
 
-# Use default network access policies on virtual machines on Azure Local, version 23H2
+# Use default network access policies on virtual machines on Azure Local
 
 :::zone pivot="azure-local"
 

azure-local/manage/manage-sdn-multisite.md

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.subservice: 
 zone_pivot_groups: windows-os
-ms.date: 11/13/2024
+ms.date: 01/28/2025
 ---
 
 # Manage SDN Multisite for Azure Local and Windows Server
@@ -45,7 +45,7 @@ Before you can enable SDN Multisite, ensure the following prerequisites are met:
 
 :::zone pivot="azure-local"
 
-- You must have access to Azure Local, version 23H2 or later clusters deployed at two separate physical sites.
+- You must have access to Azure Local clusters deployed at two separate physical sites.
 
 - There must be an underlying [physical network connectivity](../concepts/plan-software-defined-networking-infrastructure.md#physical-and-logical-network-configuration) between the sites. Additionally, the provider network name must be the same on both sites.
 

azure-local/manage/manage-security-post-upgrade.md

@@ -1,26 +1,26 @@
 ---
-title: Manage security after upgrading your Azure Local from version 22H2 to version 23H2.
-description: Learn how to manage security posture after you have upgraded Azure Local to version 23H2.
+title: Manage security after upgrading your Azure Local from an Azure Stack HCI, version 22H2.
+description: Learn how to manage security posture after you upgrade Azure Local from an Azure Stack HCI, version 22H2.
 author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 12/11/2024
+ms.date: 01/28/2025
 ---
 
 # Manage security after upgrading Azure Local
 
 [!INCLUDE [hci-applies-to-23h2](../includes/hci-applies-to-23h2.md)]
 
-This article describes how to manage security settings on an Azure Local that was upgraded from version 22H2 to version 23H2.
+This article describes how to manage security settings on an Azure Local that was upgraded from an Azure Stack HCI, version 22H2.
 
 ## Prerequisites
 
-Before you begin, make sure that you have access to an Azure Local, version 23H2 system that was upgraded from version 22H2.
+Before you begin, make sure that you have access to an Azure Local system that was upgraded from an Azure Stack HCI, version 22H2.
 
 ## Post upgrade security changes
 
-When you upgrade your Azure Local from version 22H2 to version 23H2, the security posture of your system doesn't change. We strongly recommend that you update the security settings after the upgrade to benefit from enhanced security.
+When you upgrade your system from Azure Stack HCI, version 22H2, the security posture of your system doesn't change. We strongly recommend that you update the security settings after the upgrade to benefit from enhanced security.
 
 Here are the benefits of updating the security settings:
 
@@ -51,7 +51,7 @@ A new deployment of Azure Local introduces two baselines documents injected by t
     The new security posture of your servers will combine the previous settings, the new settings, and the overlapping settings with updated values.
 
     > [!NOTE]
-    > Microsoft tests and vaildates the Azure Local, version 23H2 security settings. We strongly recommend that you keep these settings. Use of custom settings can potentially lead to system instability, incompatibility with the new product scenarios, and could require extensive testing and troubleshooting on your part.
+    > Microsoft tests and vaildates the Azure Local security settings. We strongly recommend that you keep these settings. Use of custom settings can potentially lead to system instability, incompatibility with the new product scenarios, and could require extensive testing and troubleshooting on your part.
 
 1. When running the followign commands, you'll find the documents aren't in place. These cmdlets won't return any output.
 
@@ -108,7 +108,7 @@ If you need to enable BitLocker on any of your volumes, see [Manage BitLocker en
 
 Application control for business (formerly known as Windows Defender Application Control or WDAC) provides a great layer of defense against running untrusted code.
 
-After you've upgraded to version 23H2, consider enabling Application Control. This can be disruptive if the necessary measures aren't taken for proper validation of existing third party software already existing on the servers.
+After you upgrade your system, consider enabling Application Control. This can be disruptive if the necessary measures aren't taken for proper validation of existing third party software already existing on the servers.
 
 For new deployments, Application Control is enabled in *Enforced* mode (blocking nontrusted binaries), whereas for upgraded systems we recommend that you follow these steps:
 

azure-local/manage/manage-thin-provisioning-23h2.md

@@ -5,14 +5,14 @@ author: TinaWu-Msft
 ms.author: tinawu
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 10/29/2024
+ms.date: 01/28/2025
 ---
 
-# Storage thin provisioning in Azure Local, version 23H2
+# Storage thin provisioning in Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes how thin provisioning works on your Azure Local instance, version 23H2. Traditionally, volumes are fixed provisioned, meaning that all storage is allocated from the storage pool when a volume is created. Despite the volume being empty, a portion of the storage pool's resources are depleted. Other volumes can't make use of this storage, which impacts storage efficiency and requires more maintenance.
+This article describes how thin provisioning works on your Azure Local instance. Traditionally, volumes are fixed provisioned, meaning that all storage is allocated from the storage pool when a volume is created. Despite the volume being empty, a portion of the storage pool's resources are depleted. Other volumes can't make use of this storage, which impacts storage efficiency and requires more maintenance.
 
 ## Capacity management: thin vs. fixed provisioned volumes
 
@@ -74,7 +74,7 @@ Set-StoragePool -FriendlyName <name of storage pool> -ThinProvisioningAlertThres
 
 ## Thin provisioning FAQ
 
-This section answers frequently asked questions about thin provisioning on Azure Local, version 23H2.
+This section answers frequently asked questions about thin provisioning on Azure Local.
 
 ### Can existing fixed volumes be converted to thin?
 

azure-local/manage/repair-server.md

@@ -4,10 +4,10 @@ description: Learn how to repair a node on your Azure Local, version 23H2 system
 ms.topic: article
 author: alkohli
 ms.author: alkohli
-ms.date: 12/10/2024
+ms.date: 01/28/2025
 ---
 
-# Repair a node on Azure Local, version 23H2
+# Repair a node on Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 

azure-local/manage/trusted-launch-vm-deploy.md

@@ -5,18 +5,18 @@ ms.topic: how-to
 author: alkohli
 ms.author: alkohli
 ms.service: azure-local
-ms.date: 12/11/2024
+ms.date: 01/28/2025
 ---
 
-# Deploy Trusted launch for Azure Arc VMs on Azure Local, version 23H2
+# Deploy Trusted launch for Azure Arc VMs on Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes how to deploy Trusted launch for Azure Arc virtual machines (VMs) on Azure Local, version 23H2.
+This article describes how to deploy Trusted launch for Azure Arc virtual machines (VMs) on Azure Local.
 
 ## Prerequisites
 
-Make sure that you have access to an Azure Local, version 23H2 system that is deployed and registered with Azure. For more information, see [deploy using the Azure portal](../deploy/deploy-via-portal.md).
+Make sure that you have access to an Azure Local system that is deployed and registered with Azure. For more information, see [deploy using the Azure portal](../deploy/deploy-via-portal.md).
 
 ## Create a Trusted launch Arc VM
 

azure-local/manage/trusted-launch-vm-import-key.md

@@ -6,10 +6,10 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
 ms.reviewer: alkohli
-ms.date: 10/23/2024
+ms.date: 01/28/2025
 ---
 
-# Manage Trusted launch Arc VM guest state protection key on Azure Local, version 23H2
+# Manage Trusted launch Arc VM guest state protection key on Azure Local
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]