update sidecar tutorials

cephalin · cephalin · commit 8221b55bb678 · 2025-05-08T12:47:33.000+02:00
diff --git a/articles/app-service/includes/tutorial-sidecar/common-faqs.md b/articles/app-service/includes/tutorial-sidecar/common-faqs.md
@@ -0,0 +1,20 @@
+---
+author: cephalin
+ms.service: azure-app-service
+ms.topic: include
+ms.date: 05/08/2025
+ms.author: cephalin
+---
+
+### How do sidecar containers handle internal communication?
+
+Sidecar containers share the same network host as the main container, so the main container (and other sidecar containers) can reach any port on the sidecar with `localhost:<port>`. The example *startup.sh* uses `localhost:4318` to access port 4318 on the **otel-collector** sidecar.
+
+In the **Edit container** dialog, the **Port** box isn't currently used by App Service. You can use it as part of the sidecar metadata, such as to indicate which port the sidecar is listening to.
+
+### Can a sidecar container receive internet requests?
+
+No. App Service routes internet requests only to the main container. For code-based Linux apps, the built-in Linux container is the main container, and any sidecar container ([sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers)) should be added with `IsMain=false`. For custom containers, all but one of the [sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers) should have `IsMain=false`.
+
+For more information on configuring `IsMain`, see [Microsoft.Web sites/sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers).
+
diff --git a/articles/app-service/includes/tutorial-sidecar/sidecar-overview.md b/articles/app-service/includes/tutorial-sidecar/sidecar-overview.md
@@ -0,0 +1,13 @@
+---
+author: cephalin
+ms.service: azure-app-service
+ms.topic: include
+ms.date: 05/08/2025
+ms.author: cephalin
+---
+
+## What's a sidecar container?
+
+In Azure App Service, you can add up to nine sidecar containers for each Linux app. Sidecar containers let you deploy extra services and features to your Linux apps without making them tightly coupled to the main container (built-in or custom). For example, you can add monitoring, logging, configuration, and networking services as sidecar containers. An OpenTelemetry collector sidecar is one such monitoring example. 
+
+The sidecar containers run alongside the main application container in the same App Service plan.
diff --git a/articles/app-service/tutorial-custom-container-sidecar.md b/articles/app-service/tutorial-custom-container-sidecar.md
@@ -2,7 +2,7 @@
 title: 'Tutorial: Configure a sidecar for a custom container app'
 description: Add sidecar containers to your custom container in Azure App Service. Add or update services to your application without changing your application container.
 ms.topic: tutorial
-ms.date: 04/07/2024
+ms.date: 05/07/2025
 ms.author: cephalin
 author: cephalin
 keywords: azure app service, web app, linux, windows, docker, container, sidecar
@@ -12,15 +12,10 @@ keywords: azure app service, web app, linux, windows, docker, container, sidecar
 
 In this tutorial, you add an OpenTelemetry collector as a sidecar container to a Linux custom container app in Azure App Service. For bring-your-own-code Linux apps, see [Tutorial: Configure a sidecar container for a Linux app in Azure App Service](tutorial-sidecar.md).
 
