Merge pull request #314088 from cdpark/refresh-containerapps-batch5

Feature 544850: Q&M: Azure Container Apps Freshness (Set 3 of 5) - batch 5

Author: v-dirichards

articles/container-apps/TOC.yml

@@ -236,7 +236,7 @@ items:
           href: troubleshooting.md
         - name: Errors and failures
           items:
-            - name: Container create
+            - name: Container exits
               href: troubleshoot-container-create-failures.md
             - name: Open Container Initiative (OCI)
               href: troubleshoot-open-container-initiative-errors.md

articles/container-apps/troubleshoot-container-create-failures.md

@@ -1,18 +1,18 @@
 ---
-title: Troubleshoot container create failures in Azure Container Apps
-description: Learn to troubleshoot container create failures in Azure Container Apps
+title: Troubleshoot Container Exit Failures in Azure Container Apps
+description: Learn to troubleshoot container exit events in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 01/24/2025
+ms.date: 04/01/2026
 ms.author: cshoe
 ms.custom:
 ---
 
-# Troubleshoot container create failures in Azure Container Apps
+# Troubleshoot container exit failures in Azure Container Apps
 
-Container exit events indicate that a container is stopped or exited. These exit events can significantly impact the availability, stability, and performance of your container app. The underlying issues that trigger these events can potentially lead to downtime or degraded service. Each event is recorded to provide insights into the container's lifecycle, helping you diagnose issues related to the container's execution.
+Container exit events indicate that a container is stopped or exited. These exit events can significantly affect the availability, stability, and performance of your container app. The underlying issues that trigger these events can potentially lead to downtime or degraded service. Each event is recorded to provide insights into the container's lifecycle, helping you diagnose issues related to the container's execution.
 
 When a container exits, it could exit with a nonzero exit code (indicating failure) or a zero exit code (indicating a normal exit). Azure logs each exit event to give you visibility into what happened during the container's run.
 
@@ -22,19 +22,19 @@ The following list details different reasons your application can experience con
 
 - **Application crash or exception**: If the application inside the container encounters an error or exception that it can't recover from, the error can cause the container to exit. Application errors are among the most common reasons for container exit events.
 
-- **Out of memory (OOM) errors**: If the container consumes more memory than the allocated limit, the system might kill the container due to out-of-memory (OOM) errors.
+- **Out-of-memory (OOM) errors**: If the container consumes more memory than the allocated limit, the system might kill the container due to OOM errors.
 
 - **Incorrect exit code or misconfiguration in the container**: The container might exit intentionally (but improperly) if the application inside the container exits with a nonzero exit code, indicating an abnormal termination. Additionally, misconfigurations in the container can lead to immediate container shutdown. Misconfigurations that affect the app include missing environment variables, incorrect startup command, or invalid container entry point.  
 
 - **Application termination (normal exit)**: A container might exit normally as the application inside completes its task, for example a batch job or a one-off process. This exit condition is expected behavior when the container is configured for short-lived tasks or single-use jobs.
 
 ## Diagnostics
 
-The Container Apps diagnostics features an intelligent and interactive experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Azure Container Apps diagnostics.
+Container Apps features an intelligent and interactive diagnostics experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Container Apps diagnostics.
 
 1. Go to your container app in the Azure portal.
 
-1. Select **Diagnose and solve problems**.
+1. Select **Diagnose and solve problems** in the sidebar menu.
 
 1. Under the troubleshooting categories, select the **Availability and Performance** category tile.
 

articles/container-apps/troubleshoot-health-probe-failures.md

@@ -1,24 +1,24 @@
 ---
-title: Troubleshoot health probe failures in Azure Container Apps
-description: Learn to troubleshoot health probe failures in Azure Container Apps
+title: Troubleshoot Health Probe Failures in Azure Container Apps
+description: Learn to troubleshoot health probe failures in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 01/24/2025
+ms.date: 04/01/2026
 ms.author: cshoe
 ms.custom:
 ---
 
 # Troubleshoot health probe failures in Azure Container Apps
 
