Welcome to this module on planning and implementing a disaster recovery plan for Azure Virtual Desktop.  In this module, we will cover the following:

• Disaster Recovery for Azure Virtual Desktop
• Virtual Machine Replication
• And finally, FSLogix Replication

Let's start by discussing disaster recovery in Azure Virtual Desktop.  Azure Virtual Desktop offers business continuity disaster recovery for the AVD service to preserve customer metadata during outages.

When setting up disaster recovery, you initially need to replicate your virtual machines to a secondary location.  We will discuss this in more detail shortly.  If you are using profile containers, you should also set up data replication in the same secondary location.

It is vitally important that user identities that are set up in the primary location are also made available in the secondary location.  Finally, make sure any line-of-business applications which use the data in your primary location are also failed over to the secondary location.

Let's now discuss virtual machine replication.  As part of your disaster recovery plan for Azure Virtual Desktop, VMs need to be replicated to the secondary zone.  It is recommended to use Azure Site Recovery to manage replication VMs to other Azure locations.

Once the VMs are replicated, you should turn them off to ensure you can save on cost.  One of the benefits of using Azure Site Recovery to replicate the VMs to another location is that you will not need to register the VMs manually as the Azure Virtual Desktop agent in the secondary VM will automatically use the latest security token to connect to the service instance closest to it.

Something to note is that if there are existing user connections during any type of outage, you will be required to end the user connections in the current region before you can start the failover to the secondary location.

In the final lecture of this module, we will talk about FSLogix replication. When setting up disaster recovery for profiles, which uses FSLogix there are some configuration steps you need to follow.  FSLogix supports multiple profile locations, so can enter the secondary location within the same registry entry you configure for the primary.

You will be required to provision an additional Azure file share in the second location to facilitate disaster recovery for the FSLogix user profile service.

In the event that the primary FSLogix profile path is unavailable, the FSLogix agent will automatically failover to the secondary, therefore it is recommended that the FSLogix agent be configured with a path to the secondary location.