Changed what is in preview

Author: mrm9084

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

@@ -1,5 +1,5 @@
 ---
-title: Feature flag telemetry reference (preview)
+title: Feature flag telemetry reference
 titleSuffix: Azure App Configuration
 description: Learn how App Configuration allows for telemetry viewing for feature flags.
 ms.service: azure-app-configuration
@@ -9,25 +9,25 @@ ms.topic: reference
 ms.date: 11/06/2024
 ---
 
-# Tutorial: Feature flag telemetry reference (preview)
+# Tutorial: Feature flag telemetry reference
 
-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.
+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 tutorial, you:
 
 > [!div class="checklist"]
-> - 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)
+> - Learn which telemetry data is viewable using the Azure App Configuration provider libraries
+> - Learn which telemetry data is viewable using the Feature Management libraries
 
-## Viewing telemetry data (Preview)
+## Viewing telemetry data
 
-With telemetry (preview) enabled no other properties are added to the feature flag besides the setting enabling telemetry. The use of one of the Azure App Configuration provider libraries along with the Feature Management libraries is required to start collecting telemetry data.
+With telemetry enabled no other properties are added to the feature flag besides the setting enabling telemetry. The 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
 
 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.
+- **AllocationID**: A unique identifier for the feature flag in its current state. (preview)
 - **ETag**: The current ETag for the feature flag.
 - **FeatureFlagReference**: A reference to the feature flag in the format of `<your_store_endpoint>kv/<feature_flag_key>`, it also includes the label if one is present, `<your_store_endpoint>kv/<feature_flag_key>?label=<feature_flag_label>`.
 - **FeatureFlagId**: A unique identifier for the feature flag.
@@ -43,16 +43,16 @@ When the Feature Management libraries and the provider libraries are used togeth
 - **Version**: The version of this schema.
 - **Reason**: The reason the feature flag was enabled or disabled.
 - **Variant**: The variant that was selected for the feature flag.
-- **VariantAssignmentPercentage**: If a variant wasn't targeted specifically at the user, or one of the user's groups, this number is the Percentage chance of the user being assigned to the variant.
-- **DefaultWhenEnabled**: The default variant of the feature flag when it's enabled.
-- **AllocationID**: A unique identifier for the feature flag in its current state.
+- **VariantAssignmentPercentage**  (preview): If a variant wasn't targeted specifically at the user, or one of the user's groups, this number is the Percentage chance of the user being assigned to the variant.
+- **DefaultWhenEnabled**  (preview): The default variant of the feature flag when it's enabled.
+- **AllocationID** (preview): A unique identifier for the feature flag in its current state.
 - **ETag**: The current ETag for the feature flag.
 - **FeatureFlagReference**: A reference to the feature flag in the format of `<your_store_endpoint>kv/<feature_flag_key>`, it also includes the label if one is present, `<your_store_endpoint>kv/<feature_flag_key>?label=<feature_flag_label>`.
 - **FeatureFlagId**: A unique identifier for the feature flag.
 - **TargetingId**: The ID of the user that was assigned to the variant.
 
 The full schema can be found [here](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json).
 
-## Next steps (Preview)
+## Next steps
 
 In this tutorial, you learned about how to enable telemetry for feature flags in Azure App Configuration. To learn about how to use the telemetry data in your applications, continue to the following tutorial for your language or platform.