Merge pull request #110186 from TimShererWithAquent/us1679050df

v-albemi · web-flow · commit 89dabc3afd53 · 2020-04-16T08:35:46.000-07:00
Change SSL to TLS per 1679050 (2 of 2)
diff --git a/articles/app-service/deploy-ftp.md b/articles/app-service/deploy-ftp.md
@@ -67,7 +67,7 @@ It's recommended that you use **App Credentials** to deploy to your app because
 
 ## Enforce FTPS
 
-For enhanced security, you should allow FTP over SSL only. You can also disable both FTP and FTPS if you don't use FTP deployment.
+For enhanced security, you should allow FTP over TLS/SSL only. You can also disable both FTP and FTPS if you don't use FTP deployment.
 
 In your app's resource page in [Azure portal](https://portal.azure.com), select **Configuration** > **General settings** from the left navigation.
 
diff --git a/articles/app-service/ip-address-change-ssl.md b/articles/app-service/ip-address-change-ssl.md
@@ -21,7 +21,7 @@ If you received a notification that the SSL IP address of your Azure App Service
 
 4.	Under the **Settings** header, click **SSL settings** in the left navigation.
 
-1. In the SSL bindings section, select the host name record. In the editor that opens, choose **SNI SSL** on the **SSL Type** drop-down menu and click **Add Binding**. When you see the operation success message, the existing IP address has been released.
+1. In the TLS/SSL bindings section, select the host name record. In the editor that opens, choose **SNI SSL** on the **SSL Type** drop-down menu and click **Add Binding**. When you see the operation success message, the existing IP address has been released.
 
 6.	In the **SSL bindings** section, again select the same host name record with the certificate. In the editor that opens, this time choose **IP Based SSL** on the **SSL Type** drop-down menu and click **Add Binding**. When you see the operation success message, you’ve acquired a new IP address.
 
@@ -41,4 +41,4 @@ If you received a notification that the SSL IP address of your Azure App Service
 
 ## Next steps
 