-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. An OpenTelemetry collector sidecar is one such monitoring example. 
-
-For more information about side container in App Service, see:
-
-- [Introducing Sidecars for Azure App Service for Linux: Now Generally Available](https://azure.github.io/AppService/2024/11/08/Global-Availability-Sidecars.html)
-- [Announcing the general availability of sidecar extensibility in Azure App Service](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-the-general-availability-of-sidecar-extensibility-in-azure-app-servic/4267985)
-
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
+[!INCLUDE [sidecar-overview](includes/tutorial-sidecar/sidecar-overview.md)]
+
 ## 1. Set up the needed resources
 
 First you create the resources that the tutorial uses. They're used for this particular scenario and aren't required for sidecar containers in general.
@@ -154,22 +149,39 @@ When you no longer need the environment, you can delete the resource group, App
 azd down
 ```
 
-## How do sidecar containers handle internal communication?
+## Frequently asked questions
+
+- [What are the differences for sidecar-enabled custom containers?](#what-are-the-differences-for-sidecar-enabled-custom-containers)
+- [How do sidecar containers handle internal communication?](includes/tutorial-sidecar/common-faqs.md#how-do-sidecar-containers-handle-internal-communication)
+- [Can a sidecar container receive internet requests?](includes/tutorial-sidecar/common-faqs.md#can-a-sidecar-container-receive-internet-requests)
+
+## What are the differences for sidecar-enabled custom containers?
+
+You configure sidecar-enabled apps differently than apps that aren't sidecar-enabled.
 
-Sidecar containers share the same network host as the main container, so the main container (and other sidecar containers) can reach any port on the sidecar with `localhost:<port>`. This is exactly how the Nginx container sends data to the sidecar (see the [OpenTelemetry module configuration for the sample Nginx image](https://github.com/Azure-Samples/app-service-sidecar-tutorial-prereqs/blob/main/images/nginx/opentelemetry_module.conf)).
+### Not sidecar-enabled
 
-In the **Edit container** dialog, the **Port** box isn't currently used by App Service. You can use it as part of the sidecar metadata, such as to indicate which port the sidecar is listening to.
+- Container name and types are configured directly with `LinuxFxVersion=DOCKER|<image-details>` (see [az webapp config set --linux-fx-version](/cli/azure/webapp/config)).
+- The main container is configured with app settings, such as:
+    - `DOCKER_REGISTRY_SERVER_URL`
+    - `DOCKER_REGISTRY_SERVER_USERNAME`
+    - `DOCKER_REGISTRY_SERVER_PASSWORD`
+    - `WEBSITES_PORT`
 
-## Differences for sidecar-enabled apps
+### Sidecar-enabled
 
-You configure sidecar-enabled apps differently than apps that aren't sidecar-enabled. Specifically, you don't configure the main container and sidecars with app settings, but directly in the resource properties. These app settings don't apply for sidecar-enabled apps:
+- A sidecar-enabled app is designated by `LinuxFxVersion=sitecontainers` (see [az webapp config set --linux-fx-version](/cli/azure/webapp/config)).
+- The main container is configured with a [sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers) resource. These settings don't apply for sidecar-enabled apps
+    - `DOCKER_REGISTRY_SERVER_URL`
+    - `DOCKER_REGISTRY_SERVER_USERNAME`
+    - `DOCKER_REGISTRY_SERVER_PASSWORD`
+    - `WEBSITES_PORT`
 
-- Registry authentication settings: `DOCKER_REGISTRY_SERVER_URL`, `DOCKER_REGISTRY_SERVER_USERNAME` and `DOCKER_REGISTRY_SERVER_PASSWORD`.
-- Container port: `WEBSITES_PORT`
+[!INCLUDE [common-faqs](includes/tutorial-sidecar/common-faqs.md)]
 
 ## More resources
 
 - [Configure custom container](configure-custom-container.md)
-- [Try out sidecars in this guided lab](https://mslabs.cloudguides.com/guides/Sidecars%20in%20Azure%20App%20Service)
+- [REST API: Web Apps - Create Or Update Site Container](/rest/api/appservice/web-apps/create-or-update-site-container)
+- [Infrastructure as Code: Microsoft.Web sites/sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers)
 - [Deploy custom containers with GitHub Actions](deploy-container-github-action.md)
-- [OpenTelemetry](https://opentelemetry.io/)
diff --git a/articles/app-service/tutorial-sidecar.md b/articles/app-service/tutorial-sidecar.md
@@ -2,7 +2,7 @@
 title: 'Tutorial: Configure a sidecar container'
 description: Add sidecar containers to your Linux app in Azure App Service. Add or update services to your application without changing your application code.
 ms.topic: tutorial
-ms.date: 02/20/2025
+ms.date: 05/08/2025
 ms.author: cephalin
 author: cephalin
 keywords: azure app service, web app, linux, windows, docker, sidecar
@@ -12,15 +12,10 @@ keywords: azure app service, web app, linux, windows, docker, sidecar
 
 In this tutorial, you add an OpenTelemetry collector as a sidecar container to a Linux (bring-your-own-code) app in Azure App Service. For custom containers, see [Tutorial: Configure a sidecar container for custom container in Azure App Service](tutorial-custom-container-sidecar.md).
 
-In Azure App Service, you can add up to nine sidecar containers for each Linux app. Sidecar containers let you deploy extra services and features to your Linux apps without making them tightly coupled to the main (built-in) container. For example, you can add monitoring, logging, configuration, and networking services as sidecar containers. An OpenTelemetry collector sidecar is one such monitoring example. 
-
-For more information about side container in App Service, see:
-
-- [Introducing Sidecars for Azure App Service for Linux: Now Generally Available](https://azure.github.io/AppService/2024/11/08/Global-Availability-Sidecars.html)
-- [Announcing the general availability of sidecar extensibility in Azure App Service](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-the-general-availability-of-sidecar-extensibility-in-azure-app-servic/4267985)
-
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
+[!INCLUDE [sidecar-overview](includes/tutorial-sidecar/sidecar-overview.md)]
+
 ## 1. Set up the needed resources
 
 First you create the resources that the tutorial uses. They're used for this particular scenario and aren't required for sidecar containers in general.
@@ -248,16 +243,13 @@ azd down
 
 ## Frequently asked questions
 
-- [How do sidecar containers handle internal communication?](#how-do-sidecar-containers-handle-internal-communication)
+- [How do sidecar containers handle internal communication?](includes/tutorial-sidecar/common-faqs.md#how-do-sidecar-containers-handle-internal-communication)
+- [Can a sidecar container receive internet requests?](includes/tutorial-sidecar/common-faqs.md#can-a-sidecar-container-receive-internet-requests)
 - [How do I instrument other language stacks?](#how-do-i-instrument-other-language-stacks)
 
-#### How do sidecar containers handle internal communication?
-
-Sidecar containers share the same network host as the main container, so the main container (and other sidecar containers) can reach any port on the sidecar with `localhost:<port>`. The example *startup.sh* uses `localhost:4318` to access port 4318 on the **otel-collector** sidecar.
-
-In the **Edit container** dialog, the **Port** box isn't currently used by App Service. You can use it as part of the sidecar metadata, such as to indicate which port the sidecar is listening to.
+[!INCLUDE [common-faqs](includes/tutorial-sidecar/common-faqs.md)]
 
-#### How do I instrument other language stacks?
+### How do I instrument other language stacks?
 
 You can use a similar approach to instrument apps in other language stacks. For more information, see OpenTelemetry documentation:
 
@@ -269,7 +261,9 @@ You can use a similar approach to instrument apps in other language stacks. For
 
 ## More resources
 
-- [Run a local SLM in a sidecar container in Azure App Service](tutorial-sidecar-local-small-language-model.md)
-- [Try out sidecars in this guided lab](https://mslabs.cloudguides.com/guides/Sidecars%20in%20Azure%20App%20Service)
-- [Deploy to App Service using GitHub Actions](deploy-github-actions.md)
-- [OpenTelemetry](https://opentelemetry.io/)
+- [Tutorial: Run chatbot in App Service with a Phi-3 sidecar extension (ASP.NET Core)](tutorial-ai-slm-dotnet.md)
+- [Tutorial: Run chatbot in App Service with a Phi-3 sidecar extension (Spring Boot)](tutorial-ai-slm-spring-boot.md)
+- [Tutorial: Run chatbot in App Service with a Phi-3 sidecar extension (FastAPI)](tutorial-ai-slm-fastapi.md)
+- [Tutorial: Run chatbot in App Service with a Phi-3 sidecar extension (Express.js)](tutorial-ai-slm-expressjs.md)
+- [REST API: Web Apps - Create Or Update Site Container](/rest/api/appservice/web-apps/create-or-update-site-container)
+- [Infrastructure as Code: Microsoft.Web sites/sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers)
