Merge pull request #15897 from ManikaDhiman/md-update-applies-to

JamesJBarnett · web-flow · commit 36ecfc04e59f · 2024-09-24T12:45:29.000-07:00
Update applies to include for version 22H2 articles
diff --git a/azure-stack/hci/concepts/data-collection.md b/azure-stack/hci/concepts/data-collection.md
@@ -11,7 +11,7 @@ ms.date: 04/24/2023
 
 # Azure Stack HCI data collection
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This topic describes required data collected to keep Azure Stack HCI secure, up to date, and working as expected.
 
diff --git a/azure-stack/hci/concepts/nested-virtualization.md b/azure-stack/hci/concepts/nested-virtualization.md
@@ -11,7 +11,7 @@ ms.date: 04/17/2023
 
 # Nested virtualization in Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 Nested virtualization is a feature that lets you run Hyper-V inside a Hyper-V virtual machine (VM). This allows you to maximize your hardware investments and gain flexibility in evaluation and testing scenarios.
 
diff --git a/azure-stack/hci/concepts/network-atc-overview.md b/azure-stack/hci/concepts/network-atc-overview.md
@@ -10,7 +10,7 @@ ms.reviewer: JasonGerend
 
 # Network ATC overview
 
-[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2.md)]
 
 Deployment and operation of Azure Stack HCI networking can be a complex and error-prone process. Due to the configuration flexibility provided with the host networking stack, there are many moving parts that can be easily misconfigured or overlooked. Staying up to date with the latest best practices is also a challenge as improvements are continuously made to the underlying technologies. Additionally, configuration consistency across HCI cluster nodes is important as it leads to a more reliable experience.
 
diff --git a/azure-stack/hci/concepts/network-hud-overview.md b/azure-stack/hci/concepts/network-hud-overview.md
@@ -10,7 +10,7 @@ ms.reviewer: dacuo
 
 # Network HUD overview
 
-[!INCLUDE [applies-to]( ../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to]( ../../includes/hci-applies-to-22h2.md)]
 
 Network HUD enables visibility across the network, simplifying operational network diagnostics. It performs real-time analysis of network issues and provides prescriptive alerts or auto-remediation of the issue when possible. These capabilities can increase stability and optimize network performance for workloads running on Azure Stack HCI.
 
diff --git a/azure-stack/hci/concepts/single-server-clusters.md b/azure-stack/hci/concepts/single-server-clusters.md
@@ -11,7 +11,7 @@ ms.date: 04/01/2024
 
 # Using Azure Stack HCI on a single server
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-23h2](../../includes/hci-warning-single-server-22h2.md)]
 
diff --git a/azure-stack/hci/concepts/stretched-clusters.md b/azure-stack/hci/concepts/stretched-clusters.md
@@ -10,7 +10,7 @@ ms.reviewer: johnmar
 
 # Stretched clusters overview
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 > [!IMPORTANT]
 > Stretched clusters are not yet supported in Azure Stack HCI version 23H2.
diff --git a/azure-stack/hci/concepts/system-requirements.md b/azure-stack/hci/concepts/system-requirements.md
@@ -12,7 +12,7 @@ ms.date: 05/22/2024
 
 # System requirements for Azure Stack HCI, version 22H2
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 > [!WARNING]
 > The system requirements listed in this article apply to an older version, Azure Stack HCI, version 22H2. To find the system requirements for the latest generally available version, Azure Stack HCI, version 23H2, see [System requirements for Azure Stack HCI, version 23H2](./system-requirements-23h2.md).
diff --git a/azure-stack/hci/concepts/updates.md b/azure-stack/hci/concepts/updates.md
@@ -9,7 +9,7 @@ ms.date: 02/23/2024
 
 # Updates and upgrades
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article describes the lifecycle of updates and upgrades on Azure Stack HCI. 
 
diff --git a/azure-stack/hci/concepts/utility-applications.md b/azure-stack/hci/concepts/utility-applications.md
@@ -9,7 +9,7 @@ ms.date: 02/23/2024
 
 # Utility applications for Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 Azure Stack HCI is a hyperconverged infrastructure stack that’s uniquely positioned for hybrid infrastructure, allowing customers to take advantage of cloud and on-premises resources working together and natively monitor, secure and back up to the cloud. To learn more, see the [Azure Stack HCI solution overview](../overview.md).
 
diff --git a/azure-stack/hci/deploy/branch-office-edge.md b/azure-stack/hci/deploy/branch-office-edge.md
@@ -9,7 +9,7 @@ ms.date: 04/17/2023
 
 # Deploy branch office and edge on Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This topic provides guidance on how to plan, configure, and deploy branch office and edge scenarios on the Azure Stack HCI operating system. The guidance positions your organization to run complex, highly available workloads in virtual machines (VMs) and containers in remote branch office and edge deployments. Computing at the edge shifts most data processing from a centralized system to the edge of the network, closer to a device or system that requires data quickly.
 
diff --git a/azure-stack/hci/deploy/create-cluster-powershell.md b/azure-stack/hci/deploy/create-cluster-powershell.md
@@ -9,7 +9,7 @@ ms.reviewer: robhind
 ---
 # Create an Azure Stack HCI cluster using Windows PowerShell
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-22h2](../../includes/hci-warning-deploy-22h2.md)]
 
diff --git a/azure-stack/hci/deploy/create-cluster.md b/azure-stack/hci/deploy/create-cluster.md
@@ -10,7 +10,7 @@ ms.reviewer: shsathee
 
 # Create an Azure Stack HCI cluster using Windows Admin Center
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-22h2](../../includes/hci-warning-deploy-22h2.md)]
 
diff --git a/azure-stack/hci/deploy/download-azure-stack-hci-software.md b/azure-stack/hci/deploy/download-azure-stack-hci-software.md
@@ -11,7 +11,7 @@ ms.date: 01/31/2024
 
 # Download the Azure Stack HCI software
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-22h2](../../includes/hci-warning-deploy-22h2.md)]
 
diff --git a/azure-stack/hci/deploy/network-atc.md b/azure-stack/hci/deploy/network-atc.md
@@ -10,7 +10,7 @@ ms.reviewer: jgerend
 
 # Deploy host networking with Network ATC
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article guides you through the requirements, best practices, and deployment of Network ATC. Network ATC simplifies the deployment and network configuration management for Azure Stack HCI clusters. Network ATC provides an intent-based approach to host network deployment. By specifying one or more intents (management, compute, or storage) for a network adapter, you can automate the deployment of the intended configuration. For more information on Network ATC, including an overview and definitions, please see [Network ATC overview](../concepts/network-atc-overview.md).
 
diff --git a/azure-stack/hci/deploy/operating-system.md b/azure-stack/hci/deploy/operating-system.md
@@ -11,7 +11,7 @@ ms.date: 04/12/2024
 
 # Deploy the Azure Stack HCI operating system
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-22h2](../../includes/hci-warning-deploy-22h2.md)]
 
diff --git a/azure-stack/hci/deploy/register-with-azure.md b/azure-stack/hci/deploy/register-with-azure.md
@@ -13,7 +13,7 @@ ms.date: 02/07/2024
 
 # Register Azure Stack HCI with Azure
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-22h2](../../includes/hci-warning-deploy-22h2.md)]
 
diff --git a/azure-stack/hci/deploy/single-server.md b/azure-stack/hci/deploy/single-server.md
@@ -11,7 +11,7 @@ ms.date: 01/31/2024
 
 # Deploy Azure Stack HCI on a single server
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 [!INCLUDE [warning-22h2](../../includes/hci-warning-deploy-22h2.md)]
 
diff --git a/azure-stack/hci/deploy/troubleshoot-hci-registration.md b/azure-stack/hci/deploy/troubleshoot-hci-registration.md
@@ -12,7 +12,7 @@ ms.date: 04/30/2024
 
 # Troubleshoot Azure Stack HCI registration
 
