Skip to content

Commit 4770198

Browse files
authored
Merge pull request #310295 from RoseHJM/ade-reliability
ADE - new reliability article
2 parents c1fed98 + af26bdb commit 4770198

2 files changed

Lines changed: 43 additions & 2 deletions

File tree

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Reliability and Availability in Azure Deployment Environments
3+
description: Learn how Azure Deployment Environments ensure reliability with availability zones and disaster recovery strategies. Discover best practices for resiliency.
4+
#customer intent: As a cloud architect, I want to understand how availability zones support reliability in Azure Deployment Environments so that I can ensure high availability for my applications.
5+
author: RoseHJM
6+
ms.author: rosemalcolm
7+
ms.reviewer: rosemalcolm
8+
ms.date: 01/08/2026
9+
ms.topic: concept-article
10+
---
11+
12+
# Reliability and availability zones in Azure Deployment Environments
13+
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/reliability/).
14+
15+
## Availability zone support
16+
[Availability zones](/azure/reliability/availability-zones-overview?tabs=azure-cli) are physically separate groups of datacenters within an Azure region. When one zone fails, services can fail over to one of the remaining zones. To improve the availability of your applications, architect your solutions to use multiple availability zones within a region. For more information about Azure regions where availability zones are available, see [Azure regions list](../reliability/regions-list.md).
17+
18+
When you deploy Azure Deployment Environments in a region that supports availability zones, the environments automatically support availability zones for all resources. Check the regions that support Deployment Environments by using the [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=deployment-environments) page.
19+
20+
21+
## Cross-region disaster recovery and business continuity
22+
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).
23+
24+
For DR, Microsoft uses the [shared responsibility model](/azure/reliability/concept-shared-responsibility). 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](/azure/reliability/overview-reliability-guidance) to help develop your DR plan.
25+
26+
You can replicate the following Deployment Environments resources in an alternate region to prevent data loss if a cross-region failover occurs:
27+
28+
- Dev centers
29+
- Projects
30+
- Catalogs
31+
- Catalog items
32+
- Dev center environment types
33+
- Project environment types
34+
- Environments
35+
36+
For more information, see [Azure to Azure disaster recovery architecture](/azure/site-recovery/azure-to-azure-architecture).
37+
38+
## Related content
39+
- To learn more about how Azure supports reliability, see [Azure reliability](/azure/well-architected/reliability/).
40+
- To learn more about Deployment Environments resources, see [Azure Deployment Environments key concepts](/azure/deployment-environments/concept-environments-key-concepts).
41+
- To get started with Deployment Environments, see [Quickstart: Configure Azure Deployment Environments](quickstart-create-and-configure-devcenter.md).

articles/deployment-environments/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ items:
2525
- name: Best practices for designing catalogs
2626
href: best-practice-catalog-structure.md
2727
- name: Reliability in Azure Deployment Environments
28-
href: ../reliability/reliability-deployment-environments.md?toc=/azure/deployment-environments/toc.json&bc=/azure/deployment-environments/breadcrumb/toc.json
28+
href: concept-reliability-deployment-environments.md
2929
- name: Azure role-based access control
3030
href: concept-deployment-environments-role-based-access-control.md
3131
- name: Configure resources
@@ -83,8 +83,8 @@ items:
8383
- name: Security
8484
items:
8585
- name: Grant access to Azure Deployment Environments
86-
displayName: role-based access control, RBAC, permissions, roles, access, manage
8786
href: how-to-manage-deployment-environments-access.md
87+
displayName: role-based access control, RBAC, permissions, roles, access, manage
8888
- name: Authenticate to REST APIs
8989
href: how-to-authenticate.md
9090
- name: Automate with CI/CD

0 commit comments

Comments
 (0)