Merge pull request #49108 from wwlpublish/c4d2e9587f5a51d3ea2fcbaab2300038fce1c415f3ebf50c804bc37afbeea844-live

JamesJBarnett · web-flow · commit 4aa2c3bd661e · 2025-02-10T15:17:59.000-07:00
Modules/M01-introduction-azure-app-service
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/1-introduction.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/1-introduction.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 09/30/2024
+  ms.date: 02/10/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/introduction-to-azure-app-service/2-azure-app-service.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/2-azure-app-service.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Examine Azure App Service
   description: "Examine Azure App Service"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/2-azure-app-service.md)]
+  [!include[](includes/2-azure-app-service.md)]
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/3-azure-app-service-plans.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/3-azure-app-service-plans.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Examine Azure App Service plans
   description: "Examine Azure App Service plans"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 4
 content: |
-  [!include[](includes/3-azure-app-service-plans.md)]
+  [!include[](includes/3-azure-app-service-plans.md)]
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/4-deploy-code-to-app-service.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/4-deploy-code-to-app-service.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Deploy to App Service
   description: "Deploy to App Service"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/4-deploy-code-to-app-service.md)]
+  [!include[](includes/4-deploy-code-to-app-service.md)]
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/5-authentication-authorization-app-service.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/5-authentication-authorization-app-service.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore authentication and authorization in App Service
   description: "Explore authentication and authorization in App Service"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 6
 content: |
-  [!include[](includes/5-authentication-authorization-app-service.md)]
+  [!include[](includes/5-authentication-authorization-app-service.md)]
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/6-network-features.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/6-network-features.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Discover App Service networking features
   description: "Discover App Service networking features"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 4
 content: |
-  [!include[](includes/6-network-features.md)]
+  [!include[](includes/6-network-features.md)]
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/7-create-html-web-app.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/7-create-html-web-app.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: Create a static HTML web app by using Azure Cloud Shell'
   description: "Exercise: Create a static HTML web app by using Azure Cloud Shell"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
@@ -16,4 +16,4 @@ azureSandbox: true
 durationInMinutes: 15
 content: |
   [!include[](includes/7-create-html-web-app.md)]
-interactive: bash
+interactive: bash
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/8-knowledge-check.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/8-knowledge-check.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
@@ -37,4 +37,4 @@ quiz:
       explanation: "Correct. Hybrid Connections are an outbound network feature."
     - content: "Service endpoints"
       isCorrect: false
-      explanation: "Incorrect. Service endpoints are an inbound network feature."
+      explanation: "Incorrect. Service endpoints are an inbound network feature."
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/9-summary.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/9-summary.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 09/30/2024
+  ms.date: 02/10/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/9-summary.md)]
+  [!include[](includes/9-summary.md)]
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/2-azure-app-service.md b/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/2-azure-app-service.md
@@ -10,15 +10,15 @@ With Azure App Service, you can deploy and run containerized web apps on Windows
 
 ## Continuous integration/deployment support
 
-The Azure portal provides out-of-the-box continuous integration and deployment with Azure DevOps Services, GitHub, Bitbucket, FTP, or a local Git repository on your development machine. Connect your web app with any of the above sources and App Service will do the rest for you by auto-syncing code and any future changes on the code into the web app. Continuous integration and deployment for containerized web apps is also supported using either Azure Container Registry or Docker Hub.
+The Azure portal provides out-of-the-box continuous integration and deployment with Azure DevOps Services, GitHub, Bitbucket, FTP, or a local Git repository on your development machine. Connect your web app with any of the above sources and App Service will do the rest for you by autosyncing code and any future changes on the code into the web app. Continuous integration and deployment for containerized web apps is also supported using either Azure Container Registry or Docker Hub.
 
 ## Deployment slots
 
-When deploying a web app you can use a separate deployment slot instead of the default production slot when you're running in the Standard App Service Plan tier or better. Deployment slots are live apps with their own host names. App content and configurations elements can be swapped between two deployment slots, including the production slot.
+When deploying a web app, you can use a separate deployment slot instead of the default production slot when you're running in the Standard App Service Plan tier or better. Deployment slots are live apps with their own host names. App content and configurations elements can be swapped between two deployment slots, including the production slot.
 
 ## App Service on Linux
 
-App Service can also host web apps natively on Linux for supported application stacks. It can also run custom Linux containers (also known as Web App for Containers). App Service on Linux supports many language specific built-in images. Just deploy your code. Supported languages and frameworks include: Node.js, Java (JRE 8 & JRE 11), PHP, Python, .NET, and Ruby. If the runtime your application requires isn't supported in the built-in images, you can deploy it with a custom container.
+App Service can also host web apps natively on Linux for supported application stacks. It can also run custom Linux containers (also known as *Web App for Containers*). App Service on Linux supports many language specific built-in images. Just deploy your code. Supported languages and frameworks include: .NET Core, Java (Tomcat, JBoss EAP, or Java SE with an embedded web server), Node.js, Python, and PHP. If the runtime your application requires isn't supported in the built-in images, you can deploy it with a custom container.
 
 The languages, and their supported versions, are updated regularly. You can retrieve the current list by using the following command in the Cloud Shell.
 
