Understanding Container Apps Revisions

Azure Container Apps uses a revision-based deployment model. When a revision fails, your application stops serving traffic. Common causes include image pull failures, health probe misconfigurations, resource limits, and ingress routing errors. This guide covers every failure scenario.

Why This Problem Matters in Production

In enterprise Azure environments, Azure Container Apps revision issues rarely occur in isolation. They typically surface during peak usage periods, complex deployment scenarios, or when multiple services interact under load. Understanding the underlying architecture helps you move beyond symptom-level fixes to root cause resolution.

Before diving into the diagnostic commands below, it is important to understand the service’s operational model. Azure distributes workloads across multiple fault domains and update domains. When problems arise, they often stem from configuration drift between what was deployed and what the service runtime expects. This mismatch can result from ARM template changes that were not propagated, manual portal modifications that bypassed your infrastructure-as-code pipeline, or service-side updates that changed default behaviors.

Production incidents involving Azure Container Apps revision typically follow a pattern: an initial trigger event causes a cascading failure that affects dependent services. The key to efficient troubleshooting is isolating the blast radius early. Start by confirming whether the issue is isolated to a single resource instance, affects an entire resource group, or spans the subscription. This scoping exercise determines whether you are dealing with a configuration error, a regional service degradation, or a platform-level incident.

The troubleshooting approach in this guide follows the industry-standard OODA loop: Observe the symptoms through metrics and logs, Orient by correlating findings with known failure patterns, Decide on the most likely root cause and remediation path, and Act by applying targeted fixes. This structured methodology prevents the common anti-pattern of random configuration changes that can make the situation worse.

Service Architecture Background

To troubleshoot Azure Container Apps revision effectively, you need a mental model of how the service operates internally. Azure services are built on a multi-tenant platform where your resources share physical infrastructure with other customers. Resource isolation is enforced through virtualization, network segmentation, and quota management. When you experience performance degradation or connectivity issues, understanding which layer is affected helps you target your diagnostics.

The control plane handles resource management operations such as creating, updating, and deleting resources. The data plane handles the runtime operations that your application performs, such as reading data, processing messages, or serving requests. Control plane and data plane often have separate endpoints, separate authentication requirements, and separate rate limits. A common troubleshooting mistake is diagnosing a data plane issue using control plane metrics, or vice versa.

Azure Resource Manager (ARM) orchestrates all control plane operations. When you create or modify a resource, the request flows through ARM to the resource provider, which then provisions or configures the underlying infrastructure. Each step in this chain has its own timeout, retry policy, and error reporting mechanism. Understanding this chain helps you interpret error messages and identify which component is failing.

Checking Revision Status

# List all revisions
az containerapp revision list \
  --name "my-app" \
  --resource-group "my-rg" \
  -o table

# Show specific revision details
az containerapp revision show \
  --name "my-app" \
  --resource-group "my-rg" \
  --revision "my-app--abc123"

# Check container app system logs
az containerapp logs show \
  --name "my-app" \
  --resource-group "my-rg" \
  --type system \
  --follow

Common Failure Scenarios

Image Pull Failures

ContainerCreateFailure: Failed to pull image "myacr.azurecr.io/myapp:latest": 
  unauthorized: authentication required

# Configure ACR authentication with managed identity
az containerapp registry set \
  --name "my-app" \
  --resource-group "my-rg" \
  --server "myacr.azurecr.io" \
  --identity "system"

# Or use admin credentials (not recommended for production)
az containerapp registry set \
  --name "my-app" \
  --resource-group "my-rg" \
  --server "myacr.azurecr.io" \
  --username "myacr" \
  --password "password"

# Verify the image exists
az acr repository show-tags --name "myacr" --repository "myapp" -o table

Health Probe Failures

Container Apps sends health probes to determine if a revision is healthy. If probes fail, the revision is marked as unhealthy and traffic is not routed to it.

{
  "properties": {
    "template": {
      "containers": [{
        "name": "my-app",
        "image": "myacr.azurecr.io/myapp:v1",
        "probes": [
          {
            "type": "Startup",
            "httpGet": {
              "path": "/healthz",
              "port": 8080
            },
            "initialDelaySeconds": 5,
            "periodSeconds": 10,
            "failureThreshold": 30,
            "timeoutSeconds": 3
          },
          {
            "type": "Liveness",
            "httpGet": {
              "path": "/healthz",
              "port": 8080
            },
            "periodSeconds": 30,
            "failureThreshold": 3,
            "timeoutSeconds": 5
          },
          {
            "type": "Readiness",
            "httpGet": {
              "path": "/ready",
              "port": 8080
            },
            "periodSeconds": 10,
            "failureThreshold": 3,
            "timeoutSeconds": 5
          }
        ]
      }]
    }
  }
}

Use a startup probe with a high failureThreshold for applications that take time to initialize. Without it, liveness probes may kill the container before it finishes starting.

Container Crashing on Startup

