Merge pull request #311932 from MaryanneNjeri/user/maryanne/update_afd_docs

Update screen shots in Azure Front door docs in App config

Author: Carolyn135

articles/azure-app-configuration/concept-hyperscale-client-configuration.md

@@ -63,9 +63,7 @@ Configure one or more filters to control which requests are allowed to pass thro
 
 - Configure Azure Front Door filters to precisely match your application's configuration requirements. Only expose the exact key patterns your application uses. For example, if your application loads keys with the `"App1:"` prefix, configure the Azure Front Door rule to allow only `"App1:"` keys, not broader patterns like `"App"`.
 
-- If your application loads feature flags, provide `".appconfig.featureflag/{YOUR-FEATURE-FLAG-PREFIX}"` filter for the Key with *Starts with* operator.
-
-- If you're using App Configuration provider libraries and your application loads ONLY feature flags, you should add two key filters in the Azure Front Door rules - one for `ALL` keys with no label and second for all keys starting with `".appconfig.featureflag/{YOUR-FEATURE-FLAG-PREFIX}"`. This is because App Configuration provider libraries load all key-values with no label by default when no key-value selector is specified. 
+- If you're using App Configuration provider libraries and your application loads ONLY feature flags, you should add two filters in the Azure Front Door rules - a key-value filter for ALL keys with no label and a feature flag filter for all keys starting with your feature flag prefix. This is because App Configuration provider libraries load all key-values with no label by default when no key-value selector is specified. 
 
 #### Request scoping through multiple Azure Front Door endpoints
 

articles/azure-app-configuration/how-to-connect-azure-front-door.md

@@ -90,14 +90,12 @@ Create a new Azure Front Door profile and connect it to your App Configuration s
    > [!NOTE]
    > To configure scoping filters correctly, ensure that the prefix filter in Azure Front Door exactly matches the selector your application uses to load keys from App Configuration. For example, if your application loads keys using the prefix "App1:", configure the same Starts with = "App1:" key filter in Azure Front Door. If your application instead uses a more specific key prefix such as "App1:Version", but Azure Front Door is allowlisted for "App1:" key filter (or vice versa), the request will be rejected because the selectors do not match exactly. See [examples for matching application filters with endpoint filters](https://github.com/Azure/AppConfiguration/blob/main/docs/AzureFrontDoor/readme.md).
 
-   - **Key**: The key filter to apply when querying Azure App Configuration for key-values. Reserved characters: asterisk (`*`), comma (`,`), and backslash (`\`) must be escaped using a backslash (`\`) when filtering multiple key-values.
+   - **Key of key-value filter**: The key filter to apply when querying Azure App Configuration for key-values. Reserved characters: asterisk (`*`), comma (`,`), and backslash (`\`) must be escaped using a backslash (`\`) when filtering multiple key-values.
    - **Label**: The label filter to apply when querying Azure App Configuration for key-values. Reserved characters: asterisk (`*`), comma (`,`), and backslash (`\`) must be escaped using a backslash (`\`) when filtering multiple key-values.
    - **Tags**: The tag name and value filter to apply when querying Azure App Configuration for key-values. Reserved characters: asterisk (`*`), comma (`,`), backslash (`\`), and equals (`=`) must always be escaped using a backslash (`\`).
+   - **Key of feature flag filter**: The filter to apply to feature flag names when querying Azure App Configuration for feature flags. Reserved characters: asterisk (`*`), comma (`,`), and backslash (`\`) must be escaped using a backslash (`\`) when filtering multiple feature flags. The reserved feature flag prefix `.appconfig.featureflag/` will be automatically appended to every feature flag key filter.
    - **Snapshot name**: Name of snapshot whose content should be accessible through this Azure Front Door endpoint. You can select one or more snapshots to restrict access to specific snapshots.
 
-   > [!NOTE]
-   > If your application loads feature flags, provide ".appconfig.featureflag/{YOUR-FEATURE-FLAG-PREFIX}" filter for the Key with *Starts with* operator.
-
 
 1. Select **Create & Connect** to create the profile and establish the connection.
 

articles/azure-app-configuration/how-to-load-azure-front-door-configuration-provider.md

@@ -77,9 +77,9 @@ For a complete sample app, refer to [JavaScript App with Azure App Configuration
 ## Considerations and edge cases
 
 - **Request scoping**: The key-value filters used by your application must match exactly the filters configured for the Azure Front Door endpoint; any mismatch will cause the request to be rejected. For example, if your endpoint is configured to allow access to keys starting with an "App1:" prefix, the application code must also load keys starting with "App1:". However, if your application loads keys starting with a more specific prefix like "App1:Prod:", the request is rejected. See [examples for matching application filters with endpoint filters](https://github.com/Azure/AppConfiguration/blob/main/docs/AzureFrontDoor/readme.md).
-- **Exclusively loading feature flags**: If your application loads only feature flags, you should add two key filters in the Azure Front Door rules - one for ALL keys with no label and second for all keys starting with ".appconfig.featureflag/{YOUR-FEATURE-FLAG-PREFIX}".
+- **Exclusively loading feature flags**: If your application loads only feature flags, you should add two filters in the Azure Front Door rules - one a key-value filter for ALL keys with no label and second a feature flag filter for all keys starting with your feature flag prefix.
 - **Refresh strategy**: Applications loading from Azure Front Door cannot use sentinel key refresh. If refresh is enabled, the application must be configured to [monitor all selected keys](./howto-best-practices.md#monitoring-all-selected-keys) for changes.
-- **Snapshot references**: If your application loads a key-value that is a [snapshot reference](./concept-snapshot-references.md), Azure Front Door must be configured to allowlist the referenced snapshot. Include the snapshot name in your Azure Front Door filters to enable snapshot resolution.
+- **Snapshot references**: If your application loads a key-value that is a [snapshot reference](./concept-snapshot-references.md), Azure Front Door must be configured to allow list the referenced snapshot. Include the snapshot name in your Azure Front Door filters to enable snapshot resolution.
 
 ## Troubleshooting