Merge pull request #2695 from MicrosoftDocs/cynthn-patch-2

Fix broken links and update Managed Run Command details

Author: prmerger-automator[bot]

articles/virtual-machines/windows/run-command-managed.md

@@ -8,17 +8,13 @@ author: GabstaMSFT
 ms.author: cynthn
 ms.date: 08/18/2025
 ms.topic: how-to
-ms.reviewer: jushiman
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 # Customer intent: As an IT administrator, I want to execute scripts on Azure Windows VMs using managed Run Commands, so that I can efficiently manage and troubleshoot machine and application issues.
 ---
 # Run scripts in your Windows VM by using managed Run Commands
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets 
 
-> [!IMPORTANT]
-> **Managed Run Command**  is currently available in Azure CLI, PowerShell, and API at this time. Portal functionality is on the roadmap.
-
 The Run Command feature uses the virtual machine (VM) agent to execute scripts within an Azure Windows VM. You can use these scripts for general machine or application management. They can help you quickly diagnose and remediate VM access and network issues and get the VM back to a good state.
 
 The *updated* managed Run Command uses the same VM agent channel to execute scripts and provides the following enhancements over the [original action orientated Run Command](run-command.md): 
@@ -29,6 +25,9 @@ The *updated* managed Run Command uses the same VM agent channel to execute scri
 - Support for long running (hours/days) scripts 
 - Passing secrets (parameters, passwords) in a secure manner
 
+> [!IMPORTANT]
+> **Managed Run Command**  is currently available in Azure CLI, PowerShell, and API at this time.
+
 ## Prerequisites
 
 ### **Windows Operating Systems Supported**
@@ -61,7 +60,7 @@ The *updated* managed Run Command uses the same VM agent channel to execute scri
 | **IMDSCertCheck** | Checks IMDS Health and then analyzes currently installed certificates that IMDS depends upon. If missing, shows additional details and mitigation steps. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/IMDSCertCheck) |
 | **RDPSettings** | Checks registry settings and domain policy settings. Suggests policy actions if machine is part of a domain or modifies the settings to default values. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/RDPSettings) |
 | **ResetRDPCert** | Removes the SSL certificate tied to the RDP listener and restores the RDP listener security to default. Use this script if you see any issues with the certificate. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/ResetRDPCert) |
-| **Windows_WindowsActivation_Validation** | Checks the current Windows license status (activated or not) and alert is generated if the machine is not property activated. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_WindowsActivation_Validation) |
+| **Windows_WindowsActivation_Validation** | Checks the current Windows license status (activated or not) and alert is generated if the machine is not property activated. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Activation_Validation/README.md) |
 | **SetRDPPort** | Sets the default or user specified port number for Remote Desktop connections. Enables firewall rule for inbound access to the port. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/SetRDPPort) |
 | **DisableNLA** | Disables Network Level Authentication (NLA). You must restart the VM after the script completes for the change to take effect. The script itself does not restart the VM. You can use this script to disable NLA if RDP connections are failing with error 'The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA.' or error 'An authentication error has occurred. The Local Security Authority cannot be contacted.' NLA is a security feature that should only be disabled temporarily to allow RDP connections to succeed until the domain controller connectivity issue have been resolved. | [readme](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/DisableNLA) |