-[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2.md)]
 
 > [!IMPORTANT]
 > Troubleshooting instructions provided in this article apply to an older version, Azure Stack HCI, version 22H2. To troubleshoot new deployments running the latest generally available version, Azure Stack HCI, version 23H2, see [Get support for Azure Stack HCI deployment issues](../manage/get-support-for-deployment-issues.md).
diff --git a/azure-stack/hci/deploy/trusted-enterprise-virtualization.md b/azure-stack/hci/deploy/trusted-enterprise-virtualization.md
@@ -9,7 +9,7 @@ ms.date: 04/17/2023
 
 # Deploy trusted enterprise virtualization on Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This topic provides guidance on how to plan, configure, and deploy a highly secure infrastructure that uses trusted enterprise virtualization on the Azure Stack HCI operating system. Leverage your Azure Stack HCI investment to run secure workloads on hardware that uses [virtualization-based security (VBS)](/windows-hardware/design/device-experiences/oem-vbs) and hybrid cloud services through Windows Admin Center and the Azure portal.
 
diff --git a/azure-stack/hci/deploy/virtual-desktop-infrastructure.md b/azure-stack/hci/deploy/virtual-desktop-infrastructure.md
@@ -9,7 +9,7 @@ ms.date: 05/22/2024
 
 # Deploy virtual desktop infrastructure (VDI) on Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This topic provides guidance on how to plan, configure, and deploy virtual desktop infrastructure (VDI) on the Azure Stack HCI operating system. Leverage your Azure Stack HCI investment to deliver centralized, highly available, simplified, and secure management for the users in your organization. Use this guidance to enable scenarios like bring-your-own-device (BYOD) for your users, while providing them with a consistent and reliable experience for business-critical applications without sacrificing security.
 
diff --git a/azure-stack/hci/manage/add-cluster.md b/azure-stack/hci/manage/add-cluster.md
@@ -10,7 +10,7 @@ ms.date: 02/23/2024
 
 # Add or remove servers for an Azure Stack HCI cluster
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 You can easily add or remove servers from a cluster in Azure Stack HCI. Keep in mind that each new physical server must closely match the rest of the servers in the cluster when it comes to CPU type, memory, number of drives, and the type and size of the drives.
 
diff --git a/azure-stack/hci/manage/azure-benefits.md b/azure-stack/hci/manage/azure-benefits.md
@@ -13,7 +13,7 @@ ms.lastreviewed: 02/23/2024
 
 # Azure Benefits on Azure Stack HCI (22H2 and earlier)
 
-[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2.md)]
 
 > [!NOTE]
 > This article is for Azure Stack HCI version 22H2 and earlier only. For a list of benefits associated with version 23H2 and later, see [Azure verification for VMs](../deploy/azure-verification.md).
diff --git a/azure-stack/hci/manage/azure-portal.md b/azure-stack/hci/manage/azure-portal.md
@@ -11,7 +11,7 @@ ms.date: 02/23/2024
 
 # Use the Azure portal with Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This topic explains how to connect to the Azure Stack HCI portion of the Azure portal for a global view of your Azure Stack HCI clusters. You can use the Azure portal to manage and monitor your clusters even if your physical infrastructure is hosted on premises. Cloud-based monitoring eliminates the need to maintain an on-premises monitoring system and database, reducing infrastructure complexity. It also increases scalability by uploading alerts and other information directly to Azure, which already manages millions of objects every day.
 
diff --git a/azure-stack/hci/manage/configure-proxy-settings.md b/azure-stack/hci/manage/configure-proxy-settings.md
@@ -9,7 +9,7 @@ ms.date: 11/21/2023
 
 # Configure proxy settings for Azure Stack HCI
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article describes how to configure proxy settings for Azure Stack HCI if your network uses a proxy server for internet access.
 
diff --git a/azure-stack/hci/manage/convert-to-stretched-cluster.md b/azure-stack/hci/manage/convert-to-stretched-cluster.md
@@ -10,7 +10,7 @@ ms.date: 09/16/2021
 
 # Convert to a stretched Azure Stack HCI cluster
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article explains and gives the steps required to create a stretched cluster by adding new server nodes to an existing single-site cluster. You use Windows PowerShell commands to accomplish this.
 
