Merge pull request #266622 from zhiyuanliang-ms/zhiyuanliang/remove-net-core-tab

Azure App Configuration - Remove .NET Core and some miscellaneous changes

Author: ttorble

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

@@ -18,9 +18,9 @@ The following table includes links to Azure CLI scripts for Azure App Configurat
 |**Create**||
 | [Create an App Configuration store](./scripts/cli-create-service.md) | Creates a resource group and an App Configuration store instance.  |
 |**Use**||
-| [Work with key values](./scripts/cli-work-with-keys.md) | Creates, views, updates, and deletes key values. |
-| [Import key values](./scripts/cli-import.md) | Imports key values from other sources. |
-| [Export key values](./scripts/cli-export.md) | Exports key values to other targets. |
+| [Work with key-values](./scripts/cli-work-with-keys.md) | Creates, views, updates, and deletes key-values. |
+| [Import key-values](./scripts/cli-import.md) | Imports key-values from other sources. |
+| [Export key-values](./scripts/cli-export.md) | Exports key-values to other targets. |
 |**Delete**||
 | [Delete an App Configuration store](./scripts/cli-delete-service.md) | Deletes an App Configuration store instance.  |
 | | |

articles/azure-app-configuration/concept-customer-managed-keys.md

@@ -3,7 +3,7 @@ title: Use customer-managed keys to encrypt your configuration data
 description: Encrypt your configuration data using customer-managed keys
 author: maud-lv
 ms.author: malev
-ms.date: 08/30/2022
+ms.date: 02/20/2024
 ms.custom: devdivchpfy22, devx-track-azurecli
 ms.topic: conceptual
 ms.service: azure-app-configuration
@@ -38,21 +38,9 @@ After these resources are configured, use the following steps so that the Azure
 1. Assign a managed identity to the Azure App Configuration instance.
 1. Grant the identity `GET`, `WRAP`, and `UNWRAP` permissions in the target Key Vault's access policy.
 
-## Enable customer-managed key encryption for your Azure App Configuration instance
+## Enable customer-managed key encryption for your App Configuration store
 
