Merge pull request #206632 from poojapoojari/PP-08022022-Azure-app-conf-articles-1968585

[Freshness] US-1968585: Refresh top articles by PV - Azure App Configuration articles

Author: 19BMG00

articles/azure-app-configuration/cli-samples.md

@@ -5,13 +5,13 @@ author: maud-lv
 ms.author: malev
 ms.service: azure-app-configuration
 ms.topic: sample
-ms.date: 02/19/2020 
-ms.custom: devx-track-azurecli
+ms.date: 08/09/2022 
+ms.custom: devx-track-azurecli, devdivchpfy22
 ---
 
 # Azure CLI samples
 
-The following table includes links to bash scripts for Azure App Configuration by using the Azure CLI.
+The following table includes links to bash scripts for Azure App Configuration by using the [az appconfig](/cli/azure/appconfig) commands in the Azure CLI:
 
 | Script | Description |
 |-|-|

articles/azure-app-configuration/concept-feature-management.md

@@ -4,24 +4,24 @@ description: Turn features on and off using Azure App Configuration
 author: maud-lv
 ms.author: malev
 ms.service: azure-app-configuration
-ms.custom: devx-track-dotnet
+ms.custom: devx-track-dotnet, devdivchpfy22
 ms.topic: conceptual
-ms.date: 02/20/2020
+ms.date: 08/17/2022
 ---
 
 # Feature management overview
 
-Traditionally, shipping a new application feature requires a complete redeployment of the application itself. Testing a feature often requires multiple deployments of the application.  Each deployment may change the feature or expose the feature to different customers for testing.  
+Traditionally, shipping a new application feature requires a complete redeployment of the application itself. Testing a feature often requires multiple deployments of the application. Each deployment might change the feature or expose the feature to different customers for testing.  
 
-Feature management is a modern software-development practice that decouples feature release from code deployment and enables quick changes to feature availability on demand. It uses a technique called *feature flags* (also known as *feature toggles*, *feature switches*, and so on) to dynamically administer a feature's lifecycle.
+Feature management is a modern software-development practice that decouples feature release from code deployment and enables quick changes to feature availability on demand. It uses a technique called *feature flags* (also known as *feature toggles* and *feature switches*) to dynamically administer a feature's lifecycle.
 
 Feature management helps developers address the following problems:
 
 * **Code branch management**: Use feature flags to wrap new application functionality currently under development. Such functionality is "hidden" by default. You can safely ship the feature, even though it's unfinished, and it will stay dormant in production. Using this approach, called *dark deployment*, you can release all your code at the end of each development cycle. You no longer need to maintain code branches across multiple development cycles because a given feature requires more than one cycle to complete.
 * **Test in production**: Use feature flags to grant early access to new functionality in production. For example, you can limit access to team members or to internal beta testers. These users will experience the full-fidelity production experience instead of a simulated or partial experience in a test environment.
 * **Flighting**: Use feature flags to incrementally roll out new functionality to end users. You can target a small percentage of your user population first and increase that percentage gradually over time.
 * **Instant kill switch**: Feature flags provide an inherent safety net for releasing new functionality. You can turn application features on and off without redeploying any code. If necessary, you can quickly disable a feature without rebuilding and redeploying your application.
-* **Selective activation**: Use feature flags to segment your users and deliver a specific set of features to each group. You may have a feature that works only on a certain web browser. You can define a feature flag so that only users of that browser can see and use the feature. With this approach, you can easily expand the supported browser list later without having to make any code changes.
+* **Selective activation**: Use feature flags to segment your users and deliver a specific set of features to each group. You might have a feature that works only on a certain web browser. You can define a feature flag so that only users of that browser can see and use the feature. By using this approach, you can easily expand the supported browser list later without having to make any code changes.
 
 ## Basic concepts
 
@@ -46,7 +46,7 @@ if (featureFlag) {
 }
 ```
 
-You can set the value of `featureFlag` statically.
+You can set the value of `featureFlag` statically:
 
 ```csharp
 bool featureFlag = true;
@@ -70,11 +70,21 @@ if (featureFlag) {
 
 ## Feature flag repository
 
-To use feature flags effectively, you need to externalize all the feature flags used in an application. This allows you to change feature flag states without modifying and redeploying the application itself.
+To use feature flags effectively, you need to externalize all the feature flags used in an application. You can use this approach to change feature flag states without modifying and redeploying the application itself.
 
 Azure App Configuration provides a centralized repository for feature flags. You can use it to define different kinds of feature flags and manipulate their states quickly and confidently. You can then use the App Configuration libraries for various programming language frameworks to easily access these feature flags from your application.
 
-[Use feature flags in an ASP.NET Core app](./use-feature-flags-dotnet-core.md) shows how the .NET Core App Configuration provider and Feature Management libraries are used together to implement feature flags for your ASP.NET web application.
+[The feature flags in an ASP.NET Core app](./use-feature-flags-dotnet-core.md) shows how the .NET Core App Configuration provider and Feature Management libraries are used together to implement feature flags for your ASP.NET web application. For more information on feature flags in Azure App Configuration, see the following articles:
+
+* [Manage feature flags](./manage-feature-flags.md)
+* [Use conditional feature flags](./howto-feature-filters-aspnet-core.md)
+* [Enable a feature for specified users/groups](./howto-targetingfilter-aspnet-core.md)
+* [Add feature flags to an ASP.NET Core app](./quickstart-feature-flag-aspnet-core.md)
+* [Add feature flags to a .NET Framework app](./quickstart-feature-flag-dotnet.md)
+* [Add feature flags to an Azure Functions app](./quickstart-feature-flag-azure-functions-csharp.md)
+* [Add feature flags to a Spring Boot app](./quickstart-feature-flag-spring-boot.md)
+* [Use feature flags in an ASP.NET Core](./use-feature-flags-dotnet-core.md)
+* [Use feature flags in a Spring Boot app](./use-feature-flags-spring-boot.md)
 
 ## Next steps
 

articles/azure-app-configuration/concept-key-value.md

@@ -5,7 +5,8 @@ author: maud-lv
 ms.author: malev
 ms.service: azure-app-configuration
 ms.topic: conceptual
-ms.date: 08/04/2020
+ms.date: 08/17/2022
+ms.custom: devdivchpfy22
 ---
 
 # Keys and values
@@ -16,22 +17,22 @@ Azure App Configuration stores configuration data as key-values. Key-values are
 
 Keys serve as identifiers for key-values and are used to store and retrieve corresponding values. It's a common practice to organize keys into a hierarchical namespace by using a character delimiter, such as `/` or `:`. Use a convention best suited to your application. App Configuration treats keys as a whole. It doesn't parse keys to figure out how their names are structured or enforce any rule on them.
 
-Here is an example of key names structured into a hierarchy based on component services:
+Here's an example of key names structured into a hierarchy based on component services:
 
 ```aspx
     AppName:Service1:ApiEndpoint
     AppName:Service2:ApiEndpoint
 ```
 
-The use of configuration data within application frameworks might dictate specific naming schemes for key-values. For example, Java's Spring Cloud framework defines `Environment` resources that supply settings to a Spring application.  These are parameterized by variables that include *application name* and *profile*. Keys for Spring Cloud-related configuration data typically start with these two elements separated by a delimiter.
+The use of configuration data within application frameworks might dictate specific naming schemes for key-values. For example, Java's Spring Cloud framework defines `Environment` resources that supply settings to a Spring application. These resources are parameterized by variables that include *application name* and *profile*. Keys for Spring Cloud-related configuration data typically start with these two elements separated by a delimiter.
 
-Keys stored in App Configuration are case-sensitive, unicode-based strings. The keys *app1* and *App1* are distinct in an App Configuration store. Keep this in mind when you use configuration settings within an application because some frameworks handle configuration keys case-insensitively. We do not recommend using case to differentiate keys.
+Keys stored in App Configuration are case-sensitive, unicode-based strings. The keys *app1* and *App1* are distinct in an App Configuration store. Keep this in mind when you use configuration settings within an application because some frameworks handle configuration keys case-insensitively. We don't recommend using case to differentiate keys.
 
-You can use any unicode character in key names except for `%`. A key name cannot be `.` or `..` either. There's a combined size limit of 10 KB on a key-value. This limit includes all characters in the key, its value, and all associated optional attributes. Within this limit, you can have many hierarchical levels for keys.
+You can use any unicode character in key names except for `%`. A key name can't be `.` or `..` either. There's a combined size limit of 10 KB on a key-value. This limit includes all characters in the key, its value, and all associated optional attributes. Within this limit, you can have many hierarchical levels for keys.
 
 ### Design key namespaces
 
-There are two general approaches to naming keys used for configuration data: flat or hierarchical. These methods are similar from an application usage standpoint, but hierarchical naming offers a number of advantages:
+Two general approaches to naming keys are used for configuration data: flat or hierarchical. These methods are similar from an application usage standpoint, but hierarchical naming offers many advantages:
 
 * Easier to read. Delimiters in a hierarchical key name function as spaces in a sentence. They also provide natural breaks between words.
 * Easier to manage. A key name hierarchy represents logical groups of configuration data.
@@ -56,28 +57,28 @@ Label provides a convenient way to create variants of a key. A common use of lab
 Use labels as a way to create multiple versions of a key-value. For example, you can input an application version number or a Git commit ID in labels to identify key-values associated with a particular software build.
 
 > [!NOTE]
-> If you are looking for change versions, App Configuration keeps all changes of a key-value occurred in the past certain period of time automatically. See [point-in-time snapshot](./concept-point-time-snapshot.md) for more details.
+> If you're looking for change versions, App Configuration keeps all changes of a key-value that occurred in the past certain period of time automatically. For more information, see [point-in-time snapshot](./concept-point-time-snapshot.md).
 
 ### Query key-values
 
 Each key-value is uniquely identified by its key plus a label that can be `\0`. You query an App Configuration store for key-values by specifying a pattern. The App Configuration store returns all key-values that match the pattern including their corresponding values and attributes. Use the following key patterns in REST API calls to App Configuration:
 
 | Key | Description |
 |---|---|
-| `key` is omitted or `key=*` | Matches all keys |
-| `key=abc` | Matches key name **abc** exactly |
-| `key=abc*` | Matches key names that start with **abc** |
-| `key=abc,xyz` | Matches key names **abc** or **xyz**. Limited to five CSVs |
+| `key` is omitted or `key=*` | Matches all keys. |
+| `key=abc` | Matches key name **abc** exactly. |
+| `key=abc*` | Matches key names that start with **abc**.|
+| `key=abc,xyz` | Matches key names **abc** or **xyz**. Limited to five CSVs. |
 
 You also can include the following label patterns:
 
 | Label | Description |
 |---|---|
-| `label` is omitted or `label=*` | Matches any label, which includes `\0` |
-| `label=%00` | Matches `\0` label |
-| `label=1.0.0` | Matches label **1.0.0** exactly |
-| `label=1.0.*` | Matches labels that start with **1.0.** |
-| `label=%00,1.0.0` | Matches labels `\0` or **1.0.0**, limited to five CSVs |
+| `label` is omitted or `label=*` | Matches any label, which includes `\0`. |
+| `label=%00` | Matches `\0` label. |
+| `label=1.0.0` | Matches label **1.0.0** exactly. |
+| `label=1.0.*` | Matches labels that start with **1.0.**. |
+| `label=%00,1.0.0` | Matches labels `\0` or **1.0.0**, limited to five CSVs. |
 
 > [!NOTE]
 > `*`, `,`, and `\` are reserved characters in queries. If a reserved character is used in your key names or labels, you must escape it by using `\{Reserved Character}` in queries.
@@ -86,11 +87,17 @@ You also can include the following label patterns:
 
 Values assigned to keys are also unicode strings. You can use all unicode characters for values.
 
-### Use Content-Type
-Each key-value in App Configuration has a content-type attribute. You can optionally use this attribute to store information about the type of value in a key-value that helps your application to process it properly. You can use any format for the content-type. App Configuration uses [Media Types]( https://www.iana.org/assignments/media-types/media-types.xhtml) (also known as MIME types) for built-in data types such as feature flags, Key Vault references, and JSON key-values.
+### Use content type
+
+Each key-value in App Configuration has a content type attribute. You can optionally use this attribute to store information about the type of value in a key-value that helps your application to process it properly. You can use any format for the content type. App Configuration uses [Media Types]( https://www.iana.org/assignments/media-types/media-types.xhtml) (also known as MIME types) for built-in data types such as feature flags, Key Vault references, and JSON key-values.
 
 ## Next steps
 
-* [Point-in-time snapshot](./concept-point-time-snapshot.md)
-* [Feature management](./concept-feature-management.md)
-* [Event handling](./concept-app-configuration-event.md)
+> [!div class="nextstepaction"]
+> [Point-in-time snapshot](./concept-point-time-snapshot.md)
+
+> [!div class="nextstepaction"]
+> [Feature management](./concept-feature-management.md)
+
+> [!div class="nextstepaction"]
+> [Event handling](./concept-app-configuration-event.md)