Merge pull request #10592 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-26 18:00 UTC

Author: learn-build-service-prod[bot]

support/azure/app-service/troubleshoot-dotnet-visual-studio.md

@@ -38,8 +38,8 @@ Azure uses different endpoints for Key Management Services (KMS) activation depe
 
 To troubleshoot a Windows activation issue, follow these steps:
 
-> [!Important]
-> If you're experiencing Azure virtual machine (VM) Windows activation issues, see [Troubleshooting tools for Windows activation issues on Azure virtual machines](windows-activation-troubleshoot-tools).
+> [!IMPORTANT]  
+> If you're experiencing Azure virtual machine (VM) Windows activation issues, see [Troubleshooting tools for Windows activation issues on Azure virtual machines](windows-activation-troubleshoot-tools.md).
 
 1. Get the error message and the error code:
 

support/azure/virtual-machines/windows/troubleshoot-activation-problems.md

@@ -111,19 +111,19 @@ The following table lists the current checks and findings together with any pote
 | Check for binaries | Verifies that the guest agent .exe files (WindowsAzureGuestAgent.exe and WaAppAgent.exe) exist and is also used to help determine that the Guest Agent was installed.<br><br>If this check doesn't exist, it's likely that the guest agent has to be installed. |
 | Status of agent services | Verifies that the guest agent services (WindowsAzureGuestAgent and RdAgent) exist. Also used to help determine whether the guest agent was installed.<br><br>If this check doesn't exist, it's likely that the guest agent has to be installed. If it is installed, make sure that it's set to `Running` and that the StartType is `Automatic`. |
 | Status of `winmgmt` service | Verifies that the winmgmt service is running. |
