Hello @anshuman-nath!
Based on the information you provided, here are my answers to your questions: Q1. For VMSS replication and protection using Azure Site Recovery (ASR), you can use either uniform or flexible orchestration. In your scenario, since you have a single stateless workload, uniform orchestration would be a good fit. You can keep the VM template in a storage account and replicate it to your DR site. During a planned or unplanned outage, you can use the replicated VM template to bring up the VMSS on the secondary site. The RTO (Recovery Time Objective) would depend on various factors such as the size of the VMSS, the amount of data to be replicated, and the network bandwidth between the primary and secondary sites. It's recommended to perform a DR drill to estimate the RTO. Q2. Yes, it's possible to use Blue-Green Deployment setup in the primary site with Azure Site Recovery in the DR site. You don't need to change the replication targets and policies in every app release cycle. You can fixate the replication target only to the Blue version, which is serving production traffic. When you release a new build (Green version), you can replicate it to the DR site and perform a DR drill to validate the failover process. Once you're confident that the Green version is stable, you can switch the traffic to it and make it the new Blue version. Then, you can replicate the new Blue version to the DR site and repeat the process. This way, you can ensure that the DR site is always in sync with the production site.