# View console logs (container stdout/stderr)
az containerapp logs show \
  --name "my-app" \
  --resource-group "my-rg" \
  --type console

# View system logs for platform-level errors
az containerapp logs show \
  --name "my-app" \
  --resource-group "my-rg" \
  --type system

# Stream logs in real-time
az containerapp logs show \
  --name "my-app" \
  --resource-group "my-rg" \
  --type console \
  --follow

Resource Limits

# Update CPU and memory
az containerapp update \
  --name "my-app" \
  --resource-group "my-rg" \
  --cpu 1.0 \
  --memory 2.0Gi

CPU	Memory Options
0.25	0.5Gi
0.5	1.0Gi
0.75	1.5Gi
1.0	2.0Gi
1.25	2.5Gi
1.5	3.0Gi
1.75	3.5Gi
2.0	4.0Gi

Revision Modes

Single Revision Mode

# Set single revision mode (replaces previous revision)
az containerapp update \
  --name "my-app" \
  --resource-group "my-rg" \
  --revision-suffix "v2" \
  --set-env-vars "VERSION=2"

Multiple Revision Mode (Traffic Splitting)

# Enable multiple revision mode
az containerapp revision set-mode \
  --name "my-app" \
  --resource-group "my-rg" \
  --mode "multiple"

# Split traffic between revisions
az containerapp ingress traffic set \
  --name "my-app" \
  --resource-group "my-rg" \
  --revision-weight "my-app--v1=80" "my-app--v2=20"

# Route all traffic to latest
az containerapp ingress traffic set \
  --name "my-app" \
  --resource-group "my-rg" \
  --revision-weight "latest=100"

Ingress Configuration Issues

# Enable external ingress
az containerapp ingress enable \
  --name "my-app" \
  --resource-group "my-rg" \
  --target-port 8080 \
  --type "external" \
  --transport "auto"

# Check ingress configuration
az containerapp ingress show \
  --name "my-app" \
  --resource-group "my-rg"

# Common mistake: target port doesn't match the port your app listens on
# Verify your app's listening port matches --target-port

Correlation and Cross-Service Diagnostics

Modern Azure architectures involve multiple services working together. A problem in Azure Container Apps revision may actually originate in a dependent service. For example, a database timeout might be caused by a network security group rule change, a DNS resolution failure, or a Key Vault access policy that prevents secret retrieval for the connection string.

Use Azure Resource Graph to query the current state of all related resources in a single query. This gives you a snapshot of the configuration across your entire environment without navigating between multiple portal blades. Combine this with Activity Log queries to build a timeline of changes that correlates with your incident window.

Application Insights and Azure Monitor provide distributed tracing capabilities that follow a request across service boundaries. When a user request touches multiple Azure services, each service adds its span to the trace. By examining the full trace, you can see exactly where latency spikes or errors occur. This visibility is essential for troubleshooting in microservices architectures where a single user action triggers operations across dozens of services.

For complex incidents, consider creating a war room dashboard in Azure Monitor Workbooks. This dashboard should display the key metrics for all services involved in the affected workflow, organized in the order that a request flows through them. Having this visual representation during an incident allows the team to quickly identify which service is the bottleneck or failure point.

Scaling Issues

# Configure scaling rules
az containerapp update \
  --name "my-app" \
  --resource-group "my-rg" \
  --min-replicas 1 \
  --max-replicas 10 \
  --scale-rule-name "http-rule" \
  --scale-rule-type "http" \
  --scale-rule-http-concurrency 50

If your app takes a long time to start, set min-replicas to at least 1 to avoid cold starts. Scale-to-zero is useful for cost savings but introduces startup latency.

Environment Variables and Secrets

# Set environment variables
az containerapp update \
  --name "my-app" \
  --resource-group "my-rg" \
  --set-env-vars "DB_HOST=mydb.postgres.database.azure.com" "APP_ENV=production"

# Create a secret
az containerapp secret set \
  --name "my-app" \
  --resource-group "my-rg" \
  --secrets "db-password=MySecretPassword123"

# Reference secret in environment variable
az containerapp update \
  --name "my-app" \
  --resource-group "my-rg" \
  --set-env-vars "DB_PASSWORD=secretref:db-password"

Performance Baseline and Anomaly Detection

Effective troubleshooting requires knowing what normal looks like. Establish performance baselines for Azure Container Apps revision that capture typical latency distributions, throughput rates, error rates, and resource utilization patterns across different times of day, days of the week, and seasonal periods. Without these baselines, you cannot distinguish between a genuine degradation and normal workload variation.

Azure Monitor supports dynamic alert thresholds that use machine learning to automatically learn your workload’s patterns and alert only on statistically significant deviations. Configure dynamic thresholds for your key metrics to reduce false positive alerts while still catching genuine anomalies. The learning period requires at least three days of historical data, so deploy dynamic alerts well before you need them.

Create a weekly health report that summarizes the key metrics for Azure Container Apps revision and highlights any trends that warrant attention. Include the 50th, 95th, and 99th percentile latencies, the total error count and error rate, the peak utilization as a percentage of provisioned capacity, and any active alerts or incidents. Distribute this report to the team responsible for the service so they maintain awareness of the service’s health trajectory.

