Include RDS component and template handling in a Site Recovery plan

Source facts

Microsoft’s RDS guidance places all component VMs into an Azure Site Recovery recovery plan to automate failover. The plan identifies its source and target, which can be another RDS site or Azure. In the pooled-VM example, a recovered generalized template is shut down because RDS requires a stopped template to create the pooled configuration. The example identifies the template by VM ID when names are shared between sites. Microsoft documentation.

Applicability

Inventory the actual RDS deployment type, component VMs, templates, target site, and dependent services. Review which example actions apply to the deployment before incorporating them into the plan.

DSE recommendation

Create an ordered recovery worksheet that distinguishes component startup from template handling and host registration. Ask the RDS owner to identify the template and workload instances unambiguously. Review script assumptions, pending restarts, and the expected management endpoint at the target site.

Verification

Exercise the plan in the approved recovery-test environment and verify both service access and the intended template state. Test the relevant desktop creation or reconnection workflow after recovery. Record component failures and identity mismatches separately, and reconcile them before calling the RDS recovery plan complete.

Official references

Microsoft Learn: Create your disaster recovery plan. Source reviewed September 8, 2026.