Edit

About Azure Recovery Orchestration Plan (preview)

Azure Recovery Orchestration Plan performs efficient and seamless recovery by orchestrating recovery across multiple resources within an application for zonal resiliency. The capability integrates with Azure Service Groups to provide application-level recovery orchestration.

Key benefits of Azure Recovery Orchestration Plan

With Recovery Orchestration Plan, you can:

  • Define the order of recovery for resources within your application using customizable groups.
  • Perform automated readiness checks to detect drift in your applications, increasing the chances of successful recovery.
  • Execute zonal failover operations across multiple resource types.
  • Automate group-level actions using Azure Automation Runbooks.
  • Reprotect resources after failover to maintain ongoing protection.

Note

The Recovery Orchestration Plan orchestrates recovery and doesn’t protect individual resources. To protect resources, configure Azure Site Recovery for Virtual Machines (VMs) or use Highly Available (HA) solutions for other resources. This capability supports only zonal recovery and doesn’t support regional recovery.

Understand recovery plan components and actions

This section defines how recovery plans organize resources, track states, and execute operations for coordinated recovery.

Recovery Plan and Service Groups

A Recovery Orchestration Plan gets created within a Service Group. A Service Group represents your application and contains the Azure resources that create your application. The Recovery Plan orchestrates the failover of these resources in a defined order.

Plan status

The following plan statuses indicate the readiness for failover:

  • Ready: The plan meets all requirements for failover. No resources have Needs Attention status.
  • Warning: Some resources require attention, but you can still initiate failover if at least one included resource doesn’t have a Needs Attention status.

Groups and recovery order

Groups define the order of resource recovery. By default, a Default Group is created. You can create other groups and move resources between them.

Resources within the same group failover in parallel. Resources in different groups fail over sequentially - Group 2 starts only after all Group 1 resources complete failover.

Resource protection and inclusion status

Each resource has a protection status and an inclusion status:

  • Protection status: Azure Site Recovery, Highly Available (HA) solutions, or Not protected.
  • Included: Resources actively part of the plan, orchestrated during failover.
  • Excluded: Resources not included. HA resources are automatically excluded.
  • State not selected: Default state for unprotected or non-HA resources. You must explicitly include or exclude the resources.

Resources with Needs Attention status

Resources with issues preventing failover orchestration are marked Needs Attention with an appropriate reason. Resolve all Needs Attention items to move the plan to Ready state.

Readiness checks

Automated readiness checks run every 24 hours. The readiness checks are categorized as:

  • Application Modification check: Detects resources added to or removed from a Service Group.
  • Protection health check: Validates protection solution and health for each resource.

You can also run readiness checks on demand from the Execute menu.

Execution operations

The execution operations for plan orchestration are categorized as:

  • Failover: Orchestrates failover from the active zone to the recovery zone.
  • Reprotect: Reprotects resources after failover for continued replication.
  • Readiness check: Runs on-demand readiness assessments.

Group actions

Add Azure Automation Runbooks as prescripts and post-scripts. You can also add manual steps.

  • Pre-scripts: Runs before group resources begin failover.
  • Post-scripts: Runs after group resources complete failover.
  • Manual actions: Allows resuming the failover job when it’s paused.

Role-based access control

To create and manage a Recovery Plan, you need one of the following roles:

  • Azure Resilience Management Recovery Contributor
  • Azure Resilience Management Recovery Administrator

Related content

  • Last updated on