Made it a reference doc not a how to doc

Author: mrm9084

articles/azure-app-configuration/TOC.yml

@@ -152,10 +152,6 @@
         href: howto-targetingfilter.md
       - name: ASP.NET Core
         href: howto-targetingfilter-aspnet-core.md
-    - name: Telemetry
-      items:
-      - name: Overview
-        href: howto-telemetry.md
     - name: Run experiments with variant feature flags
       items:
       - name: ASP.NET Core
@@ -334,6 +330,10 @@
         href: ./feature-management-python-reference.md
       - name: API reference
         href: https://microsoft.github.io/FeatureManagement-Python/html/index.html
+    - name: Telemetry
+      items:
+      - name: Feature flags telemetry reference
+        href: feature-flag-telemetry-reference.md
   - name: Deployment
     items:
     - name: ARM template

articles/azure-app-configuration/howto-telemetry.md renamed to articles/azure-app-configuration/feature-flag-telemetry-reference.md

@@ -1,5 +1,5 @@
 ---
-title: App Configuration and Telemetry (preview)
+title: Feature flag telemetry reference (preview)
 titleSuffix: Azure App Configuration
 description: Learn how App Configuration allows for telemetry viewing for feature flags.
 ms.service: azure-app-configuration
@@ -9,37 +9,23 @@ ms.topic: how-to
 ms.date: 10/31/2024
 ---
 
-# Tutorial: Azure App Configuration and Telemetry (preview)
+# Tutorial: Feature flag telemetry reference (preview)
 
-Having telemetry data on your feature flags can be a powerful tool for understanding how your feature flags are used. Telemetry allows you to make informed decisions about your feature management strategy. In this guide, you learn how to add telemetry (preview) to your Azure App Configuration feature flags and what data you can get from them.
+Having telemetry data on your feature flags can be a powerful tool for understanding how your feature flags are used. Telemetry (preview) allows you to make informed decisions about your feature management strategy.
 
 In this tutorial, you:
 
 > [!div class="checklist"]
-> - Add telemetry to a feature flag (preview)
 > - Learn which telemetry data is viewable using the Azure App Configuration provider libraries (preview)
 > - Learn which telemetry data is viewable using the Feature Management libraries (preview)
 
-## Prerequisites
-
-- An Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/) before you begin.
-- An App Configuration store. If you don't have an App Configuration store, see [Create an App Configuration store](./quickstart-azure-app-configuration-create.md).
-- A feature flag. If you don't have a feature flag, see [Create a feature flag](./manage-feature-flags.md).
-
-## Add telemetry to a feature flag (preview)
-
-1. Open your App Configuration store in the Azure portal.
-1. In the **Operations** section, select the **Feature manager** page.
-1. When viewing the list of feature flags, you should see a column labeled **Telemetry** (preview), it should show as **Disabled**. Right click on the feature flag you want to enable telemetry for and select **Edit**.
-1. In the new view, select the **Telemetry** tab.
-1. Select the **Enable Telemetry** checkbox and then the **Review + update** button at the bottom of the page.
-1. On the **Review + update** page, select the **Update** button.
-
 ## Viewing telemetry data (Preview)
 
-With telemetry (preview) enabled no other properties are added to the feature flag besides the setting enabling telemetry. Use of an Azure App Configuration provider library that supports telemetry is required to start collecting telemetry data.
+With telemetry (preview) enabled no other properties are added to the feature flag besides the setting enabling telemetry. The additional use of one of the Azure App Configuration provider libraries along with the Feature Management libraries is required to start collecting telemetry data.
+
+### Azure App Configuration provider libraries
 
-When telemetry is enabled, the Azure App Configuration provider libraries add more properties to the feature flags when they're retrieved. A new object is added to the **telemetry** section of the feature flag called **metadata**. The **metadata** object contains the following properties:
+The use of an Azure App Configuration provider library that supports telemetry is required to start collecting telemetry data. When telemetry is enabled, the Azure App Configuration provider libraries add more properties to the feature flags when they're retrieved. A new object is added to the **telemetry** section of the feature flag called **metadata**. The **metadata** object contains the following properties:
 
 - **AllocationID**: A unique identifier for the feature flag in its current state.
 - **ETag**: The current ETag for the feature flag.
@@ -48,7 +34,9 @@ When telemetry is enabled, the Azure App Configuration provider libraries add mo
 
 The full schema can be found [here](https://github.com/microsoft/FeatureManagement/tree/main/Schema/FeatureEvaluationEvent/FeatureEvaluationEventWithAzureAppConfiguration.v1.0.0.schema.json).
 
-When feature flags with telemetry enabled are used with the Feature Management libraries, more properties are added to the telemetry data and be sent to location to be viewed, such as Azure Monitor. When using our provided connections to Azure Monitor a **custom_event** is published to Open Telemetry with the following properties whenever a telemetry enabled feature flag is evaluated:
+### Feature Management libraries
+
+When feature flags with telemetry enabled are used with the Feature Management libraries in addition to the provider libraries, more properties are added to the telemetry data and be sent to location to be viewed, such as Azure Monitor. When using our provided connections to Azure Monitor a **custom_event** is published to Open Telemetry with the following properties whenever a telemetry enabled feature flag is evaluated:
 
 - **Feature_Name**: The name of the feature flag.
 - **Enabled**: A boolean value indicating if the feature flag is enabled.