Removing legacy option from docs

Kai Nawroth · Kai Nawroth · commit 9f2a67d6f3b7 · 2024-06-21T14:04:29.000-07:00
diff --git a/articles/azure-monitor/app/asp-net-core.md b/articles/azure-monitor/app/asp-net-core.md
@@ -166,19 +166,19 @@ If `IConfiguration` has loaded configuration from multiple providers, then `serv
 
 Run your application and make requests to it. Telemetry should now flow to Application Insights. The Application Insights SDK automatically collects incoming web requests to your application, along with the following telemetry.
 
-### Live Metrics
+### Live metrics
 
-[Live Metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but Live Metrics shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
+[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but live metrics shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
 
-#### Enable Live Metrics by using code for any .NET application
+#### Enable live metrics by using code for any .NET application
 
 > [!NOTE]
-> Live Metrics is enabled by default when you onboard it by using the recommended instructions for .NET applications.
+> Live metrics is enabled by default when you onboard it by using the recommended instructions for .NET applications.
 
-To manually configure Live Metrics:
+To manually configure live metrics:
 
 1. Install the NuGet package [Microsoft.ApplicationInsights.PerfCounterCollector](https://www.nuget.org/packages/Microsoft.ApplicationInsights.PerfCounterCollector).
-1. The following sample console app code shows setting up Live Metrics:
+1. The following sample console app code shows setting up live metrics:
 
 ```csharp
 using Microsoft.ApplicationInsights;
@@ -207,14 +207,14 @@ quickPulseModule.RegisterTelemetryProcessor(quickPulseProcessor);
 
 // Create a TelemetryClient instance. It is important
 // to use the same TelemetryConfiguration here as the one
