Skip to content

Commit 5568a07

Browse files
authored
Merge pull request #9276 from AarDavMax/docs-editor/investigate-missing-telemetry-1751824957
Update investigate-missing-telemetry.md
2 parents 3d5b09b + 8aaf625 commit 5568a07

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

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

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot missing application telemetry in Azure Monitor Application Insights
33
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.
4-
ms.date: 07/03/2025
4+
ms.date: 07/07/2025
55
ms.reviewer: aaronmax, toddfous, v-weizhu
66
ms.service: azure-monitor
77
ms.custom: sap:Missing or Incorrect data after enabling Application Insights in Azure Portal
@@ -13,14 +13,10 @@ This article helps you to identify the step in the processing pipeline that caus
1313

1414
## The Azure portal fails to pull or render the records you're trying to view
1515

16-
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.
17-
18-
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.
16+
If your Application Insights data collection endpoint is configured to use Microsoft Entra ID (formerly Azure AD) for authentication, your application must also be configured to authenticate with Microsoft Entra ID. In this scenario, your application is responsible for authenticating using Microsoft Entra ID. If the application isn't correctly configured, telemetry will be rejected and won't appear in the Azure portal even if instrumentation appears correct and your application is generating telemetry data.
1917

2018
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).
2119

22-
This scenario is a common cause of missing telemetry when migrating to Microsoft Entra ID–secured Application Insights resources.
23-
2420
## Steps that can cause telemetry to be missing
2521

2622
The following graphic shows steps where telemetry can be missing during ingestion and consumption:

0 commit comments

Comments
 (0)