Azure Virtual Desktop business continuity and disaster recovery concepts
Many users now work remotely, so organizations require solutions with high availability, rapid deployment speed, and reduced costs. Users also need to have a remote work environment with guaranteed availability and resiliency that lets them access their resources even during disasters.
To prevent system outages or downtime, every system and component in your Azure Virtual Desktop deployment must be fault-tolerant. Fault tolerance is when you have a duplicate configuration or system in another Azure region that takes over for the main configuration during an outage. This secondary configuration or system reduces the impact of a localized outage. There are many ways you can set up fault tolerance, but this article focuses on the methods currently available in Azure for dealing with business continuity and disaster recovery (BCDR).
Responsibility for components that make up Azure Virtual Desktop are divided between those components that are Microsoft-managed, and those components that are customer-managed, or partner managed.
The following components are customer-managed or partner-managed:
- Session host virtual machines
- Profile management, usually with FSLogix
- Applications
- User data
- User identities
To learn about the Microsoft-managed components and how they're designed to be resilient, see Azure Virtual Desktop service architecture and resilience.
Business continuity and disaster recovery basics
When you design a disaster recovery plan, you should keep the following three things in mind:
- High availability: distributed infrastructure so smaller, more localized outages don't interrupt your entire deployment. Designing with high availability in mind can minimize outage impact and avoid the need for a full disaster recovery.
- Business continuity: how an organization can keep operating during outages of any size.
- Disaster recovery: the process of getting back to operation after a full outage.
Azure Virtual Desktop doesn't have any native features for managing disaster recovery scenarios, but you can use many other Azure services for each scenario depending on your requirements, such as Availability sets, availability zones, Azure Site Recovery, and Azure Files data redundancy options for user profiles and data.
You can also distribute session hosts across multiple Azure regions provides even more geographical distribution, which further reduces outage impact. All these and other Azure features provide a certain level of protection within Azure Virtual Desktop, and you should carefully consider them along with any cost implications.
We have further documentation that goes into much more detail about each of the technology areas you need to consider as part of your business continuity and disaster recovery strategy and how to plan for and mitigate disruption to your organization based on your requirements. The following table lists the technology areas you need to consider as part of your disaster recovery strategy and links to other Microsoft documentation that provides guidance for each area:
| Technology area | Documentation link |
|---|---|
| Active-passive vs active-active plans | Active-Active vs. Active-Passive |
| Session host resiliency | Multiregion Business Continuity and Disaster Recovery |
| Disaster recovery plans | Multiregion Business Continuity and Disaster Recovery |
| Azure Site Recovery | Failover and failback |
| Network connectivity | Multiregion Business Continuity and Disaster Recovery |
| User profiles | Design recommendations |
| Files share storage | Storage |
| Identity provider | Identity |
| Backup | Backup |
Related content
For more in-depth information about disaster recovery for Azure Virtual Desktop, check out these articles: