Skip to content

Commit 8aaf625

Browse files
authored
Update investigate-missing-telemetry.md
1 parent baf1d27 commit 8aaf625

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ 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-
If the Application Insights data collection endpoint is set to use Microsoft Entra ID (formerly Azure AD) for authentication, the 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 is not correctly configured, telemetry will be rejected and wont appear in the Azure portal even if instrumentation appears correct and your application is generating telemetry data.
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.
1717

1818
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).
1919

0 commit comments

Comments
 (0)