Skip to content

Commit dbf6d08

Browse files
committed
edits
1 parent 118ac5f commit dbf6d08

File tree

2 files changed

+11
-33
lines changed

2 files changed

+11
-33
lines changed

articles/reliability/includes/reliability-disaster-recovery-description-include.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,12 @@
44
author: anaharris-ms
55
ms.service: azure
66
ms.topic: include
7-
ms.date: 08/25/2023
7+
ms.date: 03/05/2025
88
ms.author: anaharris
99
ms.custom: include file
1010
---
1111

1212

13-
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](/azure/well-architected/reliability/disaster-recovery).
14-
15-
16-
When it comes to DR, Microsoft uses the [shared responsibility model](../concept-shared-responsibility.md). 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're 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](../reliability-guidance-overview.md) to help develop your DR plan.
17-
18-
19-
13+
Disaster recovery (DR) refers to practices that organizations use to recover 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 start creating your disaster recovery plan, see [Recommendations for designing a disaster recovery strategy](/azure/well-architected/reliability/disaster-recovery).
2014

15+
For DR, Microsoft uses the [shared responsibility model](../concept-shared-responsibility.md). In this model, Microsoft ensures that the baseline infrastructure and platform services are available. However, 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're 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. You can use [service-specific features to support fast recovery](../reliability-guidance-overview.md) to help develop your DR plan.

articles/reliability/reliability-deployment-environments.md

Lines changed: 8 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -11,30 +11,15 @@ ms.custom: subject-reliability, references_regions
1111

1212
# Reliability in Azure Deployment Environments
1313

14-
This article describes reliability support in Azure Deployment Environments, and covers intra-regional resiliency with availability zones and inter region resiliency with disaster recovery. For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/well-architected/resiliency/overview).
14+
This article describes reliability support in Azure Deployment Environments. It covers intra-regional resiliency with availability zones and inter-region resiliency with disaster recovery. For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/well-architected/resiliency/overview).
1515

1616
## Availability zone support
1717

1818
[!INCLUDE [Availability zone description](../reliability/includes/reliability-availability-zone-description-include.md)]
1919

20-
2120
Availability zone support for all resources in Azure Deployment Environments is enabled automatically. There's no action for you to take.
2221

23-
Regions supported:
24-
- West US 2
25-
- South Central US
26-
- UK South
27-
- West Europe
28-
- East US
29-
- Australia East
30-
- East US 2
31-
- North Europe
32-
- West US 3
33-
- Japan East
34-
- East Asia
35-
- Central India
36-
- Korea Central
37-
- Canada Central
22+
For a list of regions that support Azure Deployment Environments, see [Product Availability by Region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/table).
3823

3924
For more detailed information on availability zones in Azure, see [Regions and availability zones](../reliability/availability-zones-overview.md).
4025

@@ -44,17 +29,15 @@ For more detailed information on availability zones in Azure, see [Regions and
4429

4530
You can replicate the following Deployment Environments resources in an alternate region to prevent data loss if a cross-region failover occurs:
4631

47-
- Dev center
48-
- Project
49-
- Catalog
32+
- Dev centers
33+
- Projects
34+
- Catalogs
5035
- Catalog items
51-
- Dev center environment type
52-
- Project environment type
36+
- Dev center environment types
37+
- Project environment types
5338
- Environments
5439

55-
56-
57-
For more information on Azure disaster recovery architecture, see [Azure to Azure disaster recovery architecture](../site-recovery/azure-to-azure-architecture.md).
40+
For more information, see [Azure to Azure disaster recovery architecture](../site-recovery/azure-to-azure-architecture.md).
5841

5942
## Next steps
6043

0 commit comments

Comments
 (0)