edit

anaharris-ms · anaharris-ms · commit d8e7d4002a3b · 2025-01-28T17:10:06.000-05:00
diff --git a/articles/reliability/overview-reliability-guidance.md b/articles/reliability/overview-reliability-guidance.md
@@ -4,7 +4,7 @@ description: Reliability guides for Microsoft Azure products and services. View
 author: anaharris-ms
 ms.service: azure
 ms.topic: reliability-article
-ms.date: 01/23/2025
+ms.date: 01/28/2025
 ms.author: anaharris
 ms.custom: subject-reliability
 ms.subservice: azure-reliability
@@ -20,22 +20,9 @@ Each service guide generally contains information on how the service supports:
 - *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.
 
-There are two types of Azure services in Azure: *non-regional* and *regional*:
-
-- **Non-regional services** are services that are deployed to two or more regions. If there's a regional failure, the instance of the service in a healthy region continues servicing customers. Certain non-regional services enable customers to specify the region where the underlying virtual machine (VM) on which service runs will be deployed. For example, [Azure Virtual Desktop](https://azure.microsoft.com/services/virtual-desktop/) enables customers to specify the region location where the VM resides. All Azure services that store customer data allow the customer to specify the specific regions in which their data will be stored. The exception is [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory/), which has geo placement (such as Europe or North America). For more information about data storage residency, see the [Data residency map](https://azure.microsoft.com/global-infrastructure/data-residency/).
-
-
-    >[!NOTE]
-    >If you need to understand dependencies between Azure services to help better architect your applications and services, you can request the **Azure service dependency documentation** by contacting your Microsoft sales or customer representative. This document lists the dependencies for Azure services, including dependencies on any common major internal services such as control plane services. To obtain this documentation, you must be a Microsoft customer and have the appropriate non-disclosure agreement (NDA) with Microsoft.
-
-- **Regional services** are services that are deployed in a specific region. Many regional services provide resiliency support through availability zones and multi-region support.  The reliability of regional services is determined by the service's architecture and the design of your workload, and so is a [shared responsibility between you and Microsoft](./concept-shared-responsibility.md).  For example, if you deploy a regional service in a region that has availability zones, you can design your workload to be resilient to zone failures by deploying across multiple zones. If you deploy a regional service in a region that doesn't have availability zones, you can design your workload to be resilient to region failures by deploying across multiple regions.
-
-
 This document provides links to the reliability guidance for each Azure service, detailing how each services supports or does not support specific reliability features. The guidance includes information about the service's architecture, availability, and disaster recovery options.
 
 
-
-
 >[!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.
 
diff --git a/articles/reliability/overview.md b/articles/reliability/overview.md
@@ -3,7 +3,7 @@ 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/27/2025
+ms.date: 01/28/2025
 ms.author: anaharris
 ms.service: azure
 ms.custom: subject-reliability
diff --git a/articles/reliability/regions-overview.md b/articles/reliability/regions-overview.md
@@ -59,6 +59,21 @@ It's common to use multiple Azure regions, paired or nonpaired, when you design
 
 When you select regions that are geographically far apart, the latency of network connections between those regions increases. Latency can affect how you design a multi-region solution, and it can restrict the types of geo-replication and geo-redundancy you can use. For more information, see [Recommendations for using availability zones and regions](/azure/well-architected/reliability/regions-availability-zones).
 
+## Azure regions and service deployment types
+
+Although most Azure services are deployed to a specific regions or regions, there are some services that aren't tied to any specific region. It's important to take those services into account when you design your solutions and business continuity plan.
+
+There are two types of Azure services in Azure: *non-regional* or always-available and *regional*:
+
+- **Non-regional (Always available) services** are services that are deployed to two or more regions. If there's a regional failure, the instance of the service in a healthy region continues servicing customers. Certain non-regional services enable customers to specify the region where the underlying virtual machine (VM) on which service runs will be deployed. For example, [Azure Virtual Desktop](https://azure.microsoft.com/services/virtual-desktop/) enables customers to specify the region location where the VM resides. All Azure services that store customer data allow the customer to specify the specific regions in which their data will be stored. The exception is [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory/), which has geo placement (such as Europe or North America). For more information about data storage residency, see the [Data residency map](https://azure.microsoft.com/global-infrastructure/data-residency/).
+
+
+    >[!NOTE]
+    >If you need to understand dependencies between Azure services to help better architect your applications and services, you can request the **Azure service dependency documentation** by contacting your Microsoft sales or customer representative. This document lists the dependencies for Azure services, including dependencies on any common major internal services such as control plane services. To obtain this documentation, you must be a Microsoft customer and have the appropriate non-disclosure agreement (NDA) with Microsoft.
+
+- **Regional services** are services that are deployed in a specific region. Many regional services provide resiliency support through availability zones and multi-region support.  The reliability of regional services is determined by the service's architecture and the design of your workload, and so is a [shared responsibility between you and Microsoft](./concept-shared-responsibility.md).  For example, if you deploy a regional service in a region that has availability zones, you can design your workload to be resilient to zone failures by deploying across multiple zones. If you deploy a regional service in a region that doesn't have availability zones, you can design your workload to be resilient to region failures by deploying across multiple regions.
+
+
 ## Related resources
 
 For more information on the Azure services available in each region, see [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region).
