Merge pull request #313111 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-13 05:00 UTC

Author: learn-build-service-prod[bot]

articles/app-service/configure-ssl-certificate-in-code.md

@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE [app-service-managed-certificate](./includes/managed-certs/managed-certs-note.md)]
 
-In your application code, you can access both [public key certificates and certificates that contain a private key that you add to Azure App Service.](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use public or private certificates in your application code.
+In your application code, you can access both [public key certificates and certificates that contain a private key that you add to Azure App Service.](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use publicly or privately signed certificates in your application code.
 
 This approach to using certificates in your code makes use of the Transport Layer Security (TLS) functionality in App Service, which requires your app to be in the Basic tier or higher. If your app is in the Free or Shared tier, you can [include the certificate file in your app repository](#load-a-certificate-from-a-file).
 
@@ -111,7 +111,7 @@ For languages that don't support or offer insufficient support for the Windows c
 
 ## Load a certificate from a file
 
-If you need to load a certificate file that you upload manually, it's better to upload the certificate by using [File Transfer Protocol Secure (FTPS)](deploy-ftp.md) instead of [Git](deploy-local-git.md), for example. Keep sensitive data like a private certificate out of source control.
+If you need to load a certificate file that you upload manually, it's better to upload the certificate by using [File Transfer Protocol Secure (FTPS)](deploy-ftp.md) instead of [Git](deploy-local-git.md), for example. Keep sensitive data like certificate private keys out of source control.
 
 ASP.NET and ASP.NET Core on Windows must access the certificate store even if you load a certificate from a file. To load a certificate file in a Windows .NET app, load the current user profile with the following command in <a target="_blank" href="https://shell.azure.com" >Cloud Shell</a>:
 
@@ -140,7 +140,7 @@ To see how to load a TLS/SSL certificate from a file in Node.js, PHP, Python, or
 
 The `WEBSITE_LOAD_CERTIFICATES` app setting makes the specified certificates accessible to your Windows or Linux custom containers (including built-in Linux containers) as files. The files are found under the following directories:
 
-| Container platform | Public certificates | Private certificates |
+| Container platform | Public certificate files (no private key) | Certificate files that include a private key |
 | - | - | - |
 | Windows container | `C:\appservice\certificates\public` | `C:\appservice\certificates\private` |
 | Linux container | `/var/ssl/certs` | `/var/ssl/private` |

articles/app-service/overview-hosting-plans.md

@@ -35,7 +35,7 @@ The pricing tier of an App Service plan determines what App Service features you
 | Category | Tiers | Description |
 |:-|:-|:-|
 | Shared compute | Free, Shared | Free and Shared, the two base tiers, run an app on the same Azure VM as other App Service apps, including apps of other customers. These tiers allocate CPU quotas to each app that runs on the shared resources. The resources can't scale out. These tiers are intended for only development and testing purposes. |
-| Dedicated compute | Basic, Standard, Premium, PremiumV2, PremiumV3, PremiumV4 | The Basic, Standard, Premium, PremiumV2, PremiumV3, and PremiumV4 tiers run apps on dedicated Azure VMs. Only apps in the same App Service plan share the same compute resources. The higher the tier, the more VM instances that are available to you for scale-out. |
+| Dedicated compute | Basic, Standard, Premium, PremiumV2, PremiumV3, PremiumV4 | The Basic, Standard, Premium, PremiumV2, PremiumV3, and PremiumV4 tiers run apps on dedicated Azure VMs. Only apps in the same App Service plan share the same compute resources (and those resources aren't shared with other customers). The higher the tier, the more VM instances that are available to you for scale-out. |
 | Isolated | IsolatedV2 | The IsolatedV2 tier runs dedicated Azure VMs on dedicated Azure virtual networks. This tier provides network isolation on top of compute isolation to your apps. It provides the maximum scale-out capabilities. |
 
 Each tier also provides a specific subset of App Service features. These features include custom domains and TLS/SSL certificates, autoscaling, deployment slots, backups, Azure Traffic Manager integration, and more. The higher the tier, the more features that are available. To find out which features are supported in each pricing tier, see the [App Service plan details](https://azure.microsoft.com/pricing/details/app-service/windows/#pricing).

articles/app-service/provision-resource-bicep.md

@@ -108,15 +108,17 @@ az group create --name myResourceGroup --location "southcentralus" &&
 az deployment group create --resource-group myResourceGroup --template-file <path-to-template>
 ```
 
-To deploy a different language stack, update `linuxFxVersion` with appropriate values. The following table lists examples. To show current versions, run the following command in Cloud Shell: `az webapp config show --resource-group myResourceGroup --name <app-name> --query linuxFxVersion`.
-
-| Language    | Example                                              |
-|-------------|------------------------------------------------------|
-| .NET    | `linuxFxVersion="DOTNETCORE&#124;3.0"`                 |
-| PHP     | `linuxFxVersion="PHP&#124;7.4"`                        |
-| Node.js | `linuxFxVersion="NODE&#124;24"`                     |
-| Java    | `linuxFxVersion="JAVA&#124;1.8 &#124;TOMCAT&#124;9.0"` |
-| Python  | `linuxFxVersion="PYTHON&#124;3.14"`                     |
+To deploy a different language stack, update `linuxFxVersion` with appropriate values. The following table lists examples. To show the current version, run the following command in Cloud Shell: `az webapp config show --resource-group myResourceGroup --name <app-name> --query linuxFxVersion`.
+
+| Language | Example |
+|--------|---------|
+| .NET | `linuxFxVersion="DOTNETCORE|8.0"` |
+| PHP | `linuxFxVersion="PHP|8.2"` |
+| Node.js | `linuxFxVersion="NODE|20-lts"` |
+| Java | `linuxFxVersion="TOMCAT|9.0-jre8"` |
+| Python | `linuxFxVersion="PYTHON|3.11"` |
+
+Use the `az webapp list-runtimes --os linux` command to review the current list of supported Linux runtime values. 
 
 ---