@@ -34,3 +34,8 @@ App Service on Linux does have some limitations:
 * The Azure portal shows only features that currently work for Linux apps. As features are enabled, they're activated on the portal.
 * When deployed to built-in images, your code and content are allocated a storage volume for web content, backed by Azure Storage. The disk latency of this volume is higher and more variable than the latency of the container filesystem. Apps that require heavy read-only access to content files might benefit from the custom container option, which places files in the container filesystem instead of on the content volume.
 
+## App Service Environment
+
+App Service Environment is an Azure App Service feature that provides a fully isolated and dedicated environment for running App Service apps. It offers improved security at high scale.
+
+Unlike the App Service offering, where supporting infrastructure is shared, with App Service Environment, compute is dedicated to a single customer. For more information on the differences between App Service Environment and App Service, see the [comparison](/azure/app-service/environment/ase-multi-tenant-comparison).
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/3-azure-app-service-plans.md b/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/3-azure-app-service-plans.md
@@ -11,7 +11,7 @@ When you create an App Service plan in a certain region (for example, West Europ
 The *pricing tier* of an App Service plan determines what App Service features you get and how much you pay for the plan. There are a few categories of pricing tiers:
 
 * **Shared compute**: **Free** and **Shared**, the two base tiers, runs 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, and the resources can't scale out.
-* **Dedicated compute**: The **Basic**, **Standard**, **Premium**, **PremiumV2**, and **PremiumV3** 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 are available to you for scale-out.
+* **Dedicated compute**: The **Basic**, **Standard**, **Premium**, **PremiumV2**, and **PremiumV3** tiers run apps on dedicated Azure VMs. Only apps in the same App Service plans share the same compute resources. The higher the tier, the more VM instances are available to you for scale-out.
 * **Isolated**: The **Isolated** and **IsolatedV2** tiers run dedicated Azure VMs on dedicated Azure Virtual Networks. It provides network isolation on top of compute isolation to your apps. It provides the maximum scale-out capabilities.
 
 > [!NOTE]
@@ -30,7 +30,7 @@ In this way, the App Service plan is the **scale unit** of the App Service apps.
 
 ## What if my app needs more capabilities or features?
 
-Your App Service plan can be scaled up and down at any time. It's as simple as changing the pricing tier of the plan. If your app is in the same App Service plan with other apps, you may want to improve the app's performance by isolating the compute resources. You can do it by moving the app into a separate App Service plan.
+Your App Service plan can be scaled up and down at any time. It's as simple as changing the pricing tier of the plan. If your app is in the same App Service plan with other apps, you might want to improve the app's performance by isolating the compute resources. You can do it by moving the app into a separate App Service plan.
 
 You can potentially save money by putting multiple apps into one App Service plan. However, since apps in the same App Service plan all share the same compute resources you need to understand the capacity of the existing App Service plan and the expected load for the new app.
 
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/4-deploy-code-to-app-service.md b/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/4-deploy-code-to-app-service.md
@@ -15,7 +15,7 @@ Azure supports automated deployment directly from several sources. The following
 There are a few options that you can use to manually push your code to Azure:
 
 * **Git**: App Service web apps feature a Git URL that you can add as a remote repository. Pushing to the remote repository deploys your app.
-* **CLI**: `webapp up` is a feature of the `az` command-line interface that packages your app and deploys it. Unlike other deployment methods, `az webapp up` can create a new App Service web app for you if you haven't already created one.
+* **CLI**: `webapp up` is a feature of the `az` command-line interface that packages your app and deploys it. Unlike other deployment methods, `az webapp up` can create a new App Service web app for you.
 * **Zip deploy**: Use `curl` or a similar HTTP utility to send a ZIP of your application files to App Service.
 * **FTP/S**: FTP or FTPS is a traditional way of pushing your code to many hosting environments, including App Service.
 
@@ -25,12 +25,18 @@ Whenever possible, use deployment slots when deploying a new production build. W
 
 ### Continuously deploy code
 
-If your project has designated branches for testing, QA, and staging, then each of those branches should be continuously deployed to a staging slot. This allows your stakeholders to easily assess and test the deployed branch.
+If your project designates branches for testing, QA, and staging, then each of those branches should be continuously deployed to a staging slot. This allows your stakeholders to easily assess and test the deployed branch.
 
 ### Continuously deploy containers
 
 For custom containers from Azure Container Registry or other container registries, deploy the image into a staging slot and swap into production to prevent downtime. The automation is more complex than code deployment because you must push the image to a container registry and update the image tag on the webapp.
 
-* **Build and tag the image**: As part of the build pipeline, tag the image with the git commit ID, timestamp, or other identifiable information. It’s best not to use the default “latest” tag. Otherwise, it’s difficult to trace back what code is currently deployed, which makes debugging far more difficult.
+* **Build and tag the image**: As part of the build pipeline, tag the image with the git commit ID, timestamp, or other identifiable information. It’s best not to use the default "latest" tag. Otherwise, it’s difficult to trace back what code is currently deployed, which makes debugging far more difficult.
 * **Push the tagged image**: Once the image is built and tagged, the pipeline pushes the image to our container registry. In the next step, the deployment slot will pull the tagged image from the container registry.
-* **Update the deployment slot with the new image tag**: When this property is updated, the site will automatically restart and pull the new container image.
+* **Update the deployment slot with the new image tag**: When this property is updated, the site automatically restarts and pulls the new container image.
+
+## Sidecar containers
+
+In Azure App Service, you can add up to nine sidecar containers for each sidecar-enabled custom container app. Sidecar containers let you deploy extra services and features to your container application without making them tightly coupled to your main application container. For example, you can add monitoring, logging, configuration, and networking services as sidecar containers.
+
+You can add a sidecar container through the **Deployment Center** in the app's management page. 
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/5-authentication-authorization-app-service.md b/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/5-authentication-authorization-app-service.md
@@ -16,18 +16,20 @@ App Service uses federated identity, in which a third-party identity provider ma
 
 | Provider | Sign-in endpoint | How-To guidance |
 |--|--|--|
-| Microsoft identity platform | `/.auth/login/aad` | [App Service Microsoft identity platform login](/azure/app-service/configure-authentication-provider-aad) |
+| Microsoft Entra | `/.auth/login/aad` | [App Service Microsoft Entra platform login](/azure/app-service/configure-authentication-provider-aad) |
 | Facebook | `/.auth/login/facebook` | [App Service Facebook login](/azure/app-service/configure-authentication-provider-facebook) |
 | Google | `/.auth/login/google` | [App Service Google login](/azure/app-service/configure-authentication-provider-google) |
-| X | `/.auth/login/twitter` | [App Service X login](/azure/app-service/configure-authentication-provider-twitter) |
+| X | `/.auth/login/x` | [App Service X login](/azure/app-service/configure-authentication-provider-twitter) |
 | Any OpenID Connect provider | `/.auth/login/<providerName>` | [App Service OpenID Connect login](/azure/app-service/configure-authentication-provider-openid-connect) |
 | GitHub | `/.auth/login/github` | [App Service GitHub login](/azure/app-service/configure-authentication-provider-github) |
 
-When you enable authentication and authorization with one of these providers, its sign-in endpoint is available for user authentication and for validation of authentication tokens from the provider. You can provide your users with any number of these sign-in options.
+When you configure this feature with one of these providers, its sign-in endpoint is available for user authentication and for validation of authentication tokens from the provider. You can provide your users with any number of these sign-in options.
 
 ## How it works
 
-The authentication and authorization module runs in the same sandbox as your application code. When enabled, every incoming HTTP request passes through it before being handed to your application code. This module handles several things for your app:
+The authentication and authorization middleware component is a feature of the platform that runs on the same VM as your application. When enabled, every incoming HTTP request passes through it before being handled by your application.
+
+The platform middleware handles several things for your app:
 
 * Authenticates users and clients with the specified identity provider
 * Validates, stores, and refreshes OAuth tokens issued by the configured identity provider
@@ -37,7 +39,7 @@ The authentication and authorization module runs in the same sandbox as your app
 The module runs separately from your application code and can be configured using Azure Resource Manager settings or using a configuration file. No SDKs, specific programming languages, or changes to your application code are required.
 
 > [!NOTE]
-> In Linux and containers the authentication and authorization module runs in a separate container, isolated from your application code. Because it does not run in-process, no direct integration with specific language frameworks is possible.
+> In Linux and containers the authentication and authorization module runs in a separate container, isolated from your application code. Because it doesn't run in-process, no direct integration with specific language frameworks is possible.
 
 ### Authentication flow
 
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/6-network-features.md b/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/6-network-features.md
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/7-create-html-web-app.md b/learn-pr/wwl-azure/introduction-to-azure-app-service/includes/7-create-html-web-app.md
diff --git a/learn-pr/wwl-azure/introduction-to-azure-app-service/index.yml b/learn-pr/wwl-azure/introduction-to-azure-app-service/index.yml
