Merge pull request #9170 from MicrosoftDocs/main

Auto push to live 2025-06-20 02:33:20

Author: Deland-Han

support/azure/azure-monitor/app-insights/data/how-to-update-third-party-server-configuration.md

@@ -8,6 +8,8 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 ---
 # How to update third-party server configuration
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 The server side must be able to accept connections that have certain headers. Depending on the `Access-Control-Allow-Headers` configuration on the server side, it's often necessary to extend the server-side list by manually adding the `Request-Id`, `Request-Context`, and `traceparent` (W3C distributed header) headers. For example, the configuration might resemble the following text:
 
 `Access-Control-Allow-Headers: Request-Id, traceparent, Request-Context, <your header>`.

support/azure/azure-monitor/app-insights/data/troubleshoot-app-insights-nodejs.md

@@ -13,6 +13,8 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 
 This article discusses troubleshooting steps to fix general problems that are related to the Application Insights monitoring of Node.js apps and services.
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 ## Troubleshooting checklist
 
 ### Troubleshooting step 1: Test connectivity between your application host and the ingestion service

support/azure/azure-monitor/app-insights/telemetry/asp-net-troubleshoot-no-data.md

@@ -13,7 +13,9 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 
 This article provides troubleshooting information to help resolve issues when data is missing or doesn't appear when you're using Application Insights for .NET and .NET Core.
 
-> [!NOTE]
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
+> [!IMPORTANT]
 > This article was recently updated to use the term *Azure Monitor logs* instead of *Log Analytics*. Log data is still stored in a Log Analytics workspace, and it's still collected and analyzed by the same Log Analytics service. We're updating the terminology to better reflect the role of [logs in Azure Monitor](/azure/azure-monitor/logs/data-platform-logs). For more information, see [Azure Monitor terminology changes](/azure/azure-monitor/terminology).
 
 ## Some of my telemetry is missing

support/azure/azure-monitor/app-insights/telemetry/duplicate-telemetry-data.md

@@ -8,6 +8,8 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 ---
 # Receive duplicate telemetry data from Application Insights JavaScript SDK
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 If the SDK reports correlation recursively, enable the configuration setting of `excludeRequestFromAutoTrackingPatterns` to exclude the duplicate data. This scenario can occur when you use connection strings. The syntax for the configuration setting is `excludeRequestFromAutoTrackingPatterns: [<endpointUrl>]`.
 
 [!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]

support/azure/azure-monitor/app-insights/telemetry/java-2x-troubleshoot.md

@@ -15,6 +15,8 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 
 This article provides troubleshooting solutions to common issues in a Q&A format for Application Insights Java 2.x.
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 > [!CAUTION]
 > This document applies to Application Insights Java 2.x, which is no longer recommended.
 >

support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md

@@ -15,6 +15,8 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 
 This article provides troubleshooting information to resolve common issues that might occur when you're instrumenting a Java application by using the Java agent for Application Insights. Application Insights is a feature of the Azure Monitor platform service.
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 ## Check the self-diagnostic log file
 
 By default, Application Insights Java 3._x_ produces a log file that's named *applicationinsights.log* in the same directory

support/azure/azure-monitor/app-insights/telemetry/javascript-sdk-troubleshooting.md

