edit

Author: anaharris-ms

.openpublishing.redirection.json

@@ -5114,11 +5114,6 @@
       "redirect_url": "/azure/reliability/concept-business-continuity-high-availability-disaster-recovery",
       "redirect_document_id": false
     },
-    {
-      "source_path_from_root": "/articles/reliability/overview.md",
-      "redirect_url": "/azure/reliability/concept-reliability",
-      "redirect_document_id": false
-    },
     {
       "source_path_from_root": "/articles/reliability/cross-region-replication-azure-no-pair.md",
       "redirect_url": "/azure/reliability/regions-multi-region-nonpaired",

articles/reliability/TOC.yml

@@ -1,15 +1,13 @@
 - name: Azure reliability documentation
   href: index.yml
 - name: Overview
-  href: concept-reliability.md
+  href: overview.md
 - name: Reliability fundamentals
   items:
   - name: Business continuity, high availability, and disaster recovery
     href: concept-business-continuity-high-availability-disaster-recovery.md
   - name: Shared responsibility for resiliency
     href: concept-shared-responsibility.md
-  - name: Azure service incident response
-    href: incident-response.md
 - name: Azure regions
   items:
   - name: What are Azure regions?
@@ -26,12 +24,12 @@
     href: availability-zones-service-support.md
   - name: Regions with availability zone support
     href: availability-zones-region-support.md
-  - name: Azure availability zone migration baseline
-    href: availability-zones-baseline.md
   - name: Migrate to availability zone support
     items:
     - name: Overview
       href: availability-zones-migration-overview.md
+    - name: Azure availability zone migration baseline
+      href: availability-zones-baseline.md
     - name: Migration guides by service
       items:
       - name: Azure API Management
@@ -424,6 +422,8 @@
       href: ../azure-signalr/signalr-concept-disaster-recovery.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
 - name: Resources
   items:
+  - name: Azure service incident response
+    href: incident-response.md
   - name: Service availability
     items:
     - name: Service availability by region

articles/reliability/concept-reliability.md renamed to articles/reliability/overview.md

@@ -1,25 +1,57 @@
 ---
-title: Overview of reliability
-description: Get an overview of reliability in Azure, including platform capabilities, the shared responsibility model, and how each Azure service supports reliability.
+title: Azure reliability documentation
+description: Overview of Azure reliability documentation, including platform capabilities, the shared responsibility model, and how each Azure service supports reliability.
 author: anaharris-ms
 ms.topic: overview
-ms.date: 01/23/2025
+ms.date: 01/27/2025
 ms.author: anaharris
 ms.service: azure
 ms.custom: subject-reliability
 CustomerIntent: As a cloud architect/engineer, I want to learn about Azure Reliability.
 ---
 
-# What is reliability?
+# Azure reliability documentation
+
+The Azure reliability documentation provides information on what reliability means in a cloud platform, how Azure cloud supports reliability, and in what way each Azure service can be configured to support a reliable solution. 
+
+The documentation is organized into the following sections:
+
+- **Reliability fundamentals.** Learn about the concepts of reliability, business continuity, high availability, and disaster recovery. Understand how shared responsibility works between Microsoft and you.
+- **Azure reliability guides by service.** Learn how each Azure service supports reliability, including availability zones, multi-region support, and backup support.
+- **Azure regions.** Learn about Azure regions, paired and nonpaired regions, and the list of services that are deployed to Azure regions.
+- **Azure availability zones.** Learn about availability zones, including how they support high availability and disaster recovery, and which Azure services and regions supports availability zones.
+
+## What is reliability?
 
 Reliability refers to the ability of a workload to perform consistently at the expected level, and in accordance with business continuity requirements. Reliability is a key concept in cloud computing. In Azure, reliability is achieved through a combination of factors, including the design of the platform itself, its services, the architecture of your applications, and the implementation of best practices.
 
-A key approach to achieve reliability in a workload is *resiliency*, which is a workload's ability to withstand and recover from faults and outages. Azure offers a number of resiliency features such as availability zones, multi-region support, data replication, and backup and restore capabilities. These features must be considered when designing a workload to meet its business continuity requirements. The Azure reliability documentation provides detailed information about these platform capabilities and how Azure services can be used to implement your resiliency needs.
+A key approach to achieve reliability in a workload is *resiliency*, which is a workload's ability to withstand and recover from faults and outages. Azure offers a number of resiliency features such as availability zones, multi-region support, data replication, and backup and restore capabilities. These features must be considered when designing a workload to meet its business continuity requirements. 
+
+he documentation is organized into the following sections:
+
+
+## Azure reliability guides by service
+
+Each Azure service has its own unique reliability characteristics. Azure provides a set of service-specific reliability guides that can help you design and implement a reliable workload, and the guidance can help you understand how to best use the service to meet your business needs. Each guide may contain the following sections, depending on which reliability features it supports:
+
+Each reliability service guide generally contains information on how the service supports a range of reliability capabilities, including:
+
+- *Availability zones* such as zonal or zone-redundant deployment options, traffic routing and data replication between zones, zone-down experience, capacity planning, failback, and how to configure for availability zone support.
+- *Multi-region support* such as how to configure multi-region or geo-disaster recovery support, traffic routing and data replication between regions, region-down experience, and failover and failback support. For some services that don't have native multi-region support, the guides present alternative multi-region deployment approaches to consider.
+- *Backup support* such as Microsoft-controlled and customer-controlled backup capabilities, where they are stored, how they can be recovered, and whether they are accessible only within a region or across regions.
+
+For more information and a list of reliability service guides, see [Reliability guides by service](./reliability-guidance-overview.md).
+
 
 > [!TIP]
 > Reliability also incorporates other elements of your solution design too, including how you deploy changes safely, how you manage your performance to avoid downtime due to high load, and how you test and validate each part of your solution. To learn more, see the [Azure Well-Architected Framework](/azure/well-architected).
 
-## Business continuity, high availability, and disaster recovery
+
+## Reliability fundamentals
+
+The reliability fundamentals section provides an overview of the key concepts and principles that underpin reliability in Azure. 
+
+### Business continuity, high availability, and disaster recovery
 
 Business continuity planning can be understood as the ongoing process of risk management through high availability and disaster recovery design. 
 
@@ -33,7 +65,7 @@ When considering business continuity, it's important to understand the following
 
 For more information on business continuity and business continuity planning through high availability and disaster recovery design, see [What are business continuity, high availability, and disaster recovery?](./concept-business-continuity-high-availability-disaster-recovery.md)
 
-## Resiliency and shared responsibility
+### Shared responsibility
 
 Resiliency defines a workload's ability to automatically self-correct and recover from various forms of failures or outages. Azure services are built to be resilient to many common failures, and each product provides a service level agreement (SLA) that describes the uptime you can expect. However, the overall resiliency of your workload depends on how you have designed your solution to meet your business needs. Some business continuity plans may consider certain failure risks to be unimportant, while others may consider them critical.
 
@@ -58,17 +90,7 @@ Many Azure regions provide availability zones, which are separated groups of dat
 - To learn about how each Azure service supports availability zones, see [Azure services with availability zone support](./availability-zones-service-support.md)
 - To learn how to approach a migration to availability zone support, see [Azure availability zone migration baseline](availability-zones-baseline.md).
 
-## Azure reliability guides by service
-
-Each Azure service has its own unique reliability characteristics. Azure provides a set of service-specific reliability guides that can help you design and implement a reliable workload, and the guidance can help you understand how to best use the service to meet your business needs. Each guide may contain the following sections, depending on which reliability features it supports:
-
-Each reliability service guide generally contains information on how the service supports a range of reliability capabilities, including:
-
-- *Availability zones* such as zonal or zone-redundant deployment options, traffic routing and data replication between zones, zone-down experience, capacity planning, failback, and how to configure for availability zone support.
-- *Multi-region support* such as how to configure multi-region or geo-disaster recovery support, traffic routing and data replication between regions, region-down experience, and failover and failback support. For some services that don't have native multi-region support, the guides present alternative multi-region deployment approaches to consider.
-- *Backup support* such as Microsoft-controlled and customer-controlled backup capabilities, where they are stored, how they can be recovered, and whether they are accessible only within a region or across regions.
 
-For more information and a list of reliability service guides, see [Reliability guides by service](./reliability-guidance-overview.md).
 
 
 ## Related content