Skip to content

Commit 62f7cc5

Browse files
authored
Merge pull request #295813 from v-albemi/reliability-deployment-environments
Freshness Edit: Azure Deployment Environments Set 1
2 parents cd8f724 + 01cffb5 commit 62f7cc5

File tree

2 files changed

+35
-35
lines changed

2 files changed

+35
-35
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/07/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.
Lines changed: 32 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,68 @@
11
---
22
title: Reliability and availability in Azure Deployment Environments
3-
description: Learn how Azure Deployment Environments supports disaster recovery. Understand reliability and availability within a single region and across regions.
3+
description: Learn how Azure Deployment Environments supports reliability. Understand availability zone support within a single region and cross-region disaster recovery.
44
ms.service: azure-deployment-environments
55
ms.topic: reliability-article
66
ms.author: rosemalcolm
77
author: RoseHJM
8-
ms.date: 12/30/2023
8+
ms.date: 03/07/2025
99
ms.custom: subject-reliability, references_regions
10+
11+
#customer intent: As a platform engineer, I want to get information about reliability in Azure Deployment Environments so that I can improve the reliability of my workloads.
1012
---
1113

1214
# Reliability in Azure Deployment Environments
1315

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).
16+
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).
1517

1618
## Availability zone support
1719

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

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

23-
Regions supported:
24-
- West US 2
25-
- South Central US
26-
- UK South
27-
- West Europe
28-
- East US
24+
The following regions support both Deployment Environments and availability zones:
2925
- Australia East
26+
- Brazil South
27+
- Canada Central
28+
- Central India
29+
- Central US
30+
- East Asia
31+
- East US
3032
- East US 2
31-
- North Europe
32-
- West US 3
33+
- Germany West Central
34+
- Italy North
3335
- Japan East
34-
- East Asia
35-
- Central India
3636
- Korea Central
37-
- Canada Central
38-
39-
For more detailed information on availability zones in Azure, see [Regions and availability zones](../reliability/availability-zones-overview.md).
37+
- North Europe
38+
- South Africa North
39+
- South Central US
40+
- Southeast Asia
41+
- Sweden Central
42+
- Switzerland North
43+
- UK South
44+
- West Europe
45+
- West US 2
46+
- West US 3
4047

4148
## Cross-region disaster recovery and business continuity
4249

4350
[!INCLUDE [introduction to disaster recovery](../reliability/includes/reliability-disaster-recovery-description-include.md)]
4451

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

47-
- Dev center
48-
- Project
49-
- Catalog
54+
- Dev centers
55+
- Projects
56+
- Catalogs
5057
- Catalog items
51-
- Dev center environment type
52-
- Project environment type
58+
- Dev center environment types
59+
- Project environment types
5360
- Environments
5461

62+
For more information, see [Azure to Azure disaster recovery architecture](../site-recovery/azure-to-azure-architecture.md).
5563

56-
57-
For more information on Azure disaster recovery architecture, see [Azure to Azure disaster recovery architecture](../site-recovery/azure-to-azure-architecture.md).
58-
59-
## Next steps
64+
## Related content
6065

6166
- To learn more about how Azure supports reliability, see [Azure reliability](/azure/reliability).
6267
- To learn more about Deployment Environments resources, see [Azure Deployment Environments key concepts](../deployment-environments/concept-environments-key-concepts.md).
63-
- To get started with Deployment Environments, see [Quickstart: Create and configure the Azure Deployment Environments dev center](../deployment-environments/quickstart-create-and-configure-devcenter.md).
68+
- To get started with Deployment Environments, see [Quickstart: Configure Azure Deployment Environments](../deployment-environments/quickstart-create-and-configure-devcenter.md).

0 commit comments

Comments
 (0)