Merge pull request #10093 from ryanberg-aquent/CI-8029

ryanberg-aquent · web-flow · commit e7ae256024f4 · 2025-11-03T10:34:34.000-10:00
AB#8029: Add include with link to Troubleshooting Tools for Windows Activation Issues on Azure VMs
diff --git a/support/azure/virtual-machines/windows/activation-watermark-appears.md b/support/azure/virtual-machines/windows/activation-watermark-appears.md
@@ -16,6 +16,8 @@ ms.topic: troubleshooting-problem-resolution
 
 This document discusses how to resolve the continued presence of a Windows activation watermark on Microsoft Azure virtual machines.
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Prerequisites
 
 - [Azure CLI](/cli/azure/install-azure-cli-windows)
diff --git a/support/azure/virtual-machines/windows/custom-routes-enable-kms-activation.md b/support/azure/virtual-machines/windows/custom-routes-enable-kms-activation.md
@@ -21,6 +21,8 @@ ms.author: jarrettr
 
 This article describes how to resolve the KMS activation problem that you might experience when you enable forced tunneling in site-to-site VPN connection or ExpressRoute scenarios.
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Symptom
 
 You enable [forced tunneling](/azure/vpn-gateway/vpn-gateway-forced-tunneling-rm) on Azure virtual network subnets to direct all Internet-bound traffic back to your on-premises network. In this scenario, the Azure virtual machines (VMs) that run Windows fail to activate Windows.
diff --git a/support/azure/virtual-machines/windows/troubleshoot-activation-problems.md b/support/azure/virtual-machines/windows/troubleshoot-activation-problems.md
@@ -21,6 +21,8 @@ ms.custom: sap:Cannot activate my Windows VM
 
 This article helps you troubleshoot an activation issue that occurs when you create a Microsoft Azure Windows virtual machine (VM).
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Understanding Azure KMS endpoints for Windows product activation of Azure VMs
 
 Azure uses different endpoints for Key Management Services (KMS) activation depending on the cloud region in which the VM resides. When using this troubleshooting guide, use the appropriate KMS endpoint that applies to your region.
diff --git a/support/azure/virtual-machines/windows/windows-activation-duplicate-client-machine-id.md b/support/azure/virtual-machines/windows/windows-activation-duplicate-client-machine-id.md
@@ -15,6 +15,8 @@ We generally recommend using Azure Key Management Services (KMS) servers to acti
 > [!NOTE]
 > This article applies only when you use a self-hosted KMS server for activation. It doesn't apply when you use Azure KMS for activation.
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Symptoms
 
 When you use a self-hosted KMS server for activation and try to activate more than one Windows Server VM, the activation fails after the evaluation period, and your self-hosted KMS server reports the following error in the **Duplicate Client Machine ID Report**:
diff --git a/support/azure/virtual-machines/windows/windows-activation-stopped-working.md b/support/azure/virtual-machines/windows/windows-activation-stopped-working.md
@@ -13,6 +13,8 @@ ms.custom: sap:Cannot activate my Windows VM
 
 This article discusses important changes that were made to Key Management Services (KMS) IP addresses that cause problems for Microsoft Windows virtual machine (VM) activation in Windows Azure. These changes affect Azure Global cloud users who configured custom routes or firewall rules to allow KMS IP addresses and who were previously able to activate Windows VMs successfully.
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)] 
+
 ## Overview
 
 #### Who's affected
diff --git a/support/azure/virtual-machines/windows/windows-virtual-machine-activation-faq.yml b/support/azure/virtual-machines/windows/windows-virtual-machine-activation-faq.yml
@@ -14,7 +14,7 @@ metadata:
   ms.reviewer: cwhitley, jusilver, scotro, v-naqviadil, v-leedennis, v-weizhu
   ms.custom: sap:Cannot activate my Windows VM
   appliesto: Windows VMs
-    
+        
 title: Azure Windows virtual machine activation FAQ
 summary: This article answers frequently asked questions (FAQ) about activating a Microsoft Windows virtual machine (VM) in Azure.
 sections:
@@ -46,4 +46,5 @@ additionalContent: |
   - [Troubleshoot Windows virtual machine activation problems in Azure](./troubleshoot-activation-problems.md)
   - [Advanced troubleshooting - Microsoft Windows activation error codes](../../../windows-server/deployment/troubleshoot-activation-error-codes.md)
   
