Merge pull request #102896 from jpconnock/app-config-cd-ci

App config cd ci freshness

Author: GitHubber17

articles/azure-app-configuration/integrate-ci-cd-pipeline.md

@@ -1,35 +1,29 @@
 ---
-title: "Tutorial: Integrate with a continuous integration and delivery pipeline"
-titleSuffix: Azure App Configuration
-description: In this tutorial, you learn how to generate a configuration file by using data in Azure App Configuration during continuous integration and delivery
+title: Integrate Azure App Configuration using a continuous integration and delivery pipeline
+description: Learn to implement continuous integration and delivery using Azure App Configuration
 services: azure-app-configuration
-documentationcenter: ''
 author: lisaguthrie
-manager: balans
-editor: ''
-
-ms.assetid: 
 ms.service: azure-app-configuration
 ms.topic: tutorial
-ms.date: 02/24/2019
+ms.date: 01/30/2020
 ms.author: lcozzens
-ms.custom: mvc
 
-#Customer intent: I want to use Azure App Configuration data in my CI/CD pipeline.
+# Customer intent: I want to use Azure App Configuration data in my CI/CD pipeline.
+
 ---
 # Integrate with a CI/CD pipeline
 
-This article describes various ways of using data from Azure App Configuration in a continuous integration and continuous deployment system.
+This article explains how to use data from Azure App Configuration in a continuous integration and continuous deployment system.
 
 ## Use App Configuration in your Azure DevOps Pipeline
 
-If you have an Azure DevOps Pipeline, you can fetch key-values from App Configuration and set them as task variables. The [Azure App Configuration DevOps extension](https://go.microsoft.com/fwlink/?linkid=2091063) is an add-on module that provides this functionality. Simply follow its instructions to use the extension in a build or release task sequence.
+If you have an Azure DevOps Pipeline, you can fetch key-values from App Configuration and set them as task variables. The [Azure App Configuration DevOps extension](https://go.microsoft.com/fwlink/?linkid=2091063) is an add-on module that provides this functionality. Follow its instructions to use the extension in a build or release task sequence.
 
 ## Deploy App Configuration data with your application
 
-Your application may fail to run if it depends on Azure App Configuration and cannot reach it. You can enhance the resiliency of your application to deal with such an event, however unlikely it is to happen. To do so, package the current configuration data into a file that's deployed with the application and loaded locally during its startup. This approach guarantees that your application has default setting values at least. These values are overwritten by any newer changes in an App Configuration store when it's available.
+Your application may fail to run if it depends on Azure App Configuration and cannot reach it. Enhance the resiliency of your application by packaging  configuration data into a file that's deployed with the application and loaded locally during application startup. This approach guarantees that your application has default setting values on startup. These values are overwritten by any newer changes in an App Configuration store when it's available.
 
-Using the [Export](./howto-import-export-data.md#export-data) function of Azure App Configuration, you can automate the process of retrieving current configuration data as a single file. Then embed this file in a build or deployment step in your continuous integration and continuous deployment (CI/CD) pipeline.
+Using the [Export](./howto-import-export-data.md#export-data) function of Azure App Configuration, you can automate the process of retrieving current configuration data as a single file. You can then embed this file in a build or deployment step in your continuous integration and continuous deployment (CI/CD) pipeline.
 
 The following example shows how to include App Configuration data as a build step for the web app introduced in the quickstarts. Before you continue, finish [Create an ASP.NET Core app with App Configuration](./quickstart-aspnet-core-app.md) first.
 
@@ -51,10 +45,7 @@ To do a cloud build, with Azure DevOps for example, make sure the [Azure CLI](ht
         <Exec WorkingDirectory="$(MSBuildProjectDirectory)" Condition="$(ConnectionString) != ''" Command="az appconfig kv export -d file --path $(OutDir)\azureappconfig.json --format json --separator : --connection-string $(ConnectionString)" />
     </Target>
     ```
-
-    Add the *ConnectionString* associated with your App Configuration store as an environment variable.
-
-2. Open *Program.cs*, and update the `CreateWebHostBuilder` method to use the exported JSON file by calling the `config.AddJsonFile()` method.
+1. Open *Program.cs*, and update the `CreateWebHostBuilder` method to use the exported JSON file by calling the `config.AddJsonFile()` method.  Add the `System.Reflection` namespace as well.
 
     ```csharp
     public static IWebHostBuilder CreateWebHostBuilder(string[] args) =>
@@ -72,7 +63,8 @@ To do a cloud build, with Azure DevOps for example, make sure the [Azure CLI](ht
 
 ### Build and run the app locally
 
-1. Set an environment variable named **ConnectionString**, and set it to the access key to your App Configuration store. If you use the Windows command prompt, run the following command and restart the command prompt to allow the change to take effect:
+1. Set an environment variable named **ConnectionString**, and set it to the access key to your App Configuration store. 
+    If you use the Windows command prompt, run the following command and restart the command prompt to allow the change to take effect:
 
         setx ConnectionString "connection-string-of-your-app-configuration-store"