Blue/Green Deployment Strategy for .NET Aspire + Azure Container Apps + Azure Developer CLI

Hi @Faisal Riaz ,

Thanks for reaching out to Microsoft Q&A.

It looks like you’re aiming for a true Blue/Green deployment on Azure Container Apps with .NET Aspire and azd-driven pipelines zero downtime, easy rollback, private networking…it’s all doable with Container Apps’ built-in revision & traffic-splitting features.

Check the below approach, some pipeline patterns and best practices:

1. Leverage Container Apps revisions & traffic splitting

• Enable multiple active revisions in your Container Apps (configuration.activeRevisionsMode=“multiple”).
• Deploy each new version as a new revision and label it “green” (old revision is “blue”).
• Assign 0% weight to green initially, perform validation against its label-specific FQDN (e.g. green.<your-app>.azurecontainerapps.io).
• Once validated, shift 100% traffic to green: az containerapp ingress traffic set --name <app> --resource-group <rg> --label-weight blue=0 green=100
• If something goes wrong, simply switch back to blue by reverting weights.

2. Keeping it all inside your existing ACA Environment vs. separate stamps

Recommended: Single Container Apps environment. You don’t need two separate ACA environments—revisions/labels handle traffic isolation.

• You’ll still use your internal VNet-isolated Container Apps environment. Traffic routing is managed by your internal App Gateway plus Private DNS.
• Application Gateway backend pools can reference the labeled FQDNs or the Container Apps custom domain, so you just update route weight in App GW when switching.

3. Integrating with Azure Developer CLI / azd pipelines

• azd pipeline config can be extended with extra steps:
  • Step “Build & publish” pushes a new Docker image.
  • Step “Deploy green revision” runs az containerapp update/create with --revision-suffix and --label green, weight 0.
  • Step “Validate” runs your smoke/performance tests against green label URL.
  • Step “Traffic switch” (conditional on tests) runs az containerapp ingress traffic set to shift 100% to green.
  • Step “Rollback” (on test or production failure) reverses the weights back to blue.
  • You can implement those as Azure DevOps YAML jobs or GitHub Actions, just wrap the azure-cli calls.

4. Networking, DNS & App Gateway considerations

• Internal-only ingress: your Container Apps environment sits in the VNet, and the App Gateway (WAF v2) fronts it.
• Use Azure Private DNS Zones for your custom domain and map both blue and green labels (or use CNAME to the built-in FQDN).
• App Gateway backend pools can point to the ACA internal endpoint via private IP or FQDN. When you switch traffic, you can either:
  • Update App GW routing rules/CSS to point to the new label FQDN, or
  • Keep App GW untouched and rely on Container Apps’ built-in traffic weights (preferred).
• Managed identities, key vault private endpoints, DB endpoints, etc. all remain unchanged because you’re not tearing down environments only spinning up new revisions.

5. Secrets & certificates

• Store all secrets/certs in Azure Key Vault.
• Use Container Apps’ Key Vault references (via managed identity) so each revision automatically picks up the right values.
• With .NET Aspire you can wire IConfiguration to Azure Key Vault references, so no changes needed between blue/green.

6. Rollback strategy

• Keep the last stable revision labeled “blue.” Never delete it until green has been live and stable for your SLA window.
• In your pipeline maintain a pointer or variable for the last known good revision ID—so you can automate the rollback script easily.

7. Reference architectures & samples

• Official Blue/Green in Container Apps (azure-cli & Bicep)
• GitHub sample workflow “containerapps-blue-green”
• Deploy a Container Apps environment into a VNet
• Quickstart: create an environment and container app via CLI

Thanks @Pravallika KV for your reply.
Infrastructure details i shared are already established and working. Now I want to implement Blue/Green Deployment.
I have following queries/confusions:
1- Do i need to change my Aspire.Appshost Program.cs ? I think yes but how ?
2- Do i need to add Blue/Green deployment suffix ? I think yes, but keeping in view of my project where should i change it ?
3- Do i need to change infra/bicep files ? i think yes but would it be change automatically based on my apphost program.cs / manifest file ?
4- Do i need to change my existing azd pipeline config yaml file for blue/green deployment ? I think yes and how to switch between blue and green deployment in the same pipeline or different pipeline? How should i change my existing pipeline.
5- I am using sequential deployment with templates.
6- What would be the effect on cache and background server with respect to Green/Blue deployment since there is almost no change in both containers for each deployment.

Hope I am able to convey my point.