diff --git a/azure-stack/hci/manage/create-stretched-volumes.md b/azure-stack/hci/manage/create-stretched-volumes.md
@@ -10,7 +10,7 @@ ms.date: 05/16/2022
 
 # Create stretched cluster volumes and set up replication
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article describes how to create volumes and set up replication for stretched clusters in Azure Stack HCI using Windows Admin Center and PowerShell.
 
diff --git a/azure-stack/hci/manage/kernel-soft-reboot.md b/azure-stack/hci/manage/kernel-soft-reboot.md
@@ -11,7 +11,7 @@ ms.date: 03/17/2023
 
 # Enable quick restarts with Kernel Soft Reboot
 
-[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2.md)]
 
 New in Azure Stack HCI, version 21H2, Kernel Soft Reboot (KSR) is a premium feature available on all Azure Stack HCI integrated systems. You can use it when updating the cluster to reboot the servers faster than a normal reboot. This topic explains when to use a KSR over a normal reboot and provides instructions on using this feature on Azure Stack HCI.
 
diff --git a/azure-stack/hci/manage/manage-cluster-registration.md b/azure-stack/hci/manage/manage-cluster-registration.md
@@ -11,7 +11,7 @@ ms.date: 03/11/2024
 
 # Manage Azure Stack HCI cluster registration
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 Depending on your cluster configuration and requirements, you may need to take additional steps after registering your cluster with Azure. This article describes how to manage your cluster registration using Windows Admin Center, PowerShell, or the Azure portal. It also provides answers to the frequently asked questions about cluster registration.
 
diff --git a/azure-stack/hci/manage/manage-network-atc.md b/azure-stack/hci/manage/manage-network-atc.md
@@ -9,7 +9,7 @@ ms.author: jgerend
 
 # Manage Network ATC
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article discusses how to manage Network ATC after it has been deployed. Network ATC simplifies the deployment and network configuration management for Azure Stack HCI clusters. You use Windows PowerShell to manage Network ATC.
 
@@ -81,7 +81,7 @@ You can use default VLANs specified by Network ATC or use values specific to you
 
 This task helps you update the network adapters assigned to an intent. If there are changes to the physical adapters in your cluster, you can use `Update-NetIntentAdapter` to update the relevant intents.
 
-In this example we installed two new adapters, pNIC03 and pNIC04, and we want them to be used in our intent named 'Cluster_Compute'.
+In this example, we installed two new adapters, pNIC03 and pNIC04, and we want them to be used in our intent named 'Cluster_Compute'.
 
 1. On one of the cluster nodes, run `Get-NetAdapter` to check that both adapters are present and report status of 'Up' on each cluster node. 
 
@@ -126,15 +126,15 @@ Global overrides and cluster network settings is a new feature Network ATC is in
 
 ### Cluster network features
 
-In this section, we go over the set of new Cluster Network Features that we are releasing with the 22H2 release. The new Cluster Network Features enable and optimize cluster network naming, managing cluster networks by controlling performance options, bandwidth limits, and managing live migrations.
+In this section, we go over the set of new Cluster Network Features that we're releasing with the 22H2 release. The new Cluster Network Features enable and optimize cluster network naming, managing cluster networks by controlling performance options, bandwidth limits, and managing live migrations.
 
 ###### Cluster network naming
 
-Description: By default, failover clustering always names unique subnets like this: “Cluster Network 1”, “Cluster Network 2”, and so on. This is unconnected to the actual use of the network because there is no way for clustering to know how you intended to use the networks – until now!
+Description: By default, failover clustering always names unique subnets like this: “Cluster Network 1”, “Cluster Network 2”, and so on. This is unconnected to the actual use of the network because there's no way for clustering to know how you intended to use the networks – until now!
 
