Merge pull request #270897 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 4/2

Author: ttorble

articles/azure-app-configuration/TOC.yml

@@ -35,6 +35,8 @@
           href: quickstart-feature-flag-aspnet-core.md
         - name: .NET/.NET Framework
           href: quickstart-feature-flag-dotnet.md
+        - name: .NET Background Service
+          href: quickstart-feature-flag-dotnet-background-service.md
         - name: Java Spring
           href: quickstart-feature-flag-spring-boot.md
         - name: Azure Functions

articles/azure-app-configuration/enable-dynamic-configuration-dotnet-background-service.md

@@ -43,15 +43,15 @@ You use the [.NET command-line interface (CLI)](/dotnet/core/tools/) to create a
 
 1. Create a new folder for your project.
 
-2. In the new folder, run the following command to create a new .NET background service project:
+1. In the new folder, run the following command to create a new .NET background service project:
 
     ```dotnetcli
     dotnet new worker
     ```
 
 ## Reload data from App Configuration
 
-1. Add references to the `Microsoft.Extensions.Configuration.AzureAppConfiguration` NuGet package by running the following commands:
+1. Add references to the `Microsoft.Extensions.Configuration.AzureAppConfiguration` NuGet package by running the following command:
 
     ```dotnetcli
     dotnet add package Microsoft.Extensions.Configuration.AzureAppConfiguration
@@ -175,7 +175,7 @@ You use the [.NET command-line interface (CLI)](/dotnet/core/tools/) to create a
 
     ---
 
-1. Run the following command to build the console app.
+1. Run the following command to build the app.
 
     ```dotnetcli
     dotnet build
@@ -197,7 +197,7 @@ You use the [.NET command-line interface (CLI)](/dotnet/core/tools/) to create a
     |----------------------------|-----------------------------------------------|
     | *TestApp:Settings:Message* | *Data from Azure App Configuration - Updated* |
 
-1. Wait for about 30 seconds. You should see the console outputs changed.
+1. Wait a few moments for the refresh interval time window to pass. You will see the console outputs changed.
 
     ![Screenshot of the refreshed background service.](./media/dotnet-background-service-refresh.png)
 

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

@@ -233,7 +233,7 @@ The `ProcessPushNotification` method takes in a `PushNotification` object contai
     |---|---|
     | TestApp:Settings:Message | Data from Azure App Configuration - Updated |
 
-1. Wait for 30 seconds to allow the event to be processed and configuration to be updated.
+1. Wait for a few moments to allow the event to be processed. You will see the updated configuration.
 
     ![Push refresh run after updated](./media/dotnet-core-app-pushrefresh-final.png)
 

articles/azure-app-configuration/media/dotnet-background-service-refresh.png

@@ -35,7 +35,7 @@ You can use the [.NET command-line interface (CLI)](/dotnet/core/tools/) to crea
 
 1. Create a new folder for your project.
 
-2. In the new folder, run the following command to create a new .NET console app project:
+1. In the new folder, run the following command to create a new .NET console app project:
 
     ```dotnetcli
     dotnet new console
@@ -49,20 +49,20 @@ You can use the [.NET command-line interface (CLI)](/dotnet/core/tools/) to crea
     dotnet add package Microsoft.Extensions.Configuration.AzureAppConfiguration
     ```
 
-2. Run the following command to restore packages for your project:
+1. Run the following command to restore packages for your project:
 
     ```dotnetcli
     dotnet restore
     ```
 
-3. Open *Program.cs*, and add a reference to the .NET App Configuration provider.
+1. Open *Program.cs*, and add the following statements:
 
     ```csharp
     using Microsoft.Extensions.Configuration;
     using Microsoft.Extensions.Configuration.AzureAppConfiguration;
     ```
 
-4. Use App Configuration by calling the `AddAzureAppConfiguration` method in the `Program.cs` file.
+1. Use App Configuration by calling the `AddAzureAppConfiguration` method in the `Program.cs` file.
 
     ```csharp
     var builder = new ConfigurationBuilder();

articles/azure-app-configuration/media/dotnet-background-service-run.png

@@ -20,6 +20,7 @@ The feature management support extends the dynamic configuration feature in App
 ## Prerequisites
 
 Follow the documents to create an ASP.NET Core app with dynamic configuration.
+
 - [Quickstart: Create an ASP.NET Core app with App Configuration](./quickstart-aspnet-core-app.md)
 - [Tutorial: Use dynamic configuration in an ASP.NET Core app](./enable-dynamic-configuration-aspnet-core.md)
 
@@ -57,7 +58,7 @@ Add a feature flag called *Beta* to the App Configuration store and leave **Labe
     ```
 
     > [!TIP]