When a troubleshooting investigation reveals a previously unknown failure mode, add it to your team’s knowledge base along with the diagnostic steps and resolution. Over time, this knowledge base becomes an invaluable resource that accelerates future troubleshooting efforts and reduces dependency on individual experts. Structure the entries using a consistent format: symptoms, diagnostic commands, root cause analysis, resolution steps, and preventive measures.

Deactivating and Restarting Revisions

# Deactivate a broken revision
az containerapp revision deactivate \
  --name "my-app" \
  --resource-group "my-rg" \
  --revision "my-app--broken"

# Restart a revision (creates new replicas)
az containerapp revision restart \
  --name "my-app" \
  --resource-group "my-rg" \
  --revision "my-app--v1"

Log Analytics Queries

// Container Apps system errors
ContainerAppSystemLogs_CL
| where TimeGenerated > ago(1h)
| where Log_s contains "error" or Log_s contains "fail"
| project TimeGenerated, RevisionName_s, Log_s
| order by TimeGenerated desc

// Container crash events
ContainerAppSystemLogs_CL
| where TimeGenerated > ago(24h)
| where Reason_s == "BackOff" or Reason_s == "CrashLoopBackOff"
| project TimeGenerated, RevisionName_s, Reason_s, Log_s
| order by TimeGenerated desc

Monitoring and Alerting Strategy

Reactive troubleshooting is expensive. For every hour spent diagnosing a production issue, organizations lose revenue, customer trust, and engineering productivity. A proactive monitoring strategy for Azure Container Apps revision should include three layers of observability.

The first layer is metric-based alerting. Configure Azure Monitor alerts on the key performance indicators specific to this service. Set warning thresholds at 70 percent of your limits and critical thresholds at 90 percent. Use dynamic thresholds when baseline patterns are predictable, and static thresholds when you need hard ceilings. Dynamic thresholds use machine learning to adapt to your workload’s natural patterns, reducing false positives from expected daily or weekly traffic variations.

The second layer is log-based diagnostics. Enable diagnostic settings to route resource logs to a Log Analytics workspace. Write KQL queries that surface anomalies in error rates, latency percentiles, and connection patterns. Schedule these queries as alert rules so they fire before customers report problems. Consider implementing a log retention strategy that balances diagnostic capability with storage costs, keeping hot data for 30 days and archiving to cold storage for compliance.

The third layer is distributed tracing. When Azure Container Apps revision participates in a multi-service transaction chain, distributed tracing via Application Insights or OpenTelemetry provides end-to-end visibility. Correlate trace IDs across services to pinpoint exactly where latency or errors originate. Without this correlation, troubleshooting multi-service failures becomes a manual, time-consuming process of comparing timestamps across different log streams.

Beyond alerting, implement synthetic monitoring that continuously tests critical user journeys even when no real users are active. Azure Application Insights availability tests can probe your endpoints from multiple global locations, detecting outages before your users do. For Azure Container Apps revision, create synthetic tests that exercise the most business-critical operations and set alerts with a response time threshold appropriate for your SLA.

Operational Runbook Recommendations

Document the troubleshooting steps from this guide into your team’s operational runbook. Include the specific diagnostic commands, expected output patterns for healthy versus degraded states, and escalation criteria for each severity level. When an on-call engineer receives a page at 2 AM, they should be able to follow a structured decision tree rather than improvising under pressure.

Consider automating the initial diagnostic steps using Azure Automation runbooks or Logic Apps. When an alert fires, an automated workflow can gather the relevant metrics, logs, and configuration state, package them into a structured incident report, and post it to your incident management channel. This reduces mean time to diagnosis (MTTD) by eliminating the manual data-gathering phase that often consumes the first 15 to 30 minutes of an incident response.

Implement a post-incident review process that captures lessons learned and feeds them back into your monitoring and runbook systems. Each incident should result in at least one improvement to your alerting rules, runbook procedures, or service configuration. Over time, this continuous improvement cycle transforms your operations from reactive fire-fighting to proactive incident prevention.

Finally, schedule regular game day exercises where the team practices responding to simulated incidents. Azure Chaos Studio can inject controlled faults into your environment to test your monitoring, alerting, and runbook effectiveness under realistic conditions. These exercises build muscle memory and identify gaps in your incident response process before real incidents expose them.

Summary

Container Apps revision failures come from image pull errors (configure ACR authentication with managed identity), health probe misconfigurations (use startup probes for slow-starting apps), resource limits (match CPU/memory to your workload), and ingress target port mismatches (ensure --target-port matches your app’s listening port). Use az containerapp logs show --type system for platform errors and --type console for application logs. In multiple revision mode, use traffic splitting for safe deployments.

For more details, refer to the official documentation: Azure Container Apps overview, Ingress in Azure Container Apps, Update and deploy changes in Azure Container Apps.