Merge pull request #231674 from cephalin/ssl

update SSL binding docs

Author: v-regandowner

articles/app-service/app-service-web-tutorial-custom-domain.md

@@ -157,7 +157,7 @@ Browse to the DNS names that you configured earlier.
 If you receive an HTTP 404 (Not Found) error when you browse to the URL of your custom domain, the two most-likely causes are:
 
 - The browser client has cached the old IP address of your domain. Clear the cache, and test DNS resolution again. On a Windows machine, you clear the cache with `ipconfig /flushdns`.
-- You configured an IP-based certificate binding, and the app's IP address has changed because of it. [Remap the A record](configure-ssl-bindings.md#remap-records-for-ip-ssl) in your DNS entries to the new IP address.
+- You configured an IP-based certificate binding, and the app's IP address has changed because of it. [Remap the A record](configure-ssl-bindings.md#2-remap-records-for-ip-based-ssl) in your DNS entries to the new IP address.
 
 If you receive a `Page not secure` warning or error, it's because your domain doesn't have a certificate binding yet. [Add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
 

articles/app-service/configure-common.md

@@ -4,7 +4,7 @@ description: Learn to configure common settings for an App Service app. App sett
 keywords: azure app service, web app, app settings, environment variables
 ms.assetid: 9af8a367-7d39-4399-9941-b80cbc5f39a0
 ms.topic: article
-ms.date: 07/11/2022
+ms.date: 04/21/2023
 ms.custom: devx-track-csharp, seodec18, devx-track-azurecli, devx-track-azurepowershell
 ms.devlang: azurecli
 ---
@@ -43,9 +43,9 @@ App settings are always encrypted when stored (encrypted-at-rest).
 
     ![Application Settings](./media/configure-common/open-ui.png)
 
-    By default, values for app settings are hidden in the portal for security. To see a hidden value of an app setting, click its **Value** field. To see the hidden values of all app settings, click the **Show values** button.
+    By default, values for app settings are hidden in the portal for security. To see a hidden value of an app setting, select its **Value** field. To see the hidden values of all app settings, select the **Show values** button.
 
-1. To add a new app setting, click **New application setting**. To edit a setting, click the **Edit** button on the right side.
+1. To add a new app setting, select **New application setting**. To edit a setting, select the **Edit** button on the right side.
 
 1. In the dialog, you can [stick the setting to the current slot](deploy-staging-slots.md#which-settings-are-swapped).
 
@@ -55,7 +55,7 @@ App settings are always encrypted when stored (encrypted-at-rest).
     > 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).
     >
 
-1. When finished, click **Update**. Don't forget to click **Save** back in the **Configuration** page.
+1. When finished, select **Update**. Don't forget to select **Save** back in the **Configuration** page.
 
 # [Azure CLI](#tab/cli)
 
@@ -125,7 +125,7 @@ Set-AzWebAppSlotConfigName -ResourceGroupName <group-name> -Name <app-name> -App
 
 # [Azure portal](#tab/portal)
 
-Click the **Advanced edit** button. Edit the settings in the text area. When finished, click **Update**. Don't forget to click **Save** back in the **Configuration** page.
+Select the **Advanced edit** button. Edit the settings in the text area. When finished, select **Update**. Don't forget to select **Save** back in the **Configuration** page.
 
 App settings have the following JSON formatting:
 
@@ -193,7 +193,7 @@ It's not possible to edit app settings in bulk by using a JSON file with Azure P
 
 ### Configure arrays in app settings
 
-You can also configure arrays in app settings as shown in the table below.
+You can also configure arrays in app settings as shown in the following table.
 
 |App setting name | App setting value |
 |-----------------|-------------------|
@@ -245,13 +245,13 @@ Connection strings are always encrypted when stored (encrypted-at-rest).
 
     ![Application Settings](./media/configure-common/open-ui.png)
 
-    By default, values for connection strings are hidden in the portal for security. To see a hidden value of a connection string, click its **Value** field. To see the hidden values of all connection strings, click the **Show value** button.
+    By default, values for connection strings are hidden in the portal for security. To see a hidden value of a connection string, select its **Value** field. To see the hidden values of all connection strings, select the **Show value** button.
 
-1. To add a new connection string, click **New connection string**. To edit a connection string, click the **Edit** button on the right side.
+1. To add a new connection string, select **New connection string**. To edit a connection string, select the **Edit** button on the right side.
 
 1. In the dialog, you can [stick the connection string to the current slot](deploy-staging-slots.md#which-settings-are-swapped).
 
-1. When finished, click **Update**. Don't forget to click **Save** back in the **Configuration** page.
+1. When finished, select **Update**. Don't forget to select **Save** back in the **Configuration** page.
 
 # [Azure CLI](#tab/cli)
 
@@ -332,7 +332,7 @@ Set-AzWebAppSlotConfigName -ResourceGroupName <group-name> -Name <app-name> -Con
 
 # [Azure portal](#tab/portal)
 
-Click the **Advanced edit** button. Edit the connection strings in the text area. When finished, click **Update**. Don't forget to click **Save** back in the **Configuration** page.
+Select the **Advanced edit** button. Edit the connection strings in the text area. When finished, select **Update**. Don't forget to select **Save** back in the **Configuration** page.
 
 Connection strings have the following JSON formatting:
 
@@ -433,16 +433,18 @@ Here, you can configure some common settings for the app. Some settings require
     ![General settings for Linux containers](./media/configure-common/open-general-linux.png)
 
 - **Platform settings**: Lets you configure settings for the hosting platform, including:
+    - **Platform bitness**: 32-bit or 64-bit. For Windows apps only. 
     - **FTP state**: Allow only FTPS or disable FTP altogether.
-    - **Bitness**: 32-bit or 64-bit. For Windows apps only. 
-    - **WebSocket protocol**: For [ASP.NET SignalR] or [socket.io](https://socket.io/), for example.
-    - **Always On**: Keeps the app loaded even when there's no traffic. When **Always On** is not turned on (default), the app is unloaded after 20 minutes without any incoming requests. The unloaded app can cause high latency for new requests because of its warm-up time. When **Always On** is turned on, the front-end load balancer sends a GET request to the application root every five minutes. The continuous ping prevents the app from being unloaded.
-    
-        Always On is required for continuous WebJobs or for WebJobs that are triggered using a CRON expression.
     - **HTTP version**: Set to **2.0** to enable support for [HTTPS/2](https://wikipedia.org/wiki/HTTP/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. For more information, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
+    - **Web sockets**: For [ASP.NET SignalR] or [socket.io](https://socket.io/), for example.
+    - **Always On**: Keeps the app loaded even when there's no traffic. When **Always On** isn't turned on (default), the app is unloaded after 20 minutes without any incoming requests. The unloaded app can cause high latency for new requests because of its warm-up time. When **Always On** is turned on, the front-end load balancer sends a GET request to the application root every five minutes. The continuous ping prevents the app from being unloaded.
+    
+        Always On is required for continuous WebJobs or for WebJobs that are triggered using a CRON expression.
     - **ARR affinity**: In a multi-instance deployment, ensure that the client is routed to the same instance for the life of the session. You can set this option to **Off** for stateless applications.
+    - **HTTPS Only**: When enabled, all HTTP traffic is redirected to HTTPS.
+    - **Minimum TLS version**: Select the minimum TLS encryption version required by your app.
 - **Debugging**: Enable remote debugging for [ASP.NET](troubleshoot-dotnet-visual-studio.md#remotedebug), [ASP.NET Core](/visualstudio/debugger/remote-debugging-azure), or [Node.js](configure-language-nodejs.md#debug-remotely) apps. This option turns off automatically after 48 hours.
 - **Incoming client certificates**: require client certificates in [mutual authentication](app-service-web-configure-tls-mutual-auth.md).
 
@@ -471,7 +473,7 @@ To show the existing settings, use the [Get-AzWebApp](/powershell/module/az.webs
 
 This setting is only for Windows apps.
 
-The default document is the web page that's displayed at the root URL of an App Service app. The first matching file in the list is used. If the app uses modules that route based on URL instead of serving static content, there is no need for default documents.
+The default document is the web page that's displayed at the root URL of an App Service app. The first matching file in the list is used. If the app uses modules that route based on URL instead of serving static content, there's no need for default documents.
 
 # [Azure portal](#tab/portal)
 
@@ -480,7 +482,7 @@ The default document is the web page that's displayed at the root URL of an App
 
     ![Default documents](./media/configure-common/open-documents.png)
 
-1. To add a default document, click **New document**. To remove a default document, click **Delete** to its right.
+1. To add a default document, select **New document**. To remove a default document, select **Delete** to its right.
 
 # [Azure CLI](#tab/cli)
 
@@ -512,14 +514,14 @@ By default, App Service starts your app from the root directory of your app code
 
 1. In the [Azure portal], search for and select **App Services**, and then select your app. 
 1. In the app's left menu, select **Configuration** > **Path mappings**
-1. Click **New virtual application or directory**. 
+1. Select **New virtual application or directory**. 
 
     - To map a virtual directory to a physical path, leave the **Directory** check box selected. Specify the virtual directory and the corresponding relative (physical) path to the website root (`D:\home`).
     - To mark a virtual directory as a web application, clear the **Directory** check box.
 
     ![Directory check box](./media/configure-common/directory-check-box.png)
 
-1. Click **OK**.
+1. Select **OK**.
 
 # [Azure CLI](#tab/cli)
 
@@ -582,13 +584,13 @@ To add a custom handler:
 
     ![Path mappings](./media/configure-common/open-path.png)
 
-1. Click **New handler mapping**. Configure the handler as follows:
+1. Select **New handler mapping**. Configure the handler as follows:
 
     - **Extension**. The file extension you want to handle, such as *\*.php* or *handler.fcgi*.
     - **Script processor**. The absolute path of the script processor to you. Requests to files that match the file extension are processed by the script processor. Use the path `D:\home\site\wwwroot` to refer to your app's root directory.
     - **Arguments**. Optional command-line arguments for the script processor.
 
-1. Click **OK**.
+1. Select **OK**.
 
 ## Configure custom containers