-Health probe failures for in Azure Container Apps indicates that the container app doesn't pass the required health checks and could be considered unhealthy or unready.
+Health probe failures in Azure Container Apps indicate that the container app doesn't pass the required health checks and could be considered unhealthy or unready.
 
-Health Probes are a great way to determine application health. Specifically, health probes help work around performance issues related to timeouts during container startup, deadlocks when running the container, and serving traffic when the container is not ready to accept traffic.
+Health probes are a great way to determine application health. Specifically, health probes help work around performance issues related to timeouts during container startup, deadlocks when running the container, and serving traffic when the container isn't ready to accept traffic.
 
 ## Causes
 
-Factors related to the container configuration and environments that can lead to a health probe failures include::
+Factors that can lead to health probe failures include:
 
 - **Incorrect health probe configuration**: Configuration errors surrounding protocols, endpoint addresses, paths, ports, and response codes result in probe failures and mark the container as unhealthy.
 
@@ -28,21 +28,21 @@ Factors related to the container configuration and environments that can lead to
 
 ## Diagnostics
 
-The Container Apps diagnostics features an intelligent and interactive experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Azure Container Apps diagnostics.
+Container Apps features an intelligent and interactive diagnostics experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Container Apps diagnostics.
 
 1. Go to your container app in the Azure portal.
 
-1. Select **Diagnose and solve problems**.
+1. Select **Diagnose and solve problems** in the sidebar menu.
 
 1. Under the troubleshooting categories, select the **Availability and Performance** category tile.
 
-1. In the left navigation of the *Availability and Performance* section, select **Health Probe Failures**.
+1. Select **Health Probe Failures**.
 
     This report provides details on the issue, possible causes, and recommended resolutions.
 
     You can review health probe failure events by revision by selecting the required revision of your container app.  
 
-    From this page you can view health probe failure events per revision by health probe type, inside a time frame, and by failure type.
+    From this page, you can view health probe failure events per revision by health probe type, inside a time frame, and by failure type.
 
     You can also review the health probe configuration per revision for your container app by selecting the required revision from the dropdown.
 

articles/container-apps/troubleshoot-storage-mount-failures.md

@@ -1,18 +1,18 @@
 ---
-title: Troubleshoot storage mount failures in Azure Container Apps
-description: Learn to troubleshoot storage mount failures in Azure Container Apps
+title: Troubleshoot Storage Mount Failures in Azure Container Apps
+description: Learn to troubleshoot storage mount failures in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 01/24/2025
+ms.date: 04/01/2026
 ms.author: cshoe
 ms.custom:
 ---
 
 # Troubleshoot storage mount failures in Azure Container Apps
 
-Azure Container Apps allow containers to interact with external storage systems, such as Azure Files, Azure Blob Storage, or Azure Managed Disks, for persisting data. These storage resources are mounted to the container's file system during container startup.
+Azure Container Apps allows containers to interact with external storage systems, such as Azure Files, Azure Blob Storage, or Azure Managed Disks, for persisting data. These storage resources are mounted to the container's file system during container startup.
 
 Storage mount failures occur when your app's container is unable to successfully mount or access required storage resources, such as volumes or file systems.
 
@@ -28,15 +28,15 @@ Storage mount failures occur when your app's container is unable to successfully
 
 ## Diagnostics
 
-The Container Apps diagnostics features an intelligent and interactive experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Azure Container Apps diagnostics.
+Container Apps features an intelligent and interactive diagnostics experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Container Apps diagnostics.
 
 1. Go to your container app in the Azure portal.
 
-1. Select **Diagnose and solve problems**.
+1. Select **Diagnose and solve problems** in the sidebar menu.
 
 1. Under the troubleshooting categories, select the **Availability and Performance** category tile.
 
-1. From the left navigation, select **Storage Mount Failures** to diagnose and troubleshoot the issue.
+1. Select **Storage Mount Failures** to diagnose and troubleshoot the issue.
 
     This report provides details on the issue, possible causes, and recommended resolutions.
 