-// used to set up Live Metrics.
+// used to set up live metrics.
 TelemetryClient client = new TelemetryClient(config);
 
 // This sample runs indefinitely. Replace with actual application logic.
 while (true)
 {
     // Send dependency and request telemetry.
-    // These will be shown in Live Metrics.
+    // These will be shown in live metrics.
     // CPU/Memory Performance counter is also shown
     // automatically without any additional steps.
     client.TrackDependency("My dependency", "target", "http://sample",
@@ -225,29 +225,7 @@ 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.
-
-#### Add an API key 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).
-
-In the *Program.cs* file, add the following namespace:
-
-```csharp
-using Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector.QuickPulse;
-```
-
-Then add the following service registration:
-
-```csharp
-// Existing code which includes services.AddApplicationInsightsTelemetry() to enable Application Insights.
-builder.Services.ConfigureTelemetryModule<QuickPulseTelemetryModule> ((module, o) => module.AuthenticationApiKey = "YOUR-API-KEY-HERE");
-```
-
-For more information on how to configure ASP.NET Core applications, see [Configuring telemetry modules in ASP.NET Core](#configure-or-remove-default-telemetrymodules).
+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.
 
 ### ILogger logs
 
@@ -329,7 +307,7 @@ var aiOptions = new Microsoft.ApplicationInsights.AspNetCore.Extensions.Applicat
 // Disables adaptive sampling.
 aiOptions.EnableAdaptiveSampling = false;
 
-// Disables QuickPulse (Live Metrics stream).
+// Disables live metrics (formerly QuickPulse).
 aiOptions.EnableQuickPulseMetricStream = false;
 
 builder.Services.AddApplicationInsightsTelemetry(aiOptions);
@@ -346,7 +324,7 @@ public void ConfigureServices(IServiceCollection services)
     // Disables adaptive sampling.
     aiOptions.EnableAdaptiveSampling = false;
 
-    // Disables QuickPulse (Live Metrics stream).
+    // Disables live metrics (formerly QuickPulse).
     aiOptions.EnableQuickPulseMetricStream = false;
     services.AddApplicationInsightsTelemetry(aiOptions);
 }
@@ -531,7 +509,7 @@ By default, the following automatic-collection modules are enabled. These module
 * `RequestTrackingTelemetryModule`: Collects RequestTelemetry from incoming web requests.
 * `DependencyTrackingTelemetryModule`: Collects [DependencyTelemetry](./asp-net-dependencies.md) from outgoing HTTP calls and SQL calls.
 * `PerformanceCollectorModule`: Collects Windows PerformanceCounters.
-* `QuickPulseTelemetryModule`: Collects telemetry to show in the Live Metrics portal.
+* `QuickPulseTelemetryModule`: Collects telemetry to show in the live metrics portal.
 * `AppServicesHeartbeatTelemetryModule`: Collects heartbeats (which are sent as custom metrics), about the App Service environment where the application is hosted.
 * `AzureInstanceMetadataTelemetryModule`: Collects heartbeats (which are sent as custom metrics), about the Azure VM environment where the application is hosted.
 * `EventCounterCollectionModule`: Collects [EventCounters](eventcounters.md). This module is a new feature and is available in SDK version 2.8.0 and later.
diff --git a/articles/azure-monitor/app/asp-net.md b/articles/azure-monitor/app/asp-net.md
@@ -361,19 +361,19 @@ Although it's possible to manually add the JavaScript (Web) SDK Loader Script to
 
 For the template-based ASP.NET MVC app from this article, the file that you need to edit is *_Layout.cshtml*. You can find it under **Views** > **Shared**. To add client-side monitoring, open *_Layout.cshtml* and follow the [JavaScript (Web) SDK Loader Script-based setup instructions](./javascript-sdk.md?tabs=javascriptwebsdkloaderscript#get-started) from the article about client-side JavaScript SDK configuration.
 
-## Live Metrics
+## Live metrics
 
-[Live Metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but Live Metrics shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
+[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but live metrics shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
 
-### Enable Live Metrics by using code for any .NET application
+### Enable live metrics by using code for any .NET application
 
 > [!NOTE]
-> Live Metrics is enabled by default when you onboard it by using the recommended instructions for .NET applications.
+> Live metrics is enabled by default when you onboard it by using the recommended instructions for .NET applications.
 
-To manually configure Live Metrics:
+To manually configure live metrics:
 
 1. Install the NuGet package [Microsoft.ApplicationInsights.PerfCounterCollector](https://www.nuget.org/packages/Microsoft.ApplicationInsights.PerfCounterCollector).
-1. The following sample console app code shows setting up Live Metrics:
+1. The following sample console app code shows setting up live metrics:
 
 ```csharp
 using Microsoft.ApplicationInsights;
@@ -410,14 +410,14 @@ namespace LiveMetricsDemo
 
             // Create a TelemetryClient instance. It is important
             // to use the same TelemetryConfiguration here as the one
-            // used to set up Live Metrics.
+            // used to set up live metrics.
             TelemetryClient client = new TelemetryClient(config);
 
             // This sample runs indefinitely. Replace with actual application logic.
             while (true)
             {
                 // Send dependency and request telemetry.
-                // These will be shown in Live Metrics.
+                // These will be shown in live metrics.
                 // CPU/Memory Performance counter is also shown
                 // automatically without any additional steps.
                 client.TrackDependency("My dependency", "target", "http://sample",
@@ -431,22 +431,7 @@ 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.
-
-### Add an API key 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).
-
-In the *applicationinsights.config* file, add `AuthenticationApiKey` to `QuickPulseTelemetryModule`:
-
-```xml
-<Add Type="Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector.QuickPulse.QuickPulseTelemetryModule, Microsoft.AI.PerfCounterCollector">
-      <AuthenticationApiKey>YOUR-API-KEY-HERE</AuthenticationApiKey>
-</Add>
-```
+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.
 
 ## Frequently asked questions
 
diff --git a/articles/azure-monitor/app/live-stream.md b/articles/azure-monitor/app/live-stream.md
@@ -38,22 +38,24 @@ Live metrics is currently supported for ASP.NET, ASP.NET Core, Azure Functions,
 
 1. Follow language-specific guidelines to enable live metrics:
 
-  Using OpenTelemetry (Recommended):
+  # [OpenTelemetry (Recommended)](#tab/otel)
 
    * [ASP.NET](opentelemetry-enable.md?tabs=net): Live metrics is not supported.
    * [ASP.NET Core](opentelemetry-enable.md?tabs=aspnetcore): Live metrics is enabled by default.
    * [Java](./opentelemetry-enable.md?tabs=java): Live metrics is enabled by default.
    * [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 API:
+  # [Classic API](#tab/classic)
   
-   * [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).
+   * [ASP.NET](./asp-net.md): Live metrics is enabled by default but can also be [enabled manually using code](./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](./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)
 
+---
+
 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.
@@ -111,10 +113,7 @@ If you want to monitor a particular server role instance, you can filter by serv
 
 ## Secure the control channel
 
-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-option-create-an-api-key) below.
+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, secure the live metrics channel by using [Microsoft Entra authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
 
 > [!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).
@@ -126,25 +125,6 @@ It's possible to try custom filters without having to set up an authenticated ch
 
 :::image type="content" source="media/live-stream/live-stream-auth.png" alt-text="Screenshot that shows the Authorize connected servers dialog." lightbox="media/live-stream/live-stream-auth.png":::
 
-### Legacy option: Create an API key
-
-1. Select the **API Access** tab and then select **Create API key**.
-
-   :::image type="content" source="./media/live-stream/api-key.png" lightbox="./media/live-stream/api-key.png" alt-text="Screenshot that shows selecting the API Access tab and the Create API key button.":::
-
-1. Select the **Authenticate SDK control channel** checkbox and then select **Generate key**.
-
-   :::image type="content" source="./media/live-stream/create-api-key.png" lightbox="./media/live-stream/create-api-key.png" alt-text="Screenshot that shows the Create API key pane. Select Authenticate SDK control channel checkbox and then select Generate key.":::
-
-### 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:
-
-- [.NET Core](./asp-net-core.md#add-an-api-key-to-configuration)
-- [.NET Framework](./asp-net.md#add-an-api-key-to-configuration)
-- [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
 
 | Language                         | Basic metrics       | Performance metrics | Custom filtering    | Sample telemetry    | CPU split by process |
diff --git a/articles/azure-monitor/app/monitor-functions.md b/articles/azure-monitor/app/monitor-functions.md
@@ -176,17 +176,6 @@ def main(req: func.HttpRequest, context) -> func.HttpResponse:
       ...
 ```
 
-## Live Metrics
-
-### Add an API key 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).
-
-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
 
 * Read more instructions and information about [monitoring Azure Functions](../../azure-functions/functions-monitoring.md).
diff --git a/articles/azure-monitor/app/worker-service.md b/articles/azure-monitor/app/worker-service.md
