Add link to request scoping filter samples

Author: avanigupta

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

@@ -88,7 +88,7 @@ Create a new Azure Front Door profile and connect it to your App Configuration s
 1. **Filter Configuration to scope the request**: Configure one or more filters to control which requests pass through Azure Front Door. This prevents accidental exposure of sensitive configuration and ensures only the settings your application needs are accessible. The filters here must exactly match those used in your application code; otherwise, requests will be rejected by Azure Front Door.
 
    > [!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.
+   > 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.
    - **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.

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

@@ -76,7 +76,7 @@ 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.
+- **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}".
 - **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.