-| Status of `KeyIso` service | Verifies that the `KeyIso (CNG Key Isolation)` service is running.<br><br>See [Solution: Start the CNG Key Isolation service](windows-azure-guest-agent#solution-start-the-cng-key-isolation-service). |
+| Status of `KeyIso` service | Verifies that the `KeyIso (CNG Key Isolation)` service is running.<br><br>See [Solution: Start the CNG Key Isolation service](windows-azure-guest-agent.md#solution-start-the-cng-key-isolation-service). |
 | Check if agent services/processes have crashed | This checks whether the Guest Agent services and processes have failed during the past day. If the incident is only a one-time event, it might not be important unless it occurs at the time when the issue is reported. However, if the services constantly fail, the incident must be investigated.<br><br>Start the investigation by looking in the WaAppAgent.log and system and application event logs. |
-| Checks if `stdregprov` is working | The VM agent MSI uses WMI StdRegProv to access the registry. If WMI isn't working correctly, the MSI can't set the RdAgent service path from the registry, and the MSI installation fails. <br><br> See [Guest Agent installation fails because of faulty WMI](windows-azure-guest-agent#guest-agent-installation-fails-because-of-faulty-wmi). |
+| Checks if `stdregprov` is working | The VM agent MSI uses WMI StdRegProv to access the registry. If WMI isn't working correctly, the MSI can't set the RdAgent service path from the registry, and the MSI installation fails. <br><br> See [Guest Agent installation fails because of faulty WMI](windows-azure-guest-agent.md#guest-agent-installation-fails-because-of-faulty-wmi). |
 | Agent is installed | Returns True if the guest agent is installed. Otherwise, the guest agent has to be installed. |
 | Installed by PA or MSI | This check determines whether the guest agent was installed by the provisioning agent or manually through .MSI. Neither of these options are `wrong`. However, it's included for information. |
 | Supported version | Checks whether the Azure Guest Agent version is up to date and supported. |
 | Proxy | Checks for netsh proxies. This check doesn't look for the existence of *all* types of proxy on the system. For example, it doesn't check whether a `3rd party proxy application` is installed. <br><br>If wireserver connectivity issues exist, you can start troubleshooting by using [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). |
 | CRP cert exists and is valid | Checks whether the CRP "Windows Azure CRP Certificate Generator" certificate exists. This certificate secures the communication with the host, and transfers protected settings that are used by extensions.<br><br> See [Troubleshoot extension certificate issues on a Windows VM in Azure](troubleshoot-extension-certificates-issues-windows-vm.md). |
-| WCF debugging | This check might run if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should be enabled only while debugging a WCF issue. It should not be left enabled while running a production workload.<br><br> See [Windows Azure Guest Agent service or the RdAgent service stops responding on startup (WCF)](windows-azure-guest-agent#windows-azure-guest-agent-service-or-the-rdagent-service-stops-responding-on-startup). |
+| WCF debugging | This check might run if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should be enabled only while debugging a WCF issue. It should not be left enabled while running a production workload.<br><br> See [Windows Azure Guest Agent service or the RdAgent service stops responding on startup (WCF)](windows-azure-guest-agent.md#windows-azure-guest-agent-service-or-the-rdagent-service-stops-responding-on-startup). |
 | Wireserver (168.63.129.16) connectivity on 80, 32526, and REST API | If wireserver connectivity issues exist, you can start troubleshooting by using [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). |
 | IMDS connectivity | IMDS connectivity isn't required for the guest agent to work, but the guest agent does try to connect. Therefore, you might see error entries in the logs. Additionally, VM assist itself gets information about the VM from IMDS to populate some sections of the .HTML file.<br><br>Not having connectivity to IMDS doesn't break the Guest Agent. See [Troubleshooting tool for Azure VM Instance Metadata Service issues](windows-vm-imds-tool.md). |
 | Third-party modules in WaAppAgent and WindowsAzureGuestAgent | Other applications occasionally inject their DLLs into the Guest Agent process. Usually, this behavior doesn't cause the guest agent to fail. However, DLLs might cause unexpected failures in the Guest Agent that are difficult to debug. Although DLLs rarely cause an issue, if any of them are from unexpectedly injected applications, consider removing or reconfiguring the application so that it no longer injects its .dlls into the guest agent processes. |
-| Checks permissions on machineKeys folder | Checks whether the default permissions exist on `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys`. If improper permissions are that block access are applied, extensions that use protected settings won't work even if the guest agent is in a 'Ready' state.<br><br> See [PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86](windows-azure-guest-agent#pinvoke-pfximportcertstore-failed-and-null-handle-is-returned-error-code-86). |
+| Checks permissions on machineKeys folder | Checks whether the default permissions exist on `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys`. If improper permissions are that block access are applied, extensions that use protected settings won't work even if the guest agent is in a 'Ready' state.<br><br> See [PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86](windows-azure-guest-agent.md#pinvoke-pfximportcertstore-failed-and-null-handle-is-returned-error-code-86). |
 | Checks permissions on `C:\WindowsAzure` and `C:\Packages` | Verifies that the System account has access to these directories. These directories are what the guest agent and extensions use for their binaries, configuration files, and log files. Therefore, it's important that the System account has access. |
 | Sufficient disk space |This check looks for available disk space. If the disk space is filled, the guest agent might not be able to write its status file, update, install extensions, and so on. In this situation, you must either delete files or expand the disk capacity. |
 | DHCP IP | If one private IP exists on the VM's network adapter, we highly recommend that you have DHCP enabled on the guest VM. If a static private IP address is needed, [configure it through the Azure portal or PowerShell](/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps). Make sure that the DHCP option inside the VM is enabled. This setting makes sure that the IP configuration always matches the VM configuration in Azure.<br><br>If multiple private IPs are assigned to the VM's network adapter, make sure that you follow these steps to [statically assign the IPs correctly](/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal#os-config). After you perform this procedure, if the guest agent can't communicate with 168.63.129.16, check whether the primary IP in Windows [matches the primary IP in the VM's network adapter in Azure](no-internet-access-multi-ip.md). |

support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md

@@ -1,8 +1,6 @@
 ---
 title: Troubleshoot unification output tables
 description: Provides troubleshooting steps for unification output tables in Microsoft Dynamics 365 Customer Insights - Data.
-author: wu-allison
-ms.author: allisonwu
 ms.date: 06/20/2024
 ms.reviewer: mhart
 ms.custom: sap:Data Unification

support/dynamics-365/customer-insights/data/profile-unification/troubleshoot-unification-output-tables.md

@@ -1,8 +1,6 @@
 ---
 title: Troubleshoot unification results
 description: Provides troubleshooting steps for unexpected deduplication, match, or merge results in Microsoft Dynamics 365 Customer Insights - Data.
-author: wu-allison
-ms.author: allisonwu
 ms.date: 06/20/2024
 ms.reviewer: mhart
 ms.custom: sap:Data Unification

support/dynamics-365/customer-insights/data/profile-unification/troubleshoot-unification-results.md

@@ -9,7 +9,9 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 
 # 401 Unauthorized errors in ASP.NET Core Web API with Microsoft Entra ID 
 
-When you call an ASP.NET Core Web API that's secured by using Microsoft Entra ID authentication, you might encounter a "401 Unauthorized" error. This article provides guidance for using `JwtBearerEvents` to capture detailed logs to troubleshoot these errors.
+## Summary
+
+This article provides guidance for using JwtBearerEvents to capture detailed logs to troubleshoot a "401 Unauthorized" error when you call an ASP.NET Core Web API that's secured by using Microsoft Entra ID authentication.
 
 ## Symptoms