Skip to content

Commit 4039951

Browse files
Merge pull request #10038 from ryanberg-aquent/CI-7961-pri1-request
AB#7961: New article: Troubleshooting Tools for Windows Activation Issues on Azure VMs
2 parents dc0b686 + 04dce87 commit 4039951

File tree

3 files changed

+92
-6
lines changed

3 files changed

+92
-6
lines changed
82 KB
Loading

support/azure/virtual-machines/windows/toc.yml

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -455,17 +455,19 @@ items:
455455
- name: Troubleshoot extension issues
456456
href: /azure/virtual-machines/extensions/troubleshoot?context=/troubleshoot/azure/virtual-machines/windows/context/context
457457

458-
- name: Cannot activate my Windows VM
458+
- name: Cannot activate Windows
459459
items:
460-
- name: Understanding Generic Volume License Key
461-
href: /windows-server/get-started/kms-client-activation-keys?context=/troubleshoot/azure/virtual-machines/windows/context/context
460+
- name: KMS endpoints - new endpoints
461+
href: windows-activation-stopped-working.md
462462
- name: Troubleshooting
463463
href: troubleshoot-activation-problems.md
464464
- name: Frequently asked questions
465465
href: windows-virtual-machine-activation-faq.yml
466-
- name: KMS endpoints - new endpoints
467-
href: windows-activation-stopped-working.md
468-
- name: Common Issues
466+
- name: Troubleshooting tools
467+
href: windows-activation-troubleshoot-tools.md
468+
- name: Understanding Generic Volume License Key
469+
href: /windows-server/get-started/kms-client-activation-keys?context=/troubleshoot/azure/virtual-machines/windows/context/context
470+
- name: Common issues
469471
items:
470472
- name: Activation fails in forced tunneling scenario
471473
href: custom-routes-enable-kms-activation.md
Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: Troubleshooting Tools for Windows Activation
3+
description: Provides script-based tools to help diagnose and resolve Windows activation problems on Azure virtual machines.
4+
author: JarrettRenshaw
5+
ms.author: jarrettr
6+
manager: dcscontentpm
7+
ms.date: 10/24/2025
8+
ms.reviewer: v-jsitser, scotro, v-ryanberg
9+
ms.service: azure-virtual-machines
10+
ms.custom: sap:Cannot activate my Windows VM, troubleshooting tools for Windows VM activation
11+
---
12+
# Troubleshooting tools for Windows activation issues on Azure virtual machines
13+
14+
Windows activation problems on Azure virtual machines (VMs) can occur because of configuration, certificate, or connectivity issues. Microsoft provides two script-based tools to help diagnose and resolve most activation-related problems.
15+
16+
## Tools overview
17+
18+
### 1. Windows activation validation
19+
20+
**Purpose**
21+
22+
Validates the activation status of your Windows VM and checks for common issues that prevent successful activation.
23+
24+
**Key features**
25+
26+
- Confirms Windows activation state.
27+
- Detects misconfigurations.
28+
- Provides actionable guidance.
29+
30+
For more information, see [Windows activation validation](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/WindowsActivationValidation/README.md).
31+
32+
### 2. Azure Instance Metadata Service certificate check
33+
34+
**Purpose**
35+
36+
Verifies the integrity and availability of certificates that are required for activation through Azure Instance Metadata Service (IMDS).
37+
38+
**Key features**
39+
40+
- Validates IMDS certificate presence and correctness.
41+
- Identifies certificate-related activation failures.
42+
- Suggests corrective steps.
43+
44+
For more information, see:
45+
46+
- [Cause: Azure Instance Metadata Service connection issue](activation-watermark-appears.md#cause-1-azure-instance-metadata-service-connection-issue).
47+
- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/IMDSCertCheck/README.md).
48+
49+
## How to run these tools
50+
51+
You can run these tools in any of the following manners.
52+
53+
### 1. Download from GitHub and run within the VM
54+
55+
Download the scripts from GitHub, and then run them manually. To access the scripts, follow the resource links in the previous sections.
56+
57+
### 2. Use Azure Run Command
58+
59+
- Navigate to your VM in the Azure portal: > **Operations** > **Run Command**.
60+
- Select the script from the list (see the following screenshot).
61+
62+
:::image type="content" source="media/windows-activation-troubleshoot-tools/azure-portal-view.png" alt-text="Azure portal view Run Command example." lightbox="media/windows-activation-troubleshoot-tools/azure-portal-view.png":::
63+
64+
> [!NOTE]
65+
> Alternatively, you can run these commands by using a command-line interface (CLI) tool, Windows PowerShell, or Windows on ARM.
66+
67+
### 3. Use prepackaged Run Command scripts
68+
69+
For more information, see [Run scripts in your Windows VM by using action Run Commands](/azure/virtual-machines/windows/run-command).
70+
71+
## Recommended workflow
72+
73+
1. Run **Windows Activation Validation** to verify activation status and detect common issues.
74+
2. If certificate-related errors are suspected, run **IMDS Certificate Check**.
75+
3. Apply the suggested fixes or refer to the official documentation for advanced troubleshooting.
76+
77+
### **Additional resources**
78+
79+
- [Additional troubleshooting guidance](/azure/virtual-machines/windows/troubleshoot-activation-problems)
80+
- [Virtual Machines licensing FAQ](https://azure.microsoft.com/pricing/licensing-faq/?msockid=16f3be2d0f1066e62759a8150e8867c4).
81+
82+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
83+
84+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

0 commit comments

Comments
 (0)