Merge pull request #34011 from wwlpublish/5b611ad4710f65feacd5bb235cb10928-live

v-ccolin · web-flow · commit 77cea580bad8 · 2023-04-25T08:46:12.000+01:00
Modules/M03-app-configuration
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/1-introduction.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/1-introduction.yml
@@ -4,7 +4,7 @@ title: Introduction
 metadata:
   title: Introduction
   description: "Introduction"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/2-app-configuration-overview.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/2-app-configuration-overview.yml
@@ -4,7 +4,7 @@ title: Explore the Azure App Configuration service
 metadata:
   title: Explore the Azure App Configuration service
   description: "Explore the Azure App Configuration service"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/3-keys-values.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/3-keys-values.yml
@@ -4,7 +4,7 @@ title: Create paired keys and values
 metadata:
   title: Create paired keys and values
   description: "Create paired keys and values"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/4-app-configuration-feature-management.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/4-app-configuration-feature-management.yml
@@ -4,7 +4,7 @@ title: Manage application features
 metadata:
   title: Manage application features
   description: "Manage application features"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/5-secure-app-configuration-data.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/5-secure-app-configuration-data.yml
@@ -4,7 +4,7 @@ title: Secure app configuration data
 metadata:
   title: Secure app configuration data
   description: "Secure app configuration data"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/6-knowledge-check.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/6-knowledge-check.yml
@@ -4,7 +4,7 @@ title: Knowledge check
 metadata:
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
@@ -17,21 +17,21 @@ quiz:
     choices:
     - content: "64-bit AES"
       isCorrect: false
-      explanation: "That's incorrect. Azure App Configuration encrypts sensitive information at rest using a 256-bit AES encryption key provided by Microsoft."
+      explanation: "Incorrect. Azure App Configuration encrypts sensitive information at rest using a 256-bit AES encryption key provided by Microsoft."
     - content: "128-bit AES"
       isCorrect: false
-      explanation: "That's incorrect. Azure App Configuration encrypts sensitive information at rest using a 256-bit AES encryption key provided by Microsoft."
+      explanation: "Incorrect. Azure App Configuration encrypts sensitive information at rest using a 256-bit AES encryption key provided by Microsoft."
     - content: "256-bit AES"
       isCorrect: true
-      explanation: "That's correct. Azure App Configuration encrypts sensitive information at rest using a 256-bit AES encryption key provided by Microsoft."
+      explanation: "Correct. Azure App Configuration encrypts sensitive information at rest using a 256-bit AES encryption key provided by Microsoft."
   - content: "Which of the following options evaluates the state of a feature flag?"
     choices:
     - content: "Feature flag"
       isCorrect: false
-      explanation: "That's incorrect. A feature flag is a variable with a binary state of on or off."
+      explanation: "Incorrect. A feature flag is a variable with a binary state of on or off."
     - content: "Feature manager"
       isCorrect: false
-      explanation: "That's incorrect. A feature manager is an application package that handles the lifecycle of all the feature flags in an application."
+      explanation: "Incorrect. A feature manager is an application package that handles the lifecycle of all the feature flags in an application."
     - content: "Filter"
       isCorrect: true
-      explanation: "That's correct. A filter is a rule for evaluating the state of a feature flag. A user group, a device or browser type, a geographic location, and a time window are all examples of what a filter can represent."
+      explanation: "Correct. A filter is a rule for evaluating the state of a feature flag. A user group, a device or browser type, a geographic location, and a time window are all examples of what a filter can represent."
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/7-summary.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/7-summary.yml
@@ -4,7 +4,7 @@ title: Summary
 metadata:
   title: Summary
   description: "Summary"
-  ms.date: 02/09/2023
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/includes/2-app-configuration-overview.md b/learn-pr/wwl-azure/implement-azure-app-configuration/includes/2-app-configuration-overview.md
@@ -1,5 +1,5 @@
 
-Modern programs, especially programs running in a cloud, generally have many components that are distributed in nature. Spreading configuration settings across these components can lead to hard-to-troubleshoot errors during an application deployment. Use App Configuration to store all the settings for your application and secure their access in one place.
+Azure App Configuration provides a service to centrally manage application settings and feature flags. Modern programs, especially programs running in a cloud, generally have many components that are distributed in nature. Spreading configuration settings across these components can lead to hard-to-troubleshoot errors during an application deployment. Use App Configuration to store all the settings for your application and secure their accesses in one place.
 
 App Configuration offers the following benefits:
 
@@ -10,7 +10,7 @@ App Configuration offers the following benefits:
 * Dedicated UI for feature flag management
 * Comparison of two sets of configurations on custom-defined dimensions
 * Enhanced security through Azure-managed identities
-* Complete data encryptions, at rest or in transit
+* Encryption of sensitive information at rest and in transit
 * Native integration with popular frameworks
 
 App Configuration complements Azure Key Vault, which is used to store application secrets. App Configuration makes it easier to implement the following scenarios:
@@ -25,8 +25,10 @@ The easiest way to add an App Configuration store to your application is through
 
 | Programming language and framework | How to connect |
 |--|--|
-| .NET Core and ASP.NET Core | App Configuration provider for .NET Core |
-| .NET Framework and ASP.NET | App Configuration builder for .NET |
-| Java Spring | App Configuration client for Spring Cloud |
-| Others | App Configuration REST API |  
+| .NET Core and ASP.NET Core | App Configuration [provider](/dotnet/api/Microsoft.Extensions.Configuration.AzureAppConfiguration) for .NET Core |
+| .NET Framework and ASP.NET | App Configuration [builder](https://github.com/aspnet/MicrosoftConfigurationBuilders/blob/main/README.md#azureappconfigurationbuilder) for .NET |
+| Java Spring | App Configuration [client](https://microsoft.github.io/spring-cloud-azure/docs/azure-app-configuration/2.9.0/reference/html/index.html) for Spring Cloud |
+| JavaScript/Node.js | App Configuration [client](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/appconfiguration/app-configuration) for JavaScript |
+| Python | App Configuration [client](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/appconfiguration/azure-appconfiguration) for Python |
+| Others | App Configuration [REST API](/rest/api/appconfiguration/) |  
 
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/includes/3-keys-values.md b/learn-pr/wwl-azure/implement-azure-app-configuration/includes/3-keys-values.md
@@ -11,13 +11,13 @@ You can use any unicode character in key names entered into App Configuration ex
 
 ### 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:
+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 many advantages:
 
 * Easier to read. Instead of one long sequence of characters, delimiters in a hierarchical key name function as spaces in a sentence.
 * Easier to manage. A key name hierarchy represents logical groups of configuration data.
 * Easier to use. It's simpler to write a query that pattern-matches keys in a hierarchical structure and retrieves only a portion of configuration data.
 
-Below are some examples of how you can structure your key names into a hierarchy:
+Following are some examples of how you can structure your key names into a hierarchy:
 
 * Based on component services
 
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/includes/4-app-configuration-feature-management.md b/learn-pr/wwl-azure/implement-azure-app-configuration/includes/4-app-configuration-feature-management.md
@@ -6,7 +6,7 @@ Feature management is a modern software-development practice that decouples feat
 Here are several new terms related to feature management:
 
 * **Feature flag**: A feature flag is a variable with a binary state of *on* or *off*. The feature flag also has an associated code block. The state of the feature flag triggers whether the code block runs or not.
-* **Feature manager**: A feature manager is an application package that handles the lifecycle of all the feature flags in an application. The feature manager typically provides additional functionality, such as caching feature flags and updating their states.
+* **Feature manager**: A feature manager is an application package that handles the lifecycle of all the feature flags in an application. The feature manager typically provides extra functionality, such as caching feature flags and updating their states.
 * **Filter**: A filter is a rule for evaluating the state of a feature flag. A user group, a device or browser type, a geographic location, and a time window are all examples of what a filter can represent.
 
 An effective implementation of feature management consists of at least two components working in concert:
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/includes/5-secure-app-configuration-data.md b/learn-pr/wwl-azure/implement-azure-app-configuration/includes/5-secure-app-configuration-data.md
@@ -1,5 +1,5 @@
 
-In this unit you will learn how to secure your apps configuration data by using:
+In this unit you learn how to secure your apps configuration data by using:
 
 * Customer-managed keys
 * Private endpoints
@@ -32,19 +32,9 @@ Using private endpoints for your App Configuration store enables you to:
 * Increase security for the virtual network (VNet) ensuring data doesn't escape from the VNet.
 * Securely connect to the App Configuration store from on-premises networks that connect to the VNet using VPN or ExpressRoutes with private-peering.
 
-### Private endpoints for App Configuration
-
-When creating a private endpoint, you must specify the App Configuration store to which it connects. If you have multiple App Configuration stores, you need a separate private endpoint for each store. Azure relies upon DNS resolution to route connections from the VNet to the configuration store over a private link. You can quickly find connections strings in the Azure portal by selecting your App Configuration store, then selecting **Settings** > **Access Keys**.
-
-### DNS changes for private endpoints
-
-When you create a private endpoint, the DNS CNAME resource record for the configuration store is updated to an alias in a subdomain with the prefix `privatelink`. Azure also creates a [private DNS zone](/azure/dns/private-dns-overview) corresponding to the `privatelink` subdomain, with the DNS A resource records for the private endpoints.
-
-When you resolve the endpoint URL from within the VNet hosting the private endpoint, it resolves to the private endpoint of the store. When resolved from outside the VNet, the endpoint URL resolves to the public endpoint. When you create a private endpoint, the public endpoint is disabled.
-
 ## Managed identities
 
-A managed identity from Azure Active Directory (Azure AD) allows Azure App Configuration to easily access other AAD-protected resources, such as Azure Key Vault. The identity is managed by the Azure platform. It does not require you to provision or rotate any secrets. 
+A managed identity from Azure Active Directory (Azure AD) allows Azure App Configuration to easily access other AAD-protected resources, such as Azure Key Vault. The identity is managed by the Azure platform. It doesn't require you to provision or rotate any secrets. 
 
 Your application can be granted two types of identities:
 
diff --git a/learn-pr/wwl-azure/implement-azure-app-configuration/index.yml b/learn-pr/wwl-azure/implement-azure-app-configuration/index.yml
@@ -2,8 +2,8 @@
 uid: learn.wwl.implement-azure-app-configuration
 metadata:
   title: Implement Azure App Configuration
-  description: "Implement Azure App Configuration"
-  ms.date: 02/09/2023
+  description: "Learn how to use Azure App Configuration service to centrally manage and secure your configuration settings, and to manage app features."
+  ms.date: 04/25/2023
   author: wwlpublish
   ms.author: jeffko
   ms.topic: interactive-tutorial
@@ -19,7 +19,7 @@ abstract: |
 prerequisites: |
   * You should be experienced with developer concepts and terminology.
   * An understanding of cloud computing and some experience with the Azure portal.
-iconUrl: /learn/achievements/azure-app-implement-configuration.svg
+iconUrl: /training/achievements/azure-app-implement-configuration.svg
 levels:
 - intermediate
 roles:
