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

[faisalriazz]

Blue/Green Deployment Strategy for .NET Aspire on Azure Container Apps (ACA)

Context

We have a production environment built using .NET Aspire, deployed to Azure Container Apps (ACA) via Azure Developer CLI (azd). Our current architecture includes:

• Azure Application Gateway v2 (WAF)
• Internal Azure Container Apps Environment
• Multiple Container Apps:
  • portal-app
  • admin-app
  • portal-api
  • admin-api
  • Background jobs
• Private DNS Zones
• Azure Key Vault
• IAM VM / NGINX reverse proxy
• Private endpoints (for DB and Key Vault)
• Internal Load Balancer
• Managed identities

Current Deployment Model

Deployments are performed directly to the existing ACA environment using azd up.

---

Requirement: Blue/Green Deployment

Clients are requesting a Blue/Green deployment strategy with the following goals:
✅ Near-zero downtime
✅ Easy rollback
✅ Pre-validation of new releases before traffic switch
✅ Minimal impact on internal networking/private endpoints
✅ Compatibility with .NET Aspire orchestration

---

Questions

1. Recommended Approach for Blue/Green in ACA

Which of the following is the best fit for our architecture?

• ACA Revisions with Traffic Splitting
  • Pros/Cons?
  • How does this integrate with Application Gateway?
• Separate Container Apps Environments (Blue/Green)
  • How to manage networking (Private DNS, Private Endpoints)?
  • Impact on Managed Identities?
• Separate Aspire Environments/Stamps
  • How to orchestrate with azd?
• Separate Application Gateway Backend Pools
  • How to sync with ACA revisions?

2. Compatibility with Existing Components

How does Blue/Green work with:

• Internal-only ACA ingress?
• Private DNS Zones?
• Application Gateway (WAF rules, backend health probes)?
• Managed Identities (do they need duplication)?
• Private Endpoints (DB, Key Vault)?

3. Officially Recommended Workflows

Is there a Microsoft-recommended deployment workflow for:

• .NET Aspire + ACA?
• Azure Developer CLI (azd)?
• Enterprise-grade Blue/Green?

4. Best Practices

What are the best practices for:

• Database migrations during Blue/Green?
  • Schema changes, backward compatibility?
• Session/State Management?
  • Sticky sessions, distributed cache (Redis)?
• Avoiding Background Job Duplication?
  • Singleton patterns, leader election?
• Rollback Strategy?
  • Automated vs. manual rollback triggers?

5. Reference Architectures & Examples

Are there any Microsoft reference architectures or production examples for:

• Enterprise-grade Blue/Green with ACA?
• Lessons learned from real-world deployments?

---