Merge pull request #293492 from anaharris-ms/rel-overview

Reliability - Overview

Author: JillGrant615

articles/expressroute/design-architecture-for-resiliency.md

@@ -50,7 +50,7 @@ Standard resiliency in ExpressRoute is a single circuit with two connections con
 
 [Azure regions](/azure/cloud-adoption-framework/ready/azure-setup-guide/regions) are an integral part of your ExpressRoute design and resiliency strategy. These regions are geographical locations of data centers that host Azure services. Regions are interconnected through a dedicated low-latency network and are designed to be highly available, fault-tolerant, and scalable.
 
-Azure offers several features to ensure regional resiliency. One such feature is [availability zones](../reliability/availability-zones-overview.md). Availability zones protect applications and data from data center failures by spanning across multiple physical locations within a region. Regions and availability zones are central to your application design and resiliency strategy. By utilizing availability zones, you can achieve higher availability and resilience in your deployments. For more information, see [Regions & availability zones](../reliability/overview.md#regions-and-availability-zones).
+Azure offers several features to ensure regional resiliency. One such feature is [availability zones](../reliability/availability-zones-overview.md). Availability zones protect applications and data from data center failures by spanning across multiple physical locations within a region. Regions and availability zones are central to your application design and resiliency strategy. By utilizing availability zones, you can achieve higher availability and resilience in your deployments. For more information, see [Regions & availability zones](../reliability/overview.md).
 
 We recommend deploying your [ExpressRoute Virtual Network Gateways](expressroute-about-virtual-network-gateways.md) as zone redundant across availability zones within a region. These availability zones are separate physical locations with independent infrastructure (power, cooling, and networking). The purpose is to protect your on-premises network connectivity to Azure from zone level failures. [Zone-redundant ExpressRoute gateways](../vpn-gateway/about-zone-redundant-vnet-gateways.md?toc=%2Fazure%2Fexpressroute%2Ftoc.json) provide resiliency, scalability, and higher availability for accessing mission-critical services on Azure. 
 

articles/reliability/TOC.yml

@@ -1,6 +1,6 @@
 - name: Azure reliability documentation
   href: index.yml
-- name: What is reliability?
+- name: Overview
   href: overview.md
 - name: Reliability fundamentals
   items:

articles/reliability/availability-zones-service-support.md

@@ -37,10 +37,7 @@ Some Azure services don't support availability zones because they are:
 
 - Available across multiple Azure regions within a geographic area, or even across all Azure regions globally.
 - Resilient to zone-wide outages.
-- Resilient to region-wide outages. 
-
-For a complete list of always-available services, also called non-regional services, in Azure, see [Products available by region](https://azure.microsoft.com/global-infrastructure/services/).
-
+- Resilient to region-wide outages.
 For more information on older-generation virtual machines, see [Previous generations of virtual machine sizes](/azure/virtual-machines/sizes-previous-gen).
 
 ## Azure services with availability zone support

articles/reliability/overview-reliability-guidance.md

@@ -4,15 +4,22 @@ description: Reliability guides for Microsoft Azure products and services. View
 author: anaharris-ms
 ms.service: azure
 ms.topic: reliability-article
-ms.date: 12/03/2024
+ms.date: 01/28/2025
 ms.author: anaharris
 ms.custom: subject-reliability
 ms.subservice: azure-reliability
 ---
 
-# Azure service reliability guides
+# Reliability guides by service
+
+While Azure provides a set of reliability features, the resiliency of your workload is a [shared responsibility between you and Microsoft](./concept-shared-responsibility.md) and depends on how you have designed your business continuity plan to define your expectations for reliability. For this reason, it's important that you understand the reliability features of each service you use, and how to best implement them in your workload. This document provides links to the reliability guidance for each Azure service, detailing how each service supports your reliability requirements through its features and design.
+
+Each service guide generally contains information on how the service supports:
+
+- *Availability zones* such as zonal and zone-redundant deployment options, traffic routing and data replication between zones, what happens if a zone experiences an outage, failback, and how to configure your resources for availability zone support.
+- *Multi-region support* such as how to configure multi-region or geo-disaster support, traffic routing and data replication between regions, region-down experience, failover and failback support, alternative multi-region support.
+- *Backup support* such as who controls backups, where they are stored, how they can be recovered, and whether they are accessible only within a region or across regions.
 
-Below is a list of Azure service reliability guides, organized by service category.
 
 >[!NOTE]
 >Some service documents are in the process of, or are not yet updated into a single reliability guide format. These may contain more than one document that references reliability guidance.