+  [!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
   [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
diff --git a/support/azure/virtual-machines/windows/windows-vm-activation-error-0x800705b4.md b/support/azure/virtual-machines/windows/windows-vm-activation-error-0x800705b4.md
@@ -13,6 +13,8 @@ ms.custom: sap:Cannot activate my Windows VM
 
 This article provides a solution to the error 0x800705B4 that occurs when you try to activate an Azure Windows virtual machine (VM).
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Symptoms
 
 When you try to activate an Azure Windows VM, you receive the 0x800705B4 error:
diff --git a/support/azure/virtual-machines/windows/windows-vm-activation-error-0xc004f074.md b/support/azure/virtual-machines/windows/windows-vm-activation-error-0xc004f074.md
@@ -14,6 +14,8 @@ ms.reviewer: cwhitley, mumustafa, v-naqviadil, v-leedennis
 
 This article discusses how to resolve the 0xC004F074 error that occurs when you try to activate a Windows virtual machine (VM) in Microsoft Azure.
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Prerequisites
 
 - [PowerShell](/powershell/scripting/install/installing-powershell-on-windows)
diff --git a/support/azure/virtual-machines/windows/windows-vm-activation-error-0xc004fd01-0xc004fd02.md b/support/azure/virtual-machines/windows/windows-vm-activation-error-0xc004fd01-0xc004fd02.md
@@ -14,6 +14,8 @@ ms.custom: sap:Cannot activate my Windows VM
 
 This article provides a solution to the error 0xC004FD01 or 0xC004FD02 that occurs when you try to activate an Azure Windows virtual machine (VM).
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Symptoms
 
 When you try to activate an Azure Windows VM, you receive an error message that resembles the following samples:
diff --git a/support/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md b/support/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md
@@ -0,0 +1,11 @@
+---
+author: JarrettRenshaw
+ms.author: jarrettr
+manager: dcscontentpm
+ms.service: azure-virtual-machines
+ms.topic: include
+ms.date: 10/31/2025
+---
+
+> [!IMPORTANT]
+> If you're experiencing Azure virtual machine (VM) Windows activation issues, see [Troubleshooting tools for Windows activation issues on Azure virtual machines](../../azure/virtual-machines/windows/windows-activation-troubleshoot-tools.md). 
diff --git a/support/windows-server/licensing-and-activation/error-0x80070005-access-denied.md b/support/windows-server/licensing-and-activation/error-0x80070005-access-denied.md
@@ -20,6 +20,8 @@ This article discusses how to fix Windows activation error 0x80070005 (access de
 
 _Applies to:_ &nbsp; Windows Server, all versions, and Windows client, all versions
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## Symptoms
 
 You run the `slmgr /ato` command to activate a domain-joined computer that's running Windows. However, Windows doesn't activate, and you receive the following error message:
diff --git a/support/windows-server/licensing-and-activation/error-0xc004e015-sl-e-eul-consumption-failed-activate-windows.md b/support/windows-server/licensing-and-activation/error-0xc004e015-sl-e-eul-consumption-failed-activate-windows.md
@@ -24,6 +24,8 @@ This error occurs because the *C:\\Windows\\System32\\spp\\store\\2.0\\tokens.da
 
 To resolve the issue, [rebuild the tokens.dat file](../licensing-and-activation/rebuild-tokens-dotdat-file.md) and activate Windows again.
 
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
+
 ## More information
 
 Normally, Windows can create a *tokens.dat* file. If you get an "Error: Product not found" error, run the following commands to reapply the Key Management Services (KMS) client key:
diff --git a/support/windows-server/licensing-and-activation/error-0xc004f06c-activate-windows.md b/support/windows-server/licensing-and-activation/error-0xc004f06c-activate-windows.md
@@ -70,3 +70,5 @@ To resolve this error, follow these steps:
         `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters`.
 
     2. Make sure the value of the **Type** registry entry is **NT5DS**. This means the computer is synchronizing its time with the AD DS time hierarchy.
+
+[!INCLUDE [virtual-machines-windows-activation-troubleshoot-tools](~/includes/azure/virtual-machines-windows-activation-troubleshoot-tools.md)]
