Making further adjustments

Author: Kai Nawroth

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

@@ -229,7 +229,7 @@ The preceding sample is for a console app, but the same code can be used in any
 
 #### 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.
+If you [create a secret API key](./live-stream.md#legacy-option-create-an-api-key) to set up an authenticated channel, 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).

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

@@ -435,7 +435,7 @@ The preceding sample is for a console app, but the same code can be used in any
 
 ### 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.
+If you [create a secret API key](./live-stream.md#legacy-option-create-an-api-key) to set up an authenticated channel, 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).

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

@@ -54,7 +54,7 @@ Live metrics is currently supported for ASP.NET, ASP.NET Core, Azure Functions,
    * [.NET Applications: Enable using code](#enable-live-metrics-by-using-code-for-any-net-application).
    * [Node.js](./nodejs.md#live-metrics)
 
-2. In the [Azure portal](https://portal.azure.com), open the Application Insights resource for your app. Then open Live Stream.
+2. In the [Azure portal](https://portal.azure.com), open the Application Insights resource for your application. Under **Investigate**, open **Live metrics**.
 
 3. [Secure the control channel](#secure-the-control-channel) if you might use sensitive data like customer names in your filters.
 
@@ -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 below.
+- **Legacy (no longer recommended):** Set up an authenticated channel by configuring a secret API key as explained in the [Legacy option section](#legacy-option-create-an-api-key) 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,12 +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:
+For ASP.NET, ASP.NET Core, WorkerService, and Azure Functions apps, you can add an API key to configuration:
 
 - [.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]()
+- [WorkerService](./worker-service.md#add-an-api-key-to-configuration)
+- [Azure Functions apps](./monitor-functions.md#add-an-api-key-to-configuration)
 
 ## Supported features table
 

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

@@ -180,13 +180,11 @@ def main(req: func.HttpRequest, context) -> func.HttpResponse:
 
 ### 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.
+For Azure Functions apps (v2), you can secure the channel with an API key by using an environment variable.
 
 > [!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.
-
 Create an API key from within your Application Insights resource and go to **Settings** > **Configuration** for your Azure Functions app. Select **New application setting**, enter a name of `APPINSIGHTS_QUICKPULSEAUTHAPIKEY`, and enter a value that corresponds to your API key.
 
 ## Next steps

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

@@ -317,7 +317,7 @@ The following sections list the full telemetry automatically collected by Applic
 
 #### 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.
+If you [create a secret API key](./live-stream.md#legacy-option-create-an-api-key) to set up an authenticated channel, 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).