-This article explained how to prepare for an IP address change that was initiated by Azure. For more information about IP addresses in Azure App Service, see [SSL and SSL IP addresses in Azure App Service](overview-inbound-outbound-ips.md).
+This article explained how to prepare for an IP address change that was initiated by Azure. For more information about IP addresses in Azure App Service, see [Inbound and outbound IP addresses in Azure App Service](overview-inbound-outbound-ips.md).
diff --git a/articles/app-service/manage-backup.md b/articles/app-service/manage-backup.md
@@ -40,8 +40,8 @@ The following database solutions are supported with backup feature:
 * The Backup and Restore feature requires the App Service plan to be in the **Standard** tier or **Premium** tier. For more information about scaling your App Service plan to use a higher tier, see [Scale up an app in Azure](manage-scale-up.md). **Premium** tier allows a greater number of daily back ups than **Standard** tier.
 * You need an Azure storage account and container in the same subscription as the app that you want to back up. For more information on Azure storage accounts, see [Azure storage account overview](https://docs.microsoft.com/azure/storage/common/storage-account-overview).
 * Backups can be up to 10 GB of app and database content. If the backup size exceeds this limit, you get an error.
-* Backups of SSL enabled Azure Database for MySQL is not supported. If a backup is configured, you will get failed backups.
-* Backups of SSL enabled Azure Database for PostgreSQL is not supported. If a backup is configured, you will get failed backups.
+* Backups of TLS enabled Azure Database for MySQL is not supported. If a backup is configured, you will get failed backups.
+* Backups of TLS enabled Azure Database for PostgreSQL is not supported. If a backup is configured, you will get failed backups.
 * In-app MySQL databases are automatically backed up without any configuration. If you make manually settings for in-app MySQL databases, such as adding connection strings, the backups may not work correctly.
 * Using a firewall enabled storage account as the destination for your backups is not supported. If a backup is configured, you will get failed backups.
 
diff --git a/articles/app-service/manage-custom-dns-buy-domain.md b/articles/app-service/manage-custom-dns-buy-domain.md
@@ -133,7 +133,7 @@ You also see the selected hostnames in the **Custom domains** page, in the **Cus
 ![](./media/custom-dns-web-site-buydomains-web-app/dncmntask-cname-buydomains-hostnames-added.png)
 
 > [!NOTE]
-> A **Not Secure** label for your custom domain means that it's not yet bound to an SSL certificate, and any HTTPS request from a browser to your custom domain will receive an error or warning, depending on the browser. To configure SSL binding, see [Secure a custom DNS name with an SSL binding in Azure App Service](configure-ssl-bindings.md).
+> A **Not Secure** label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive an error or warning, depending on the browser. To configure TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
 >
 
 To test the hostnames, navigate to the listed hostnames in the browser. In the example in the preceding screenshot, try navigating to _kontoso.net_ and _www\.kontoso.net_.
diff --git a/articles/app-service/manage-custom-dns-migrate-domain.md b/articles/app-service/manage-custom-dns-migrate-domain.md
@@ -126,7 +126,7 @@ You can find the deployment unit for your app by looking at the domain name of t
 
 ## Next steps
 
-Learn how to bind a custom SSL certificate to App Service.
+Learn how to bind a custom TLS/SSL certificate to App Service.
 
 > [!div class="nextstepaction"]
-> [Bind an SSL certificate to Azure App Service](configure-ssl-bindings.md)
+> [Secure a custom DNS name with a TLS binding in Azure App Service](configure-ssl-bindings.md)
diff --git a/articles/app-service/overview-hosting-plans.md b/articles/app-service/overview-hosting-plans.md
@@ -27,7 +27,7 @@ The _pricing tier_ of an App Service plan determines what App Service features y
 
 [!INCLUDE [app-service-dev-test-note](../../includes/app-service-dev-test-note.md)]
 
-Each tier also provides a specific subset of App Service features. These features include custom domains and SSL certificates, autoscaling, deployment slots, backups, Traffic Manager integration, and more. The higher the tier, the more features are available. To find out which features are supported in each pricing tier, see [App Service plan details](https://azure.microsoft.com/pricing/details/app-service/plans/).
+Each tier also provides a specific subset of App Service features. These features include custom domains and TLS/SSL certificates, autoscaling, deployment slots, backups, Traffic Manager integration, and more. The higher the tier, the more features are available. To find out which features are supported in each pricing tier, see [App Service plan details](https://azure.microsoft.com/pricing/details/app-service/plans/).
 
 <a name="new-pricing-tier-premiumv2"></a>
 
@@ -66,11 +66,11 @@ Except for **Free** tier, an App Service plan carries an hourly charge on the co
 - In the dedicated compute tiers (**Basic**, **Standard**, **Premium**, **PremiumV2**), the App Service plan defines the number of VM instances the apps are scaled to, so _each VM instance_ in the App Service plan has an hourly charge. These VM instances are charged the same regardless how many apps are running on them. To avoid unexpected charges, see [Clean up an App Service plan](app-service-plan-manage.md#delete).
 - In the **Isolated** tier, the App Service Environment defines the number of isolated workers that run your apps, and _each worker_ is charged hourly. In addition, there's an hourly base fee for the running the App Service Environment itself.
 
-You don't get charged for using the App Service features that are available to you (configuring custom domains, SSL certificates, deployment slots, backups, etc.). The exceptions are:
+You don't get charged for using the App Service features that are available to you (configuring custom domains, TLS/SSL certificates, deployment slots, backups, etc.). The exceptions are:
 
 - App Service Domains - you pay when you purchase one in Azure and when you renew it each year.
 - App Service Certificates - you pay when you purchase one in Azure and when you renew it each year.
-- IP-based SSL connections - There's an hourly charge for each IP-based SSL connection, but some **Standard** tier or above gives you one IP-based SSL connection for free. SNI-based SSL connections are free.
+- IP-based TLS connections - There's an hourly charge for each IP-based TLS connection, but some **Standard** tier or above gives you one IP-based TLS connection for free. SNI-based TLS connections are free.
 
 > [!NOTE]
 > If you integrate App Service with another Azure service, you may need to consider charges from these other services. For example, if you use Azure Traffic Manager to scale your app geographically, Azure Traffic Manager also charges you based on your usage. To estimate your cross-services cost in Azure, see [Pricing calculator](https://azure.microsoft.com/pricing/calculator/). 
@@ -81,7 +81,7 @@ You don't get charged for using the App Service features that are available to y
 
 Your App Service plan can be scaled up and down at any time. It is as simple as changing the pricing tier of the plan. You can choose a lower pricing tier at first and scale up later when you need more App Service features.
 
-For example, you can start testing your web app in a **Free** App Service plan and pay nothing. When you want to add your [custom DNS name](app-service-web-tutorial-custom-domain.md) to the web app, just scale your plan up to **Shared** tier. Later, when you want to [create an SSL binding](configure-ssl-bindings.md), scale your plan up to **Basic** tier. When you want to have [staging environments](deploy-staging-slots.md), scale up to **Standard** tier. When you need more cores, memory, or storage, scale up to a bigger VM size in the same tier.
+For example, you can start testing your web app in a **Free** App Service plan and pay nothing. When you want to add your [custom DNS name](app-service-web-tutorial-custom-domain.md) to the web app, just scale your plan up to **Shared** tier. Later, when you want to [create a TLS binding](configure-ssl-bindings.md), scale your plan up to **Basic** tier. When you want to have [staging environments](deploy-staging-slots.md), scale up to **Standard** tier. When you need more cores, memory, or storage, scale up to a bigger VM size in the same tier.
 
 The same works in the reverse. When you feel you no longer need the capabilities or features of a higher tier, you can scale down to a lower tier, which saves you money.
 
diff --git a/articles/app-service/overview-inbound-outbound-ips.md b/articles/app-service/overview-inbound-outbound-ips.md
@@ -19,7 +19,7 @@ Regardless of the number of scaled-out instances, each app has a single inbound
 
 - Delete an app and recreate it in a different resource group.
 - Delete the last app in a resource group _and_ region combination and recreate it.
-- Delete an existing SSL binding, such as during certificate renewal (see [Renew certificate](configure-ssl-certificate.md#renew-certificate)).
+- Delete an existing TLS binding, such as during certificate renewal (see [Renew certificate](configure-ssl-certificate.md#renew-certificate)).
 
 ## Find the inbound IP
 
@@ -31,7 +31,7 @@ nslookup <app-name>.azurewebsites.net
 
 ## Get a static inbound IP
 
-Sometimes you might want a dedicated, static IP address for your app. To get a static inbound IP address, you need to configure an [IP-based SSL binding](configure-ssl-bindings.md#secure-a-custom-domain). If you don't actually need SSL functionality to secure your app, you can even upload a self-signed certificate for this binding. In an IP-based SSL binding, the certificate is bound to the IP address itself, so App Service provisions a static IP address to make it happen. 
+Sometimes you might want a dedicated, static IP address for your app. To get a static inbound IP address, you need to [secure a custom domain](configure-ssl-bindings.md#secure-a-custom-domain). If you don't actually need TLS functionality to secure your app, you can even upload a self-signed certificate for this binding. In an IP-based TLS binding, the certificate is bound to the IP address itself, so App Service provisions a static IP address to make it happen. 
 
 ## When outbound IPs change
 
diff --git a/articles/app-service/overview-security.md b/articles/app-service/overview-security.md
@@ -26,14 +26,14 @@ The following sections show you how to further protect your App Service app from
 
 ## HTTPS and Certificates
 
-App Service lets you secure your apps with [HTTPS](https://wikipedia.org/wiki/HTTPS). When your app is created, its default domain name (\<app_name>.azurewebsites.net) is already accessible using HTTPS. If you [configure a custom domain for your app](app-service-web-tutorial-custom-domain.md), you should also [secure it with an SSL certificate](configure-ssl-bindings.md) so that client browsers can make secured HTTPS connections to your custom domain. There are several types of certificates supported by App Service:
+App Service lets you secure your apps with [HTTPS](https://wikipedia.org/wiki/HTTPS). When your app is created, its default domain name (\<app_name>.azurewebsites.net) is already accessible using HTTPS. If you [configure a custom domain for your app](app-service-web-tutorial-custom-domain.md), you should also [secure it with a TLS/SSL certificate](configure-ssl-bindings.md) so that client browsers can make secured HTTPS connections to your custom domain. There are several types of certificates supported by App Service:
 
 - Free App Service Managed Certificate
 - App Service certificate
 - Third-party certificate
 - Certificate imported from Azure Key Vault
 
-For more information, see [Add an SSL certificate in Azure App Service](configure-ssl-certificate.md).
+For more information, see [Add a TLS/SSL certificate in Azure App Service](configure-ssl-certificate.md).
 
 ## Insecure protocols (HTTP, TLS 1.0, FTP)
 
diff --git a/articles/app-service/overview.md b/articles/app-service/overview.md
@@ -12,7 +12,7 @@ ms.custom: mvc, seodec18
 
 *Azure App Service* is an HTTP-based service for hosting web applications, REST APIs, and mobile back ends. You can develop in your favorite language, be it .NET, .NET Core, Java, Ruby, Node.js, PHP, or Python. Applications run and scale with ease on both Windows and Linux-based environments. For Linux-based environments, see [App Service on Linux](containers/app-service-linux-intro.md). 
 
-App Service not only adds the power of Microsoft Azure to your application, such as security, load balancing, autoscaling, and automated management. You can also take advantage of its DevOps capabilities, such as continuous deployment from Azure DevOps, GitHub, Docker Hub, and other sources, package management, staging environments, custom domain, and SSL certificates. 
+App Service not only adds the power of Microsoft Azure to your application, such as security, load balancing, autoscaling, and automated management. You can also take advantage of its DevOps capabilities, such as continuous deployment from Azure DevOps, GitHub, Docker Hub, and other sources, package management, staging environments, custom domain, and TLS/SSL certificates. 
 
 With App Service, you pay for the Azure compute resources you use. The compute resources you use is determined by the _App Service plan_ that you run your apps on. For more information, see [Azure App Service plans overview](overview-hosting-plans.md).
 
diff --git a/articles/app-service/samples-cli.md b/articles/app-service/samples-cli.md
@@ -24,7 +24,7 @@ The following table includes links to bash scripts built using the Azure CLI.
 | [Create an ASP.NET Core app in a Docker container](./scripts/cli-linux-docker-aspnetcore.md?toc=%2fcli%2fazure%2ftoc.json)| Creates an App Service app on Linux and loads a Docker image from Docker Hub. |
 |**Configure app**||
 | [Map a custom domain to an app](./scripts/cli-configure-custom-domain.md?toc=%2fcli%2fazure%2ftoc.json)| Creates an App Service app and maps a custom domain name to it. |
-| [Bind a custom SSL certificate to an app](./scripts/cli-configure-ssl-certificate.md?toc=%2fcli%2fazure%2ftoc.json)| Creates an App Service app and binds the SSL certificate of a custom domain name to it. |
+| [Bind a custom TLS/SSL certificate to an app](./scripts/cli-configure-ssl-certificate.md?toc=%2fcli%2fazure%2ftoc.json)| Creates an App Service app and binds the TLS/SSL certificate of a custom domain name to it. |
 |**Scale app**||
 | [Scale an app manually](./scripts/cli-scale-manual.md?toc=%2fcli%2fazure%2ftoc.json) | Creates an App Service app and scales it across 2 instances. |
 | [Scale an app worldwide with a high-availability architecture](./scripts/cli-scale-high-availability.md?toc=%2fcli%2fazure%2ftoc.json) | Creates two App Service apps in two different geographical regions and makes them available through a single endpoint using Azure Traffic Manager. |
diff --git a/articles/app-service/samples-powershell.md b/articles/app-service/samples-powershell.md
@@ -22,7 +22,7 @@ The following table includes links to PowerShell scripts built using the Azure P
 | [Create an app and deploy code to a staging environment](./scripts/powershell-deploy-staging-environment.md?toc=%2fpowershell%2fmodule%2ftoc.json) | Creates an App Service app with a deployment slot for staging code changes. |
 |**Configure app**||
 | [Map a custom domain to an app](./scripts/powershell-configure-custom-domain.md?toc=%2fpowershell%2fmodule%2ftoc.json)| Creates an App Service app and maps a custom domain name to it. |
-| [Bind a custom SSL certificate to an app](./scripts/powershell-configure-ssl-certificate.md?toc=%2fpowershell%2fmodule%2ftoc.json)| Creates an App Service app and binds the SSL certificate of a custom domain name to it. |
+| [Bind a custom TLS/SSL certificate to an app](./scripts/powershell-configure-ssl-certificate.md?toc=%2fpowershell%2fmodule%2ftoc.json)| Creates an App Service app and binds the TLS/SSL certificate of a custom domain name to it. |
 |**Scale app**||
 | [Scale an app manually](./scripts/powershell-scale-manual.md?toc=%2fpowershell%2fmodule%2ftoc.json) | Creates an App Service app and scales it across 2 instances. |
 | [Scale an app worldwide with a high-availability architecture](./scripts/powershell-scale-high-availability.md?toc=%2fpowershell%2fmodule%2ftoc.json) | Creates two App Service apps in two different geographical regions and makes them available through a single endpoint using Azure Traffic Manager. |
diff --git a/articles/app-service/scripts/cli-configure-ssl-certificate.md b/articles/app-service/scripts/cli-configure-ssl-certificate.md
diff --git a/articles/app-service/scripts/powershell-configure-ssl-certificate.md b/articles/app-service/scripts/powershell-configure-ssl-certificate.md

Original file line number	Diff line number	Diff line change
`@@ -133,7 +133,7 @@ You also see the selected hostnames in the Custom domains page, in the **Cus`
`133`	`133`	`![](./media/custom-dns-web-site-buydomains-web-app/dncmntask-cname-buydomains-hostnames-added.png)`
`134`	`134`
`135`	`135`	`> [!NOTE]`
`136`		`-> A Not Secure label for your custom domain means that it's not yet bound to an SSL certificate, and any HTTPS request from a browser to your custom domain will receive an error or warning, depending on the browser. To configure SSL binding, see [Secure a custom DNS name with an SSL binding in Azure App Service](configure-ssl-bindings.md).`
	`136`	`+> A Not Secure label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive an error or warning, depending on the browser. To configure TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).`
`137`	`137`	`>`
`138`	`138`
`139`	`139`	`To test the hostnames, navigate to the listed hostnames in the browser. In the example in the preceding screenshot, try navigating to _kontoso.net_ and _www\.kontoso.net_.`