Merge pull request #49131 from wwlpublish/3353babb84a7da013205f917b7a3adec7ac38b34763dfd6bf40d11ac40d215ce-live

JamesJBarnett · web-flow · commit 8ff8b25817b3 · 2025-02-12T10:07:37.000-07:00
Modules/M02-configure-web-app-settings
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/1-introduction.yml b/learn-pr/wwl-azure/configure-web-app-settings/1-introduction.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/1-introduction.md)]
+  [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/2-configure-application-settings.yml b/learn-pr/wwl-azure/configure-web-app-settings/2-configure-application-settings.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure application settings
   description: "Configure application settings"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 5
 content: |
-  [!include[](includes/2-configure-application-settings.md)]
+  [!include[](includes/2-configure-application-settings.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/3-configure-general-settings.yml b/learn-pr/wwl-azure/configure-web-app-settings/3-configure-general-settings.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure general settings
   description: "Configure general settings"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 4
 content: |
-  [!include[](includes/3-configure-general-settings.md)]
+  [!include[](includes/3-configure-general-settings.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/4-configure-path-mappings.yml b/learn-pr/wwl-azure/configure-web-app-settings/4-configure-path-mappings.yml
@@ -6,14 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure path mappings
   description: "Configure path mappings"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
-    - N/A
-    - linux-related-content
+  - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/4-configure-path-mappings.md)]
-
+  [!include[](includes/4-configure-path-mappings.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/5-enable-diagnostic-logging.yml b/learn-pr/wwl-azure/configure-web-app-settings/5-enable-diagnostic-logging.yml
@@ -6,14 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Enable diagnostic logging
   description: "Enable diagnostic logging"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
-    - N/A
-    - linux-related-content
+  - N/A
 durationInMinutes: 6
 content: |
-  [!include[](includes/5-enable-diagnostic-logging.md)]
-
+  [!include[](includes/5-enable-diagnostic-logging.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/6-configure-security-certificates.yml b/learn-pr/wwl-azure/configure-web-app-settings/6-configure-security-certificates.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure security certificates
   description: "Configure security certificates"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 4
 content: |
-  [!include[](includes/6-configure-security-certificates.md)]
+  [!include[](includes/6-configure-security-certificates.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/7-knowledge-check.yml b/learn-pr/wwl-azure/configure-web-app-settings/7-knowledge-check.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
@@ -37,4 +37,4 @@ quiz:
       explanation: "Incorrect. Failed request tracing is not supported on the Linux platform."
     - content: "Deployment logging"
       isCorrect: true
-      explanation: "Correct. Deployment logging is supported on the Linux platform."
+      explanation: "Correct. Deployment logging is supported on the Linux platform."
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/8-summary.yml b/learn-pr/wwl-azure/configure-web-app-settings/8-summary.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 2
 content: |
-  [!include[](includes/8-summary.md)]
+  [!include[](includes/8-summary.md)]
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/includes/2-configure-application-settings.md b/learn-pr/wwl-azure/configure-web-app-settings/includes/2-configure-application-settings.md
@@ -1,23 +1,24 @@
-In App Service, app settings are variables passed as environment variables to the application code. For Linux apps and custom containers, App Service passes app settings to the container using the `--env` flag to set the environment variable in the container.
+In App Service, app settings are variables passed as environment variables to the application code. For Linux apps and custom containers, App Service passes app settings to the container using the `--env` flag to set the environment variable in the container. In either case, they're injected into your app environment at app startup. When you add, remove, or edit app settings, App Service triggers an app restart.
 
-Application settings can be accessed by navigating to your app's management page and selecting **Environment variables > Application settings**.
+For ASP.NET and ASP.NET Core developers, setting app settings in App Service is like setting them in `<appSettings>` in *Web.config* or *appsettings.json*, but the values in App Service override the ones in *Web.config* or *appsettings.json*. You can keep development settings (for example, local MySQL password) in *Web.config* or *appsettings.json* and production secrets (for example, Azure MySQL database password) safely in App Service. The same code uses your development settings when you debug locally, and it uses your production secrets when deployed to Azure.
 
-:::image type="content" source="../media/configure-app-settings.png" alt-text="Navigating to Environment variables > Application settings":::
+App settings are always encrypted when stored (encrypted-at-rest). App settings names can only contain letters, numbers (0-9), periods ("."), and underscores ("_")
+Special characters in the value of an App Setting must be escaped as needed by the target OS.
 
-For ASP.NET and ASP.NET Core developers, setting app settings in App Service is like setting them in `<appSettings>` in *Web.config* or *appsettings.json*, but the values in App Service override the ones in *Web.config* or *appsettings.json*. You can keep development settings (for example, local MySQL password) in *Web.config* or *appsettings.json* and production secrets (for example, Azure MySQL database password) safely in App Service. The same code uses your development settings when you debug locally, and it uses your production secrets when deployed to Azure.
+Application settings can be accessed by navigating to your app's management page and selecting **Environment variables > Application settings**.
 
-App settings are always encrypted when stored (encrypted-at-rest).
+:::image type="content" source="../media/configure-app-settings.png" alt-text="Screenshot of Navigating to Environment variables > Application settings.":::
 
 ## Adding and editing settings
 
-To add a new app setting, select **+ Add**. If you're using deployment slots you can specify if your setting is swappable or not. In the dialog, you can stick the setting to the current slot.
+To add a new app setting, select **+ Add**. If you're using deployment slots, you can specify if your setting is swappable or not. In the dialog, you can stick the setting to the current slot.
 
 :::image type="content" source="../media/app-configure-slotsetting.png" alt-text="Selecting deployment slot setting to stick the setting to the current slot.":::
 
 When finished, select **Apply**. Don't forget to select **Apply** back in the **Environment variables** page.
 
 > [!NOTE]
-> In a default Linux app service or a custom Linux container, any nested JSON key structure in the app setting name like `ApplicationInsights:InstrumentationKey` needs to be configured in App Service as `ApplicationInsights__InstrumentationKey` for the key name. In other words, any `:` should be replaced by `__` (double underscore). Any periods in the app setting name will be replaced with a `_` (single underscore).
+> In a default Linux app service or a custom Linux container, any nested JSON key structure in the app setting name like `ApplicationInsights:InstrumentationKey` needs to be configured in App Service as `ApplicationInsights__InstrumentationKey` for the key name. In other words, replace any `:` with `__` (double underscore). Any periods in the app setting name are replaced with a `_` (single underscore).
 
 ### Editing application settings in bulk
 
@@ -44,7 +45,7 @@ To add or edit app settings in bulk, select the **Advanced edit** button. When f
 For ASP.NET and ASP.NET Core developers, setting connection strings in App Service are like setting them in `<connectionStrings>` in *Web.config*, but the values you set in App Service override the ones in *Web.config*. For other language stacks, it's better to use app settings instead, because connection strings require special formatting in the variable keys in order to access the values.
 
 > [!TIP]
-> There is one case where you may want to use connection strings instead of app settings for non-.NET languages: certain Azure database types are backed up along with the app *only* if you configure a connection string for the database in your App Service app.
+> There's one case where you may want to use connection strings instead of app settings for non-.NET languages: certain Azure database types are backed up along with the app *only* if you configure a connection string for the database in your App Service app.
 
 Adding and editing connection strings follow the same principles as other app settings and they can also be tied to deployment slots. An example of connection strings in JSON formatting that you would use for bulk adding or editing:
 
@@ -67,7 +68,22 @@ Adding and editing connection strings follow the same principles as other app se
 ```
 
 > [!NOTE]
-> .NET apps targeting PostgreSQL should set the connection string to **Custom** as workaround for a known issue in .NET EnvironmentVariablesConfigurationProvider.
+> .NET apps targeting PostgreSQL should set the connection string to **Custom** as work around for a known issue in .NET `EnvironmentVariablesConfigurationProvider`.
+
+At runtime, connection strings are available as environment variables, prefixed with the following connection types:
+
+* SQLServer: `SQLCONNSTR_`
+* MySQL: `MYSQLCONNSTR_`
+* SQLAzure: `SQLAZURECONNSTR_`
+* Custom: `CUSTOMCONNSTR_`
+* PostgreSQL: `POSTGRESQLCONNSTR_`
+* Notification Hub: `NOTIFICATIONHUBCONNSTR_`
+* Service Bus: `SERVICEBUSCONNSTR_`
+* Event Hub: `EVENTHUBCONNSTR_`
+* Document DB: `DOCDBCONNSTR_`
+* Redis Cache: `REDISCACHECONNSTR_`
+
+For example, a MySQL connection string named *connectionstring1* can be accessed as the environment variable `MYSQLCONNSTR_connectionString1`.
 
 ## Configure environment variables for custom containers
 
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/includes/3-configure-general-settings.md b/learn-pr/wwl-azure/configure-web-app-settings/includes/3-configure-general-settings.md
@@ -17,7 +17,7 @@ A list of the currently available settings:
     * **HTTP version**: Set to **2.0** to enable support for HTTPS/2 protocol.
 
         > [!NOTE]
-        > Most modern browsers support HTTP/2 protocol over TLS only, while non-encrypted traffic continues to use HTTP/1.1. To ensure that client browsers connect to your app with HTTP/2, secure your custom DNS name.
+        > Most modern browsers support HTTP/2 protocol over TLS only, while nonencrypted traffic continues to use HTTP/1.1. To ensure that client browsers connect to your app with HTTP/2, secure your custom DNS name.
 
     * **Web sockets**: For ASP.NET SignalR or socket.io, for example.
 
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/includes/4-configure-path-mappings.md b/learn-pr/wwl-azure/configure-web-app-settings/includes/4-configure-path-mappings.md
@@ -27,3 +27,4 @@ You can add custom storage for your containerized app. Containerized apps includ
 * **Access key**: For advanced configuration, the access key.
 * **Mount path**: The absolute path in your container to mount the custom storage.
 * **Deployment slot setting**: When checked, the storage mount settings also apply to deployment slots.
+
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/includes/5-enable-diagnostic-logging.md b/learn-pr/wwl-azure/configure-web-app-settings/includes/5-enable-diagnostic-logging.md
@@ -6,7 +6,7 @@ The following table shows the types of logging, the platforms supported, and whe
 |--|--|--|--|
 | Application logging | Windows, Linux | App Service file system and/or Azure Storage blobs | Logs messages generated by your application code. The messages are generated by the web framework you choose, or from your application code directly using the standard logging pattern of your language. Each message is assigned one of the following categories: **Critical**, **Error**, **Warning**, **Info**, **Debug**, and **Trace**. |
 | Web server logging | Windows | App Service file system or Azure Storage blobs | Raw HTTP request data in the W3C extended log file format. Each log message includes data like the HTTP method, resource URI, client IP, client port, user agent, response code, and so on. |
-| Detailed error messages | Windows | App Service file system | Copies of the *.html* error pages that would have been sent to the client browser. For security reasons, detailed error pages shouldn't be sent to clients in production, but App Service can save the error page each time an application error occurs that has HTTP code 400 or greater. |
+| Detailed error messages | Windows | App Service file system | Copies of the *.html* error pages that would otherwise be sent to the client browser. For security reasons, detailed error pages shouldn't be sent to clients in production, but App Service can save the error page each time an application error occurs that has HTTP code 400 or greater. |
 | Failed request tracing | Windows | App Service file system | Detailed tracing information on failed requests, including a trace of the IIS components used to process the request and the time taken in each component. One folder is generated for each failed request, which contains the XML log file, and the XSL stylesheet to view the log file with. |
 | Deployment logging | Windows, Linux | App Service file system | Helps determine why a deployment failed. Deployment logging happens automatically and there are no configurable settings for deployment logging. |
 
@@ -88,3 +88,4 @@ For logs stored in the App Service file system, the easiest way is to download t
 * Windows apps: `https://<app-name>.scm.azurewebsites.net/api/dump`
 
 For Linux/container apps, the ZIP file contains console output logs for both the docker host and the docker container. For a scaled-out app, the ZIP file contains one set of logs for each instance. In the App Service file system, these log files are the contents of the */home/LogFiles* directory.
+
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/includes/6-configure-security-certificates.md b/learn-pr/wwl-azure/configure-web-app-settings/includes/6-configure-security-certificates.md
@@ -1,13 +1,13 @@
-You've been asked to help secure information being transmitted between your company’s app and the customer. Azure App Service has tools that let you  create, upload, or import a private certificate or a public certificate into App Service.
+Azure App Service has tools that let you  create, upload, or import a private certificate or a public certificate into App Service.
 
-A certificate uploaded into an app is stored in a deployment unit that is bound to the app service plan's resource group and region combination (internally called a *webspace*). This makes the certificate accessible to other apps in the same resource group and region combination.
+A certificate uploaded into an app is stored in a deployment unit that is bound to the app service plan's resource group and region combination (internally called a *webspace*). The certificate is accessible to other apps in the same resource group and region combination.
 
 The table below details the options you have for adding certificates in App Service:
 
 | Option | Description |
 |--|--|
 | Create a free App Service managed certificate | A private certificate that's free of charge and easy to use if you just need to secure your custom domain in App Service. |
-| Purchase an App Service certificate | A private certificate that's managed by Azure. It combines the simplicity of automated certificate management and the flexibility of renewal and export options. |
+| Purchase an App Service certificate | A private certificate managed by Azure. It combines the simplicity of automated certificate management and the flexibility of renewal and export options. |
 | Import a certificate from Key Vault | Useful if you use Azure Key Vault to manage your certificates. |
 | Upload a private certificate | If you already have a private certificate from a third-party provider, you can upload it. |
 | Upload a public certificate | Public certificates aren't used to secure custom domains, but you can load them into your code if you need them to access remote resources. |
@@ -17,7 +17,7 @@ The table below details the options you have for adding certificates in App Serv
 The free **App Service managed certificate** and the **App Service certificate** already satisfy the requirements of App Service. If you want to use a private certificate in App Service, your certificate must meet the following requirements:
 
 * Exported as a password-protected PFX file, encrypted using triple DES.
-* Contains private key at least 2048 bits long.
+* Contains private key at least 2,048 bits long.
 * Contains all intermediate certificates and the root certificate in the certificate chain.
 
 To secure a custom domain in a TLS binding, the certificate has other requirements:
@@ -29,10 +29,10 @@ To secure a custom domain in a TLS binding, the certificate has other requiremen
 
 To create custom TLS/SSL bindings or enable client certificates for your App Service app, your App Service plan must be in the **Basic**, **Standard**, **Premium**, or **Isolated** tier.
 
-The free App Service managed certificate is a turn-key solution for securing your custom DNS name in App Service. It's a TLS/SSL server certificate that's fully managed by App Service and renewed continuously and automatically in six-month increments, 45 days before expiration. You create the certificate and bind it to a custom domain, and let App Service do the rest.
+The free App Service managed certificate is a turn-key solution for securing your custom DNS name in App Service. It's a TLS/SSL server certificate fully managed by App Service and renewed continuously and automatically in six-month increments, 45 days before expiration. You create the certificate and bind it to a custom domain, and let App Service do the rest.
 
 > [!IMPORTANT]
-> Before you create a free managed certificate, make sure you have met the prerequisites for your app. Free certificates are issued by DigiCert. For some domains, you must explicitly allow DigiCert as a certificate issuer by creating a CAA domain record with the value: `0 issue digicert.com`. Azure fully manages the certificates on your behalf, so any aspect of the managed certificate, including the root issuer, can change at anytime. These changes are outside your control. Make sure to avoid hard dependencies and "pinning" practice certificates to the managed certificate or any part of the certificate hierarchy.
+> Before you create a free managed certificate, make sure you meet the prerequisites for your app. Free certificates are issued by DigiCert. For some domains, you must explicitly allow DigiCert as a certificate issuer by creating a CAA domain record with the value: `0 issue digicert.com`. Azure fully manages the certificates on your behalf, so any aspect of the managed certificate, including the root issuer, can change at any time. These changes are outside your control. Make sure to avoid hard dependencies and "pinning" practice certificates to the managed certificate or any part of the certificate hierarchy.
 
 The free certificate comes with the following limitations:
 
@@ -60,4 +60,4 @@ If you already have a working App Service certificate, you can:
 * Manage the certificate, such as renew, rekey, and export it.
 
 > [!NOTE]
-> App Service Certificates are not supported in Azure National Clouds at this time.
+> App Service Certificates aren't supported in Azure National Clouds at this time.
diff --git a/learn-pr/wwl-azure/configure-web-app-settings/index.yml b/learn-pr/wwl-azure/configure-web-app-settings/index.yml
@@ -5,15 +5,15 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure web app settings
   description: "Configure web app settings"
-  ms.date: 06/11/2024
+  ms.date: 02/12/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: module
   ms.custom:
   - N/A
   ms.service: azure-app-service
   ms.subservice: web-apps
-  ai-usage: human-only
+  ai-usage: ai-assisted
 title: Configure web app settings
 summary: Learn how to create and manage application settings, install SSL/TLS certificates to secure web traffic, enable diagnostic logging, create virtual app to directory mappings, and manage app features.
 abstract: |
@@ -50,4 +50,4 @@ units:
 - learn.wwl.configure-web-app-settings.knowledge-check
 - learn.wwl.configure-web-app-settings.summary
 badge:
-  uid: learn.wwl.configure-web-app-settings.badge
+  uid: learn.wwl.configure-web-app-settings.badge