articles/container-apps/troubleshoot-target-port-settings.md

@@ -1,47 +1,47 @@
 ---
-title: Troubleshoot target port settings in Azure Container Apps
-description: Learn to troubleshoot target port settings in Azure Container Apps
+title: Troubleshoot Target Port Settings in Azure Container Apps
+description: Learn to troubleshoot target port settings in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 01/24/2025
+ms.date: 04/01/2026
 ms.author: cshoe
 ms.custom:
 ---
 
 # Troubleshoot target port settings in Azure Container Apps
 
-Incorrect target port settings in a container app prevent incoming requests from reaching the correct port where the container listens for traffic. This port mismatch stops the container app from routing external traffic to the right application inside the container. Such misconfiguration can cause app downtime or delays in serving requests, reducing service availability. Additionally, if the app scales and the target port is misconfigured, new instances might not function correctly, negatively impacting overall performance and scalability.
+Incorrect target port settings in a container app prevent incoming requests from reaching the correct port where the container listens for traffic. This port mismatch stops the container app from routing external traffic to the right application inside the container. Such misconfiguration can cause app downtime or delays in serving requests, reducing service availability. Additionally, if the app scales and the target port is misconfigured, new instances might not function correctly, which can negatively impact overall performance and scalability.
 
 ## Causes
 
-- **Port not exposed in dockerfile or app configuration**: This error comes when there's a mismatch between the container configuration and the port where the application is listening. For instance, if:
+- **Port not exposed in dockerfile or app configuration**: This error comes when there's a mismatch between the container configuration and the port where the application is listening. For instance:
 
-  - The container configurations don't expose the required port using the `EXPOSE` directive.
+  - If the container configurations don't expose the required port using the `EXPOSE` directive.
 
-  - The containerized application inside the app isn't configured to listen on the container app's expected routing or networking port.
+  - If the containerized application inside the app isn't configured to listen on the container app's expected routing or networking port.
 
-    Then the ports are mismatched. For example, the container might be configured to listen on port `8080`, but the container app is expecting it to be on port `80`.
+    Then the ports are mismatched. For example, the container might be configured to listen on port `8080`, but the container app expects it to be on port `80`.
 
 - **Multiple containers and service ports conflicts**: In a scenario where multiple containers are running in the same app, there could be conflicts between different services trying to use the same port. Ensuring that each service listens to a unique port or that the routing is configured correctly is essential.
 
 ## Diagnostics
 
-The Container Apps diagnostics features an intelligent and interactive experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Azure Container Apps diagnostics.
+Container Apps features an intelligent and interactive diagnostics experience that helps you troubleshoot your app with no configuration required. Use the following steps to access Container Apps diagnostics.
 
 1. Go to your container app in the Azure portal.
 
-1. Select **Diagnose and solve problems**.
+1. Select **Diagnose and solve problems** in the sidebar menu.
 
 1. Under the troubleshooting categories, select the **Availability and Performance** category tile.
 
-1. In the left navigation, select **Container Apps Ingress Port settings check** to diagnose and troubleshoot the issue.
+1. Select **Ingress Port settings check** to diagnose and troubleshoot the issue.
 
     Select the required revision of your container app from the dropdown. The latest revision would be populated by default.
 
     :::image type="content" source="media/troubleshooting/port-mismatch.png" alt-text="Screenshot of port mismatch report.":::
 
     This report provides details on the issue, possible causes, and recommended resolutions.
 
-    These errors are only raised when the container app is trying to start or scale. Therefore, if the tool doesn't find any issues during a given period, try running the detector during a time when you know the container app is expected to start or scale. In the case when the app isn't receiving any traffic, try to browse the issue or trigger it.
+    These errors are only raised when the container app is trying to start or scale. If the tool doesn't find any issues during a given period, try running the detector during a time when you know the container app is expected to start or scale. In the case when the app isn't receiving any traffic, try to browse the issue or trigger it.