-Once you define your configuration through Network ATC, we now understand how the subnets are going to be used and can name the cluster networks more appropriately. For example, we know which subnet is used for management, storage network 1, storage network 2 (and so on, if applicable). As a result we can name the networks more contextually.
+Once you define your configuration through Network ATC, we now understand how the subnets are going to be used, and we can name the cluster networks more appropriately. For example, we know which subnet is used for management, storage network 1, storage network 2 (and so on, if applicable). As a result we can name the networks more contextually.
 
-In the following screenshot, you can see the storage intent was applied to this set of adapters. There is another unknown cluster network shown which the administrator may want to investigate.
+In the following screenshot, you can see the storage intent was applied to this set of adapters. There's another unknown cluster network shown which the administrator may want to investigate.
 
 :::image type="content" source="media/manage-network-atc/cluster-network-naming.png" alt-text="Screenshot of Cluster Network Selection." lightbox="media/manage-network-atc/cluster-network-naming.png":::
 
@@ -149,7 +149,7 @@ This value enables or disables the intent-based selection of virtual machine liv
 If disabled:
 
 - Live migration transport selection uses the transport specified in VirtualMachineMigrationPerformanceOption override value.
-- If the VirtualMachineMigrationPerformanceOption override value is not specified, Network ATC reverts to behavior when Network ATC was absent.
+- If the VirtualMachineMigrationPerformanceOption override value isn't specified, Network ATC reverts to behavior when Network ATC was absent.
 - If null, but VirtualMachineMigrationPerformanceOption is configured, configure this option to $false and use the option specified in the VirtualMachineMigrationPerformanceOption override
 
 ###### Virtual machine migration performance option
@@ -158,7 +158,7 @@ Network ATC configures the live migration transport to TCPIP, Compression, or SM
 
 ###### Maximum concurrent virtual machine migrations
 
-Network ATC sets the default number of concurrent Virtual Machine migrations to one. The range of possible, allowed values for this property is one through ten. 
+Network ATC sets the default number of concurrent Virtual Machine migrations to one. The range of possible, allowed values for this property is one through 10.
 
 ###### Maximum SMB migration bandwidth
 
@@ -198,7 +198,7 @@ Remove-NetIntent -GlobalOverrides $clusterOverride
 
 ### Proxy configurations
 
-Proxy is unlike the existing ATC overrides because it is not tied to a specific intent. In fact, we support proxy configuration when there are no intents. We support this scenario best by implementing new global override parameters on Add/Set/Get-NetIntent, similar to Cluster Network Features.
+Proxy is unlike the existing ATC overrides because it isn't tied to a specific intent. In fact, we support proxy configuration when there are no intents. We support this scenario best by implementing new global override parameters on Add/Set/Get-NetIntent, similar to Cluster Network Features.
 
 The `New-NetIntentGlobalProxyOverrides` command is used to create an override object similar to existing QoS, RSS, and SwitchConfig overrides. The command will have two parameter sets:
 
diff --git a/azure-stack/hci/manage/monitor-hci-single.md b/azure-stack/hci/manage/monitor-hci-single.md
@@ -13,7 +13,7 @@ ms.date: 11/06/2023
 
 # Monitor a single Azure Stack HCI cluster with Insights
 
-[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2-21h2.md)]
+[!INCLUDE [applies-to](../../includes/hci-applies-to-22h2.md)]
 
 This article explains how to use Insights to monitor a single Azure Stack HCI cluster. For multiple Azure Stack HCI clusters, see [Monitor multiple Azure Stack HCI clusters with Insights](./monitor-hci-multi.md).
 
diff --git a/azure-stack/hci/manage/thin-provisioning.md b/azure-stack/hci/manage/thin-provisioning.md
diff --git a/azure-stack/hci/manage/troubleshoot-credssp.md b/azure-stack/hci/manage/troubleshoot-credssp.md
diff --git a/azure-stack/hci/manage/update-cluster.md b/azure-stack/hci/manage/update-cluster.md
diff --git a/azure-stack/hci/manage/windows-server-azure-edition.md b/azure-stack/hci/manage/windows-server-azure-edition.md
diff --git a/azure-stack/includes/hci-applies-to-22h2-21h2.md b/azure-stack/includes/hci-applies-to-22h2-21h2.md