-    > When no parameter is passed to the `UseFeatureFlags` method, it loads *all* feature flags with *no label* in your App Configuration store. The default refresh expiration of feature flags is 30 seconds. You can customize this behavior via the `FeatureFlagOptions` parameter. For example, the following code snippet loads only feature flags that start with *TestApp:* in their *key name* and have the label *dev*. The code also changes the refresh expiration time to 5 minutes. Note that this refresh expiration time is separate from that for regular key-values.
+    > When no parameter is passed to the `UseFeatureFlags` method, it loads *all* feature flags with *no label* in your App Configuration store. The default refresh interval of feature flags is 30 seconds. You can customize this behavior via the `FeatureFlagOptions` parameter. For example, the following code snippet loads only feature flags that start with *TestApp:* in their *key name* and have the label *dev*. The code also changes the refresh interval time to 5 minutes. Note that this refresh interval time is separate from that for regular key-values.
     >
     > ```csharp
     > options.UseFeatureFlags(featureFlagOptions =>
@@ -165,7 +166,7 @@ Add a feature flag called *Beta* to the App Configuration store and leave **Labe
 
 1. Select **Feature manager** and locate the **Beta** feature flag. Enable the flag by selecting the checkbox under **Enabled**.
 
-1. Refresh the browser a few times. When the cache expires after 30 seconds, the page shows with updated content.
+1. Refresh the browser a few times. When the refresh interval time window passes, the page will show with updated content.
 
     ![Feature flag after enabled](./media/quickstarts/aspnet-core-feature-flag-local-after.png)
 

articles/azure-app-configuration/media/quickstarts/dotnet-background-service-feature-flag-disabled.png

@@ -68,7 +68,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
    - [Microsoft.FeatureManagement](https://www.nuget.org/packages/Microsoft.FeatureManagement/) version 2.2.0 or later
    - [Microsoft.Azure.Functions.Extensions](https://www.nuget.org/packages/Microsoft.Azure.Functions.Extensions/) version 1.1.0 or later 
 
-2. Add a new file, *Startup.cs*, with the following code. It defines a class named `Startup` that implements the `FunctionsStartup` abstract class. An assembly attribute is used to specify the type name used during Azure Functions startup.
+1. Add a new file, *Startup.cs*, with the following code. It defines a class named `Startup` that implements the `FunctionsStartup` abstract class. An assembly attribute is used to specify the type name used during Azure Functions startup.
 
     ```csharp
     using System;
@@ -94,7 +94,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
     ```
 
 
-3. Update the `ConfigureAppConfiguration` method, and add Azure App Configuration provider as an extra configuration source by calling `AddAzureAppConfiguration()`. 
+1. Update the `ConfigureAppConfiguration` method, and add Azure App Configuration provider as an extra configuration source by calling `AddAzureAppConfiguration()`. 
 
     The `UseFeatureFlags()` method tells the provider to load feature flags. All feature flags have a default cache expiration of 30 seconds before rechecking for changes. The expiration interval can be updated by setting the `FeatureFlagsOptions.CacheExpirationInterval` property passed to the `UseFeatureFlags` method. 
 
@@ -113,7 +113,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
     > [!TIP]
     > If you don't want any configuration other than feature flags to be loaded to your application, you can call `Select("_")` to only load a nonexisting dummy key `"_"`. By default, all configuration key-values in your App Configuration store will be loaded if no `Select` method is called.
 
-4. Update the `Configure` method to make Azure App Configuration services and feature manager available through dependency injection.
+1. Update the `Configure` method to make Azure App Configuration services and feature manager available through dependency injection.
 
     ```csharp
     public override void Configure(IFunctionsHostBuilder builder)
@@ -123,7 +123,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
     }
     ```
 
-5. Open *Function1.cs*, and add the following namespaces.
+1. Open *Function1.cs*, and add the following namespaces.
 
     ```csharp
     using System.Linq;
@@ -144,7 +144,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
     }
     ```
 
-6. Update the `Run` method to change the value of the displayed message depending on the state of the feature flag.
+1. Update the `Run` method to change the value of the displayed message depending on the state of the feature flag.
 
    The `TryRefreshAsync` method is called at the beginning of the Functions call to refresh feature flags. It will be a no-op if the cache expiration time window isn't reached. Remove the `await` operator if you prefer the feature flags to be refreshed without blocking the current Functions call. In that case, later Functions calls will get updated value.
 
@@ -200,7 +200,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
 
 1. Select **Feature manager**, and change the state of the **Beta** key to **On**.
 
-1. Refresh the browser a few times. When the cached feature flag expires after 30 seconds, the page should have changed to indicate the feature flag `Beta` is turned on, as shown in the image below.
+1. Refresh the browser a few times. When the refresh interval time window passes, the page will change to indicate the feature flag `Beta` is turned on, as shown in the image below.
 
     ![Quickstart Function feature flag enabled](./media/quickstarts/functions-launch-ff-enabled.png)