Making adjustments

Author: Kai Nawroth

articles/azure-monitor/app/asp-net-core.md

@@ -227,11 +227,12 @@ while (true)
 
 The preceding sample is for a console app, but the same code can be used in any .NET applications. If any other telemetry modules are enabled to autocollect telemetry, it's important to ensure that the same configuration used for initializing those modules is used for the Live Metrics module.
 
-#### Secure the control channel
+#### Add an API key to configuration
 
-##### Add an API key to configuration
+If you set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section in [Live metrics: Monitor and diagnose with 1-second latency](./live-stream.md#legacy-option-create-an-api-key), you can add it to configuration.
 
-You can add an API key to configuration for ASP.NET, ASP.NET Core, WorkerService, and Azure Functions apps.
+> [!NOTE]
+> Setting up an authenticated channel by configuring a secret API key is no longer recommended. Instead, we recommend securing the live metrics channel by using [Microsoft Entra authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
 
 In the *Program.cs* file, add the following namespace:
 

articles/azure-monitor/app/asp-net.md

@@ -433,11 +433,12 @@ namespace LiveMetricsDemo
 
 The preceding sample is for a console app, but the same code can be used in any .NET applications. If any other telemetry modules are enabled to autocollect telemetry, it's important to ensure that the same configuration used for initializing those modules is used for the Live Metrics module.
 
-### Secure the control channel
+### Add an API key to configuration
 
-#### Add an API key to configuration
+If you set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section in [Live metrics: Monitor and diagnose with 1-second latency](./live-stream.md#legacy-option-create-an-api-key), you can add it to configuration.
 
-You can add an API key to configuration for ASP.NET, ASP.NET Core, WorkerService, and Azure Functions apps.
+> [!NOTE]
+> Setting up an authenticated channel by configuring a secret API key is no longer recommended. Instead, we recommend securing the live metrics channel by using [Microsoft Entra authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
 
 In the *applicationinsights.config* file, add `AuthenticationApiKey` to `QuickPulseTelemetryModule`:
 

articles/azure-monitor/app/live-stream.md

@@ -46,10 +46,10 @@ Live metrics is currently supported for ASP.NET, ASP.NET Core, Azure Functions,
    * [Node.js](opentelemetry-enable.md?tabs=nodejs): Live metrics is enabled by default.
    * [Python](opentelemetry-enable.md?tabs=python): Live metrics is enabled by default.
 
-  Using Classic:
+  Using Classic API:
 
-   * [ASP.NET](./asp-net.md): Live metrics is enabled by default.
-   * [ASP.NET Core](./asp-net-core.md): Live metrics is enabled by default.
+   * [ASP.NET](./asp-net.md): Live metrics is enabled by default but can also be enabled manually using code, see [Configure monitoring for ASP.NET with Azure Application Insights](./asp-net.md#enable-live-metrics-by-using-code-for-any-.net-application).
+   * [ASP.NET Core](./asp-net-core.md): Live metrics is enabled by default but can also be enabled manually using code, see [Application Insights for ASP.NET Core applications](./asp-net-core.md#enable-live-metrics-by-using-code-for-any-.net-application).
    * [.NET/.NET Core Console/Worker](./worker-service.md): Live metrics is enabled by default.
    * [.NET Applications: Enable using code](#enable-live-metrics-by-using-code-for-any-net-application).
    * [Node.js](./nodejs.md#live-metrics)
@@ -114,7 +114,7 @@ If you want to monitor a particular server role instance, you can filter by serv
 Live metrics custom filters allow you to control which of your application's telemetry is streamed to the live metrics view in the Azure portal. The filters criteria are sent to the apps that are instrumented with the Application Insights SDK. The filter value could potentially contain sensitive information, such as the customer ID. To keep this value secured and prevent potential disclosure to unauthorized applications, you have two options:
 
 - **Recommended:** Secure the live metrics channel by using [Microsoft Entra authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
-- **Legacy (no longer recommended):** Set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section.
+- **Legacy (no longer recommended):** Set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section below.
 
 > [!NOTE]
 > On September 30, 2025, API keys used to stream live metrics telemetry into Application Insights will be retired. After that date, applications that use API keys won't be able to send live metrics data to your Application Insights resource. Authenticated telemetry ingestion for live metrics streaming to Application Insights will need to be done with [Microsoft Entra authentication for Application Insights](./azure-ad-authentication.md).
@@ -138,14 +138,12 @@ It's possible to try custom filters without having to set up an authenticated ch
 
 ### Add an API key to configuration
 
-You can add an API key to configuration for ASP.NET, ASP.NET Core, WorkerService, and Azure Functions apps.
+You can add an API key to configuration for ASP.NET, ASP.NET Core, WorkerService, and Azure Functions apps:
 
-#### Instructions
-
-[.NET Core]()
-[.NET Framework]()
-[WorkerService]()
-[Azure Functions apps]()
+- [.NET Core](./asp-net-core.md#add-an-api-key-to-configuration)
+- [.NET Framework](./asp-net.md#add-an-api-key-to-configuration)
+- [WorkerService]()
+- [Azure Functions apps]()
 
 ## Supported features table
 

articles/azure-monitor/app/monitor-functions.md

@@ -178,9 +178,12 @@ def main(req: func.HttpRequest, context) -> func.HttpResponse:
 
 ## Live Metrics
 
-### Secure the control channel
+### Add an API key to configuration
 
-#### Add an API key to configuration
+If you set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section in [Live metrics: Monitor and diagnose with 1-second latency](./live-stream.md#legacy-option-create-an-api-key), you can add it to configuration.
+
+> [!NOTE]
+> Setting up an authenticated channel by configuring a secret API key is no longer recommended. Instead, we recommend securing the live metrics channel by using [Microsoft Entra authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
 
 For Azure Functions apps (v2), you can secure the channel with an API key by using an environment variable.
 

articles/azure-monitor/app/worker-service.md

@@ -315,11 +315,12 @@ The following sections list the full telemetry automatically collected by Applic
 
 [Live Metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. Although it might take a few minutes before telemetry appears in the portal and analytics, Live Metrics shows CPU usage of the running process in near real time. It can also show other telemetry like Requests, Dependencies, and Traces.
 
-#### Secure the control channel
+#### Add an API key to configuration
 
-##### Add an API key to configuration
+If you set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section in [Live metrics: Monitor and diagnose with 1-second latency](./live-stream.md#legacy-option-create-an-api-key), you can add it to configuration.
 
-You can add an API key to configuration for ASP.NET, ASP.NET Core, WorkerService, and Azure Functions apps.
+> [!NOTE]
+> Setting up an authenticated channel by configuring a secret API key is no longer recommended. Instead, we recommend securing the live metrics channel by using [Microsoft Entra authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
 
 Add the following namespace: