Reliability in Microsoft Purview
This article describes reliability support in Microsoft Purview for governance experiences, and covers both regional resiliency with availability zones and disaster recovery and business continuity. For a more detailed overview of reliability principles in Azure, see Azure reliability.
Availability zone support
Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. In the case of a local zone failure, availability zones are designed so that if the one zone is affected, regional services, capacity, and high availability are supported by the remaining two zones.
Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see Regions and availability zones.
Azure availability zones-enabled services are designed to provide the right level of reliability and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see Recommendations for using availability zones and regions.
Microsoft Purview makes commercially reasonable efforts to support zone-redundant availability zones, where resources automatically replicate across zones, without any need for you to set up or configure.
Prerequisites
- Microsoft Purview governance experience currently provides partial availablility-zone support in a limited number of regions. This partial availability-zone support covers experiences (and/or certain functionalities within an experience).
- Zone availability might or might not be available for Microsoft Purview governance experiences or features/functionalities that are in preview.
Supported regions
Microsoft Purview makes commercially reasonable efforts to provide availability zone support in various regions as follows:
| Region | Data Map | Scan | Policy | Insights |
|---|---|---|---|---|
| Southeast Asia | 
|
|
|
|
| East US |
|
|
|
|
| Australia East |
|
|
|
|
| West US 2 |
|
|
|
|
| Canada Central |
|
|
|
|
| Central India |
|
|
||
| East US 2 |
|
|
|
|
| France Central |
|
|
|
|
| Germany West Central |
|
|
|
|
| Japan East |
|
|
|
|
| Korea Central |
|
|
|
|
| West US 3 |
|
|
|
|
| North Europe |
|
|
|
|
| South Africa North |
|
|
|
|
| Sweden Central |
|
|
|
|
| Switzerland North |
|
|||
| USGov Virginia |
|
|
|
|
| South Central US |
|
|
|
|
| Brazil South |
|
|
|
|
| UK South |
|
|
|
|
| Qatar Central |
|
|
|
|
| China North 3 |
|
|
|
|
| West Europe |
|
|
|
Disaster recovery and business continuity
Disaster recovery (DR) is about recovering from high-impact events, such as natural disasters or failed deployments that result in downtime and data loss. Regardless of the cause, the best remedy for a disaster is a well-defined and tested DR plan and an application design that actively supports DR. Before you begin to think about creating your disaster recovery plan, see Recommendations for designing a disaster recovery strategy.
When it comes to DR, Microsoft uses the shared responsibility model. In a shared responsibility model, Microsoft ensures that the baseline infrastructure and platform services are available. At the same time, many Azure services don't automatically replicate data or fall back from a failed region to cross-replicate to another enabled region. For those services, you are responsible for setting up a disaster recovery plan that works for your workload. Most services that run on Azure platform as a service (PaaS) offerings provide features and guidance to support DR and you can use service-specific features to support fast recovery to help develop your DR plan.
Important
Today, Microsoft Purview doesn't support automated disaster recovery. Until that support is added, you're responsible to take care of backup and restore activities. You can manually create a secondary Microsoft Purview account as a warm standby instance in another region. Note that this standby instance in another region would not support Microsoft Purview Data Governance Solution. Today, it only supports Azure Purview solution. We are working on adding DR support for Microsoft Purview Data Governance Solution.
To implement disaster recovery for Microsoft Purview, see the Microsoft Purview disaster recovery documentation.