@@ -13,6 +13,8 @@ ms.reviewer: mmcc, toddfous, aaronmax, v-leedennis
 
 This article discusses how to troubleshoot various issues that involve the [Application Insights JavaScript SDK](https://github.com/Microsoft/ApplicationInsights-JS). The subjects in this article include SDK load failure for JavaScript web apps and source map support for JavaScript apps.
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 <!-- 
 Editor's Note: This link name above "SDK Load Failure" has a direct references by https://go.microsoft.com/fwlink/?linkid=2128109 which is embedded in the snippet and from the JavaScript Page. If you change this text you MUST also update these references.
 -->

support/azure/azure-monitor/app-insights/telemetry/sdk-support-guidance.md

@@ -0,0 +1,56 @@
+---
+title: Application Insights SDK support guidance 
+description: Support guidance for Application Insights legacy and preview SDKs.
+ms.topic: how-to
+ms.date: 06/18/2025
+ms.service: azure-monitor
+ms.reviewer: vgorbenko, aaronmax, v-weizhu
+ms.custom: sap:Application Insights
+---
+
+# Application Insights SDK support guidance
+
+Microsoft announces feature deprecations or breaking changes at least one year in advance and strives to provide a seamless process for migration to the replacement experience.
+
+For more information, review the [Azure SDK Lifecycle and Support Policy](https://azure.github.io/azure-sdk/policies_support.html).
+
+> [!NOTE]
+> Diagnostic tools often provide better insight into the root cause of a problem when the latest stable SDK version is used.
+
+## SDK update guidance
+
+Support engineers are expected to provide SDK update guidance according to the following table, referencing the current SDK version in use and any alternatives.
+
+|Current SDK version in use |Alternative version available |Update policy for support |
+|---------|---------|---------|
+|Latest GA SDK                                                                  | Newer preview version available                | **NO UPDATE NECESSARY** |
+|GA SDK                                                                         | Newer GA released < one year ago               | **UPDATE RECOMMENDED**  |
+|GA SDK                                                                         | Newer GA released > one year ago               | **UPDATE REQUIRED**     |
+|Unsupported ([support policy](/lifecycle/faq/azure))                           | Any supported version                          | **UPDATE REQUIRED**     |
+|Latest Preview                                                                 | No newer version available                     | **NO UPDATE NECESSARY** |
+|Latest Preview                                                                 | Newer GA SDK                                   | **UPDATE REQUIRED**     |
+|Preview                                                                        | Newer preview version                          | **UPDATE REQUIRED**     |
+
+> [!NOTE]
+>
+> * General Availability (GA) refers to non-beta versions.
+> * Preview refers to beta versions.
+
+> [!TIP]
+> Switching to [autoinstrumentation](/azure/azure-monitor/app/codeless-overview) eliminates the need for manual SDK updates.
+
+> [!WARNING]
+> Only commercially reasonable support is provided for Preview versions of the SDK. If a support incident requires escalation to development for further guidance, customers will be asked to use a fully supported SDK version to continue support. Commercially reasonable support does not include an option to engage Microsoft product development resources; technical workarounds may be limited or not possible.
+
+## Release notes
+
+Reference the release notes to see the current version of Application Insights SDKs and previous versions release dates.
+
+- [.NET SDKs (Including ASP.NET, ASP.NET Core, and Logging Adapters)](https://github.com/Microsoft/ApplicationInsights-dotnet/releases)
+- [Python](https://github.com/census-instrumentation/opencensus-python/blob/master/contrib/opencensus-ext-azure/CHANGELOG.md)
+- [Node.js](https://github.com/Microsoft/ApplicationInsights-node.js/releases)
+- [JavaScript](https://github.com/microsoft/ApplicationInsights-JS/releases)
+
+Our [Service Updates](https://azure.microsoft.com/updates/?service=application-insights) also summarize major Application Insights improvements.
+
+[!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]

support/azure/azure-monitor/app-insights/telemetry/troubleshoot-webpages-issues.md

@@ -11,6 +11,8 @@ ms.reviewer: mmcc, toddfous, aaronmax, v-weizhu
 
 The article explains certain issues that involve [Application Insights JavaScript SDK for webpages](/azure/azure-monitor/app/javascript) and offers strategies to help fix these issues.
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 ## I'm seeing a "0" value recorded for page views in Application Insights
 
 This is by design when instrumenting Single Page Applications (SPA). See the following [GitHub issue](https://github.com/microsoft/ApplicationInsights-JS/issues/1139). 

support/azure/azure-monitor/app-insights/telemetry/webpages-not-get-request-context-header.md

@@ -8,6 +8,8 @@ ms.custom: sap:Missing or Incorrect data after enabling Application Insights in
 ---
 # Failed to get Request-Context correlation header as it may be not included in the response or not accessible error
 
+[!INCLUDE [Azure Help Support](../../../../includes/azure/application-insights-sdk-support.md)]
+
 The `correlationHeaderExcludedDomains` configuration property is an exclude list that disables correlation headers for specific domains. This option is useful if you include headers that cause the request to fail or not to be sent because of third-party server configuration. This property supports wildcards. Therefore, you can specify a value such as `*.queue.core.windows.net`. Avoid adding the application domain to this property because this stops the SDK from including the required distributed tracing `Request-Id`, `Request-Context`, and `traceparent` headers as part of the request.
 
 [!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]