Merge pull request #9265 from MicrosoftDocs/main

Auto push to live 2025-07-03 02:34:58

Author: Deland-Han

support/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot missing application telemetry in Azure Monitor Application Insights
 description: Describes how to test connectivity and telemetry ingestion by using PowerShell or curl to identify the step in the processing pipeline that causes telemetry to go missing.
-ms.date: 05/28/2025
+ms.date: 07/03/2025
 ms.reviewer: aaronmax, toddfous, v-weizhu
 ms.service: azure-monitor
 ms.custom: sap:Missing or Incorrect data after enabling Application Insights in Azure Portal
@@ -11,6 +11,16 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 
 This article helps you to identify the step in the processing pipeline that causes telemetry to be missing by testing connectivity and telemetry ingestion using PowerShell or curl.
 
+## The Azure portal fails to pull or render the records you're trying to view
+
+Check if Microsoft Entra ID (formerly Azure AD) authentication is required. If your Application Insights resource is configured to use Microsoft Entra ID authentication, your application must also be configured to authenticate using Microsoft Entra ID.
+
+If the application hasn't been updated to support Microsoft Entra ID, telemetry won't be accepted by the backend, even if the instrumentation appears correct.
+
+To configure your application to authenticate using Microsoft Entra ID, follow the steps in [Enable Microsoft Entra ID (formerly Azure AD) authentication](/azure/azure-monitor/app/opentelemetry-configuration#enable-microsoft-entra-id-formerly-azure-ad-authentication).
+
+This scenario is a common cause of missing telemetry when migrating to Microsoft Entra ID–secured Application Insights resources.
+
 ## Steps that can cause telemetry to be missing
 
 The following graphic shows steps where telemetry can be missing during ingestion and consumption:
@@ -25,7 +35,7 @@ If application telemetry doesn't show in the Azure portal, failures across steps
 - The ingestion pipeline drops or severely slows down telemetry as part of its processing due to [service health](https://azure.microsoft.com/get-started/azure-portal/service-health/#overview).
 - (Uncommon) Log Analytics faces service health problems when saving telemetry records.
 - (Uncommon) The query API at `api.applicationinsights.io` fails when querying records from Log Analytics.
-- The Azure portal fails to pull or render the records you're trying to view.
+- Other possible causes and solutions are discussed in [Troubleshoot missing application telemetry in Azure Monitor Application Insights](investigate-missing-telemetry.md).
 
 > [!TIP]
 > The Application Insights support teams can't assist with networking issues. When submitting a support ticket for networking issues that prevent Application Insights from receiving telemetry data, such as DNS resolution failures, ensure that you specify Azure Networking or Azure Private Link in your product or issue description in the Azure portal. This will ensure that your support case is routed correctly.

support/windows-client/licensing-and-activation/error-certificate-connection-information-expired.md

@@ -2,7 +2,7 @@
 title: Certificate in the connection information has expired when accessing an AVD VM
 description: Helps resolve the error certificate in the connection information has expired when accessing an AVD VM by using the Remote Desktop client for Windows.
 manager: dcscontentpm
-ms.date: 01/15/2025
+ms.date: 07/03/2025
 audience: itpro
 ms.topic: troubleshooting
 ms.reviewer: kaushika, v-nehaborkar, jasone, v-lianna
@@ -39,6 +39,6 @@ To fix this issue, follow these steps:
 	:::image type="content" source="./media/error-certificate-connection-information-expired/remote-desktop-reset-user-data.png" alt-text="Screenshot of the Remote Desktop client with the Reset button which you can reset user data.":::
 
 2.	Close and uninstall the client.
-3.	Install [the latest version of the client](/azure/virtual-desktop/whats-new-client-windows).
+3.	Install [the latest version of the client](/windows-server/remote/remote-desktop-services/web-client-whats-new).
 
 For proper functionality, make sure that safe URLs are not subject to Secure Sockets Layer (SSL) inspection from the perspective of the Remote Desktop client. Also, verify that no blocking mechanisms are interfering with the safe URLs listed for the Remote Desktop client. If the above method doesn't work, try to disable or uninstall the antivirus software.