Skip to content

Zone Redundancy

Zone redundancy improves resilience within a single region, but it is not a substitute for full multi-region disaster recovery.

Prerequisites

  • A target region that supports the required Container Apps resilience features
  • Infrastructure as Code for environment creation
  • A decision on whether zonal failure tolerance is enough for the workload
export RG="rg-aca-prod"
export ENVIRONMENT_NAME="aca-env-prod"
export LOCATION="eastus"

When to Use

  • When you need protection from a single availability zone failure
  • When you need a lower-complexity option than multi-region deployment
  • When you need to explain why zonal resilience and regional resilience are different

Procedure

  1. Check the current reliability guidance for Azure Container Apps.
  2. Confirm the target region and environment type support zone redundancy.
  3. Decide whether the setting must be enabled at environment creation.
  4. Compare the zonal design against your DR objectives.

Illustrative Bicep shape:

resource managedEnvironment 'Microsoft.App/managedEnvironments@2024-03-01' = {
  name: envName
  location: location
  properties: {
    zoneRedundant: true
  }
}

Microsoft Learn now documents the current zone-redundancy rules: zone redundancy is available to all Container Apps plans, it must be enabled during environment creation, it can't be changed afterward, and it doesn't add charges beyond standard Container Apps pricing.

flowchart TD
    A[Need higher availability] --> B{Failure domain}
    B -->|Single-zone failure| C[Zone redundancy]
    B -->|Regional outage| D[Multi-region design]
    C --> E[Lower complexity]
    D --> F[Stronger failover posture]

Verification

  • Confirm the environment reports the expected zone-redundancy state.
  • Confirm the region and environment type support the configuration.
  • Confirm your DR plan does not treat zone redundancy as a regional failover solution.

Rollback / Troubleshooting

  • If the setting is immutable, recreate the environment instead of editing in place.
  • If the region does not support the setting, move to a supported region or a multi-region pattern.
  • If RTO or RPO targets exceed a single region, use multi-region instead.

See Also

Sources