-To begin, you'll need a properly configured Azure App Configuration instance. If you don't yet have an App Configuration instance available, follow one of these quickstarts to set one up:
-
-- [Create an ASP.NET Core app with Azure App Configuration](quickstart-aspnet-core-app.md)
-- [Create a .NET Core app with Azure App Configuration](quickstart-dotnet-core-app.md)
-- [Create a .NET Framework app with Azure App Configuration](quickstart-dotnet-app.md)
-- [Create a Java Spring app with Azure App Configuration](quickstart-java-spring-app.md)
-- [Create a JavaScript app with Azure App Configuration](quickstart-javascript.md)
-- [Create a Python app with Azure App Configuration](quickstart-python.md)
-
-> [!TIP]
-> The Azure Cloud Shell is a free interactive shell that you can use to run the command line instructions in this article. It has common Azure tools preinstalled, including the .NET Core SDK. If you are logged in to your Azure subscription, launch your [Azure Cloud Shell](https://shell.azure.com) from shell.azure.com. You can learn more about Azure Cloud Shell by [reading our documentation](../cloud-shell/overview.md).
-
-### Create and configure an Azure Key Vault
+1. [Create an App Configuration store](./quickstart-azure-app-configuration-create.md) if you don't have one.
 
 1. Create an Azure Key Vault by using the Azure CLI. Both `vault-name` and `resource-group-name` are user-provided and must be unique. We use `contoso-vault` and `contoso-resource-group` in these examples.
 

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

@@ -6,7 +6,7 @@ ms.author: malev
 ms.service: azure-app-configuration
 ms.custom: devdivchpfy22
 ms.topic: conceptual
-ms.date: 08/17/2022
+ms.date: 02/20/2024
 ---
 
 # Feature management overview
@@ -74,7 +74,7 @@ To use feature flags effectively, you need to externalize all the feature flags
 
 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.
 
-[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:
+[The feature flags in an ASP.NET Core app](./use-feature-flags-dotnet-core.md) shows how the App Configuration .NET 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)

articles/azure-app-configuration/concept-point-time-snapshot.md

@@ -28,7 +28,7 @@ You can use the Azure portal or the Azure CLI to retrieve past key-values.
    :::image type="content" source="media/restore-key-value-portal.png" alt-text="Screenshot of the Azure portal, selecting restore":::
 
 3. Select **Date: Select date** to select a date and time you want to revert to.
-4. Click outside of the date and time fields or press **Tab** to validate your choice. You can now see which key values have changed between your selected date and time and the current time. This step helps you understand what keys and values you're preparing to revert to. 
+4. Click outside of the date and time fields or press **Tab** to validate your choice. You can now see which key-values have changed between your selected date and time and the current time. This step helps you understand what keys and values you're preparing to revert to. 
 
    :::image type="content" source="media/restore-key-value-past-values.png" alt-text="Screenshot of the Azure portal with saved key-values":::
 

articles/azure-app-configuration/enable-dynamic-configuration-aspnet-core.md

@@ -6,7 +6,7 @@ author: zhenlan
 ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.topic: tutorial
-ms.date: 09/30/2022
+ms.date: 02/20/2024
 ms.author: zhenlwa
 ms.custom: devx-track-csharp
 ---
@@ -37,7 +37,6 @@ A *sentinel key* is a key that you update after you complete the change of all o
 
 1. Open *Program.cs*, and update the `AddAzureAppConfiguration` method you added previously during the quickstart.
 
-    #### [.NET 6.0+](#tab/core6x)
     ```csharp
     // Load configuration from Azure App Configuration
     builder.Configuration.AddAzureAppConfiguration(options =>
@@ -51,35 +50,6 @@ A *sentinel key* is a key that you update after you complete the change of all o
     });
     ```
 
-    #### [.NET Core 3.x](#tab/core3x)
-    ```csharp
-    public static IHostBuilder CreateHostBuilder(string[] args) =>
-        Host.CreateDefaultBuilder(args)
-            .ConfigureWebHostDefaults(webBuilder =>
-            {
-                webBuilder.ConfigureAppConfiguration(config =>
-                {
-                    //Retrieve the Connection String from the secrets manager
-                    IConfiguration settings = config.Build();
-                    string connectionString = settings.GetConnectionString("AppConfig");
-
-                    // Load configuration from Azure App Configuration
-                    config.AddAzureAppConfiguration(options =>
-                    {
-                        options.Connect(connectionString)
-                               // Load all keys that start with `TestApp:` and have no label
-                               .Select("TestApp:*", LabelFilter.Null)
-                               // Configure to reload configuration if the registered sentinel key is modified
-                               .ConfigureRefresh(refreshOptions =>
-                                    refreshOptions.Register("TestApp:Settings:Sentinel", refreshAll: true));
-                    });
-                });
-
-                webBuilder.UseStartup<Startup>();
-            });
-    ```
-    ---
-
     The `Select` method is used to load all key-values whose key name starts with *TestApp:* and that have *no label*. You can call the `Select` method more than once to load configurations with different prefixes or labels. If you share one App Configuration store with multiple apps, this approach helps load configuration only relevant to your current app instead of loading everything from your store.
 
     In the `ConfigureRefresh` method, you register keys you want to monitor for changes in your App Configuration store. The `refreshAll` parameter to the `Register` method indicates that all configurations you specified by the `Select` method will be reloaded if the registered key changes.
@@ -89,7 +59,6 @@ A *sentinel key* is a key that you update after you complete the change of all o
 
 1. Add Azure App Configuration middleware to the service collection of your app.
 
-    #### [.NET 6.0+](#tab/core6x)
     Update *Program.cs* with the following code. 
 
     ```csharp
@@ -110,26 +79,8 @@ A *sentinel key* is a key that you update after you complete the change of all o
     // ... ...
     ```
 
-    #### [.NET Core 3.x](#tab/core3x)
-    Open *Startup.cs*, and update the `ConfigureServices` method.
-
-    ```csharp
-    public void ConfigureServices(IServiceCollection services)
-    {
-        services.AddRazorPages();
-
-        // Add Azure App Configuration middleware to the container of services.
-        services.AddAzureAppConfiguration();
-
-        // Bind configuration "TestApp:Settings" section to the Settings object
-        services.Configure<Settings>(Configuration.GetSection("TestApp:Settings"));
-    }   
-    ```
-    ---
-
 1. Call the `UseAzureAppConfiguration` method. It enables your app to use the App Configuration middleware to update the configuration for you automatically.
 
-    #### [.NET 6.0+](#tab/core6x)
     Update *Program.cs* withe the following code. 
 
     ```csharp
@@ -151,40 +102,6 @@ A *sentinel key* is a key that you update after you complete the change of all o
     // ... ...
     ```
 
-    #### [.NET Core 3.x](#tab/core3x)
-    Update the `Configure` method in *Startup.cs*.
-
-    ```csharp
-    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
-    {
-        if (env.IsDevelopment())
-        {
-            app.UseDeveloperExceptionPage();
-        }
-        else
-        {
-            app.UseExceptionHandler("/Error");
-            app.UseHsts();
-        }
-
-        // Use Azure App Configuration middleware for dynamic configuration refresh.
-        app.UseAzureAppConfiguration();
-
-        app.UseHttpsRedirection();
-        app.UseStaticFiles();
-
-        app.UseRouting();
-
-        app.UseAuthorization();
-
-        app.UseEndpoints(endpoints =>
-        {
-            endpoints.MapRazorPages();
-        });
-    }
-    ```
-    ---
-
 You've set up your app to use the [options pattern in ASP.NET Core](/aspnet/core/fundamentals/configuration/options) during the quickstart. When the underlying configuration of your app is updated from App Configuration, your strongly typed `Settings` object obtained via `IOptionsSnapshot<T>` is updated automatically. Note that you shouldn't use the `IOptions<T>` if dynamic configuration update is desired because it doesn't read configuration data after the app has started.
 
 ## Request-driven configuration refresh
@@ -197,7 +114,7 @@ The configuration refresh is triggered by the incoming requests to your web app.
 
 ## Build and run the app locally
 
-1. To build the app by using the .NET Core CLI, run the following command in the command shell:
+1. To build the app by using the .NET CLI, run the following command in the command shell:
 
     ```console
         dotnet build

articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md

@@ -1,40 +1,40 @@
 ---
-title: "Tutorial: Use dynamic configuration using push refresh in a .NET Core app"
+title: "Tutorial: Use dynamic configuration using push refresh in a .NET app"
 titleSuffix: Azure App Configuration
-description: In this tutorial, you learn how to dynamically update the configuration data for .NET Core apps using push refresh
+description: In this tutorial, you learn how to dynamically update the configuration data for .NET apps using push refresh
 services: azure-app-configuration
 author: MBSolomon
 manager: zhenlan
 ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.custom: devx-track-dotnet
 ms.topic: tutorial
-ms.date: 02/03/2022
-ms.author: msolomon
+ms.date: 02/20/2024
+ms.author: malev
 #Customer intent: I want to use push refresh to dynamically update my app to use the latest configuration data in App Configuration.
 ---
-# Tutorial: Use dynamic configuration using push refresh in a .NET Core app
+# Tutorial: Use dynamic configuration using push refresh in a .NET app
 
-The App Configuration .NET Core client library supports updating configuration on demand without causing an application to restart. An application can be configured to detect changes in App Configuration using one or both of the following two approaches.
+The App Configuration .NET client library supports updating configuration on demand without causing an application to restart. An application can be configured to detect changes in App Configuration using one or both of the following two approaches.
 
 1. Poll Model: This is the default behavior that uses polling to detect changes in configuration. Once the cached value of a setting expires, the next call to `TryRefreshAsync` or `RefreshAsync` sends a request to the server to check if the configuration has changed, and pulls the updated configuration if needed.
 
 1. Push Model: This uses [App Configuration events](./concept-app-configuration-event.md) to detect changes in configuration. Once App Configuration is set up to send key value change events to Azure Event Grid, the application can use these events to optimize the total number of requests needed to keep the configuration updated. Applications can choose to subscribe to these either directly from Event Grid, or through one of the [supported event handlers](../event-grid/event-handlers.md) such as a webhook, an Azure function, or a Service Bus topic.
 
-This tutorial shows how you can implement dynamic configuration updates in your code using push refresh. It builds on the app introduced in the tutorial. Before you continue, finish Tutorial: [Use dynamic configuration in a .NET Core app](./enable-dynamic-configuration-dotnet-core.md) first.
+This tutorial shows how you can implement dynamic configuration updates in your code using push refresh. It builds on the app introduced in the tutorial. Before you continue, finish Tutorial: [Use dynamic configuration in a .NET app](./enable-dynamic-configuration-dotnet-core.md) first.
 
 You can use any code editor to do the steps in this tutorial. [Visual Studio Code](https://code.visualstudio.com/) is an excellent option that's available on the Windows, macOS, and Linux platforms.
 
 In this tutorial, you learn how to:
 > [!div class="checklist"]
 >
 > * Set up a subscription to send configuration change events from App Configuration to a Service Bus topic
-> * Set up your .NET Core app to update its configuration in response to changes in App Configuration.
+> * Set up your .NET app to update its configuration in response to changes in App Configuration.
 > * Consume the latest configuration in your application.
 
 ## Prerequisites
 
-* Tutorial: [Use dynamic configuration in a .NET Core app](./enable-dynamic-configuration-dotnet-core.md)
+* Tutorial: [Use dynamic configuration in a .NET app](./enable-dynamic-configuration-dotnet-core.md)
 * NuGet package `Microsoft.Extensions.Configuration.AzureAppConfiguration` version 5.0.0 or later
 
 ## Set up Azure Service Bus topic and subscription
@@ -171,7 +171,7 @@ The `ProcessPushNotification` method resets the cache expiration to a short rand
 
 The short random delay for cache expiration is helpful if you have many instances of your application or microservices connecting to the same App Configuration store with the push model. Without this delay, all instances of your application could send requests to your App Configuration store simultaneously as soon as they receive a change notification. This can cause the App Configuration Service to throttle your store. Cache expiration delay is set to a random number between 0 and a maximum of 30 seconds by default, but you can change the maximum value through the optional parameter `maxDelay` to the `ProcessPushNotification` method.
 
-The `ProcessPushNotification` method takes in a `PushNotification` object containing information about which change in App Configuration triggered the push notfication. This helps ensure all configuration changes up to the triggering event are loaded in the following configuration refresh. The `SetDirty` method does not gurarantee the change that triggers the push notification to be loaded in an immediate configuration refresh. If you are using the `SetDirty` method for the push model, we recommend using the `ProcessPushNotification` method instead.
+The `ProcessPushNotification` method takes in a `PushNotification` object containing information about which change in App Configuration triggered the push notification. This helps ensure all configuration changes up to the triggering event are loaded in the following configuration refresh. The `SetDirty` method does not guarantee the change that triggers the push notification to be loaded in an immediate configuration refresh. If you are using the `SetDirty` method for the push model, we recommend using the `ProcessPushNotification` method instead.
 
 ## Build and run the app locally
 
@@ -243,7 +243,7 @@ The `ProcessPushNotification` method takes in a `PushNotification` object contai
 
 ## Next steps
 
-In this tutorial, you enabled your .NET Core app to dynamically refresh configuration settings from App Configuration. To learn how to use an Azure managed identity to streamline the access to App Configuration, continue to the next tutorial.
+In this tutorial, you enabled your .NET app to dynamically refresh configuration settings from App Configuration. To learn how to use an Azure managed identity to streamline the access to App Configuration, continue to the next tutorial.
 
 > [!div class="nextstepaction"]
 > [Managed identity integration](./howto-integrate-azure-managed-service-identity.md)