Merge pull request #293247 from MicrosoftDocs/main

Publish to live, Sunday 4:00PM PST, 01/19

Author: Stacyrch140

.openpublishing.redirection.json

@@ -1782,8 +1782,8 @@
     },
     {
       "source_path_from_root": "/articles/best-practices-availability-paired-regions.md",
-      "redirect_url": "/azure/reliability/cross-region-replication-azure",
-      "redirect_document_id": true
+      "redirect_url": "/azure/reliability/regions-paired",
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/best-practices-background-jobs.md",
@@ -4994,6 +4994,11 @@
       "source_path_from_root": "/articles/virtual-network/create-vm-accelerated-networking-powershell.md",
       "redirect_url": "/azure/virtual-network/create-virtual-machine-accelerated-networking",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/reliability/cross-region-replication-azure.md",
+      "redirect_url": "/azure/reliability/regions-paired",
+      "redirect_document_id": false
     }
   ]
 }

articles/defender-for-iot/organizations/TOC.yml

@@ -330,8 +330,6 @@
         items:
         - name: HPE ProLiant DL360 Gen11
           href: appliance-catalog/hpe-proliant-dl360-gen11.md
-        - name: HPE ProLiant DL360
-          href: appliance-catalog/hpe-proliant-dl360.md
         - name: Dell PowerEdge R660
           href: appliance-catalog/dell-poweredge-r660.md
       - name: Large enterprises
@@ -368,6 +366,8 @@
           href: appliance-catalog/hpe-proliant-dl20-plus-smb.md
         - name: HPE ProLiant DL20 Gen10 Plus (4SFF)
           href: appliance-catalog/hpe-proliant-dl20-plus-enterprise.md
+        - name: HPE ProLiant DL360
+          href: appliance-catalog/hpe-proliant-dl360.md
         - name: Dell PowerEdge R350
           href: appliance-catalog/dell-poweredge-r350-e1800.md
         - name: Dell PowerEdge R340 XL (E1800)

articles/reliability/TOC.yml

@@ -8,7 +8,15 @@
     href: concept-shared-responsibility.md
   - name: Azure service incident response
     href: incident-response.md
-- name: Availability zone support
+- name: Azure regions
+  items:
+  - name: What are Azure regions?
+    href: regions-overview.md
+  - name: Paired and nonpaired regions
+    href: regions-paired.md
+  - name: Multi-region solutions in nonpaired regions
+    href: cross-region-replication-azure-no-pair.md
+- name: Availability zones
   items:
   - name: What are Azure availability zones?
     href: availability-zones-overview.md
@@ -86,12 +94,6 @@
     href: disaster-recovery-overview.md
   - name: Business continuity management program
     href: business-continuity-management-program.md
-  - name: Cross-region replication
-    items:
-    - name: Cross-region replication overview
-      href: cross-region-replication-azure.md
-    - name: Solutions for non-paired regions
-      href: cross-region-replication-azure-no-pair.md
 - name: Reliability guides by service
   items:
   - name: Overview

articles/reliability/availability-zones-baseline.md

@@ -66,7 +66,7 @@ Below are three important questions that will help you choose the correct availa
 
 #### Does your application include latency sensitive components?
 
-Azure availability zones within the same Azure region are connected by a high-performance network [with a round-trip latency of less than 2 ms](/azure/reliability/availability-zones-overview#availability-zones). 
+Azure availability zones within the same Azure region are connected by a high-performance network [with a round-trip latency of less than approximately 1.2 ms](/azure/reliability/availability-zones-overview#availability-zones).
 
 The recommended approach to achieving high availability, if low latency isn't a strict requirement, is to configure your workload with a zone redundant deployment.
 

articles/reliability/availability-zones-overview.md

@@ -4,29 +4,25 @@ description: Learn about availability zones and how they work to help you achiev
 ms.service: azure
 ms.subservice: azure-availability-zones
 ms.topic: conceptual
-ms.date: 09/20/2023
+ms.date: 11/22/2024
 ms.author: anaharris
-author: anaharris
+author: anaharris-ms
 ms.reviewer: asinghal
 ms.custom: references_regions, subject-reliability
 ---
 
-
 # What are availability zones?
 
-Many Azure regions provide *availability zones*, which are separated groups of datacenters within a region. Availability zones are close enough to have low-latency connections to other availability zones. They're connected by a high-performance network with a round-trip latency of less than 2ms. However, availability zones are far enough apart to reduce the likelihood that more than one will be affected by local outages or weather. Availability zones have independent power, cooling, and networking infrastructure. They're designed so that if one zone experiences an outage, then regional services, capacity, and high availability are supported by the remaining zones. They help your data stay synchronized and accessible when things go wrong.
+Many Azure regions provide *availability zones*, which are separated groups of datacenters within a region. Availability zones are close enough to have low-latency connections to other availability zones. They're connected by a high-performance network with a round-trip latency of less than approximately 1.2 ms. However, availability zones are far enough apart to reduce the likelihood that more than one will be affected by local outages or weather. Availability zones have independent power, cooling, and networking infrastructure. They're designed so that if one zone experiences an outage, then regional services, capacity, and high availability are supported by the remaining zones. They help your data stay synchronized and accessible when things go wrong.
 
 Datacenter locations are selected by using rigorous vulnerability risk assessment criteria. This process identifies all significant datacenter-specific risks and considers shared risks between availability zones.
 
-The following diagram shows several example Azure regions. Regions 1 and 2 support availability zones.
+The following diagram shows several example Azure regions. Regions 1 and 2 support availability zones, and regions 3 and 4 don't have availability zones.
 
 :::image type="content" source="media/regions-availability-zones.png" alt-text="Screenshot of physically separate availability zone locations within an Azure region.":::
 
 To see which regions support availability zones, see [Azure regions with availability zone support](availability-zones-region-support.md).
 
-> [!NOTE]  
-> You need to deploy two or more Virtual Machines to different availability zones in the same region to get the highest possible [SLA connectivity percentage](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).
-
 ## Zonal and zone-redundant services
 
 When you deploy into an Azure region that contains availability zones, you can use multiple availability zones together. By using multiple availability zones, you can keep separate copies of your application and data within separate physical datacenters in a large metropolitan area.
@@ -45,44 +41,39 @@ For information on service-specific reliability support using availability zones
 
 ## Physical and logical availability zones
 
-Each datacenter is assigned to a physical zone. Physical zones are mapped to logical zones in your Azure subscription, and different subscriptions might have a different mapping order. Azure subscriptions are automatically assigned their mapping at the time the subscription is created. Because of this, the zone mapping for one subscription could be different for other subscriptions. For example: Subscription A may have physical zone X mapped to logical zone 1, while subscription B has physical zone X mapped to logical zone 3, instead.
+Each datacenter is assigned to a physical zone. Physical zones are mapped to logical zones in your Azure subscription, and different subscriptions might have a different mapping order. Azure subscriptions are automatically assigned their mapping at the time the subscription is created. Because of this, the zone mapping for one subscription could be different for other subscriptions.
+
+For example: A subscription named "finance" may have physical zone X mapped to logical zone 1, while another subscription named "engineering" has physical zone X mapped to logical zone 3, instead.
 
 To understand the mapping between logical and physical zones for your subscription, use the [List Locations Azure Resource Manager API](/rest/api/resources/subscriptions/list-locations). You can use the [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/what-is-azure-powershell) to retrieve the information from the API.
 
 # [CLI](#tab/azure-cli)
 
 ```azurecli
-az rest --method get --uri '/subscriptions/{subscriptionId}/locations?api-version=2022-12-01' --query 'value'
+az rest --method get \
+    --uri '/subscriptions/{subscriptionId}/locations?api-version=2022-12-01' \
+    --query 'value[?availabilityZoneMappings != `null`].{displayName: displayName, name: name, availabilityZoneMappings: availabilityZoneMappings}'
 ```
+
 # [PowerShell](#tab/azure-powershell)
 
 ```azurepowershell
 $subscriptionId = (Get-AzContext).Subscription.ID
 $response = Invoke-AzRestMethod -Method GET -Path "/subscriptions/$subscriptionId/locations?api-version=2022-12-01"
 $locations = ($response.Content | ConvertFrom-Json).value
 ```
+
 ---
 
 ## Availability zones and Azure updates
 
-Microsoft aims to deploy updates to Azure services to a single availability zone at a time. This approach reduces the impact that updates might have on an active workload, because the workload can continue to run in other zones while the update is in process. You need to run your workload across multiple zones to take advantage of this benefit. For more information about how Azure deploys updates, see [Advancing safe deployment practices](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/).
-
-
-## Paired and unpaired regions
-
-Many regions also have a [*paired region*](./cross-region-replication-azure.md#azure-paired-regions). Paired regions support certain types of multi-region deployment approaches. Some newer regions have [multiple availability zones and don't have a paired region](./cross-region-replication-azure.md#regions-with-availability-zones-and-no-region-pair). You can still deploy multi-region solutions into these regions, but the approaches you use might be different.
-
-## Shared responsibility model
-
-The [shared responsibility model](./concept-shared-responsibility.md) describes how responsibilities are divided between the cloud provider (Microsoft) and you. Depending on the type of services you use, you might take on more or less responsibility for operating the service.
-
-Microsoft provides availability zones and regions to give you flexibility in how you design your solution to meet your requirements. When you use managed services, Microsoft takes on more of the management responsibilities for your resources, which might even include data replication, failover, failback, and other tasks related to operating a distributed system.
+For each region, Microsoft aims to deploy updates to Azure services within a single availability zone at a time. This approach reduces the impact that updates might have on an active workload, because the workload can continue to run in other zones while the update is in process. You need to run your workload across multiple zones to take advantage of this benefit. For more information about how Azure deploys updates, see [Advancing safe deployment practices](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/).
 
 ## Availability zone architectural guidance
 
 To achieve more reliable workloads:
 
-- Production workloads should be configured to use availability zones if the region they are in supports availability zones.
+- Production workloads should be configured to use multiple availability zones if the region they are in supports availability zones.
 - For mission-critical workloads, you should consider a solution that is *both* multi-region and multi-zone.
 
 For more detailed information on how to use regions and availability zones in a solution architecture, see [Recommendations for using availability zones and regions](/azure/well-architected/resiliency/regions-availability-zones).
@@ -96,8 +87,6 @@ For more detailed information on how to use regions and availability zones in a
 
 - [Availability zone migration guidance](availability-zones-migration-overview.md)
 
-- [Availability of service by category](availability-service-by-category.md)
-
 - [Microsoft commitment to expand Azure availability zones to more regions](https://azure.microsoft.com/blog/our-commitment-to-expand-azure-availability-zones-to-more-regions/)
 
-- [Build solutions for high availability using availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability)
+- [Recommendations for using availability zones and regions](/azure/well-architected/reliability/regions-availability-zones)

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

@@ -4,7 +4,7 @@ description: Learn which Azure regions offer availability zone support
 ms.service: azure
 ms.subservice: azure-availability-zones
 ms.topic: conceptual
-ms.date: 11/20/2024
+ms.date: 01/16/2025
 ms.author: anaharris
 author: anaharris-ms
 ms.custom: references_regions, subject-reliability
@@ -32,6 +32,9 @@ The following regions currently support availability zones:
 
 \* To learn more about availability zones and available services support in these regions, contact your Microsoft sales or customer representative. For upcoming regions that support availability zones, see [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/).
 
+> [!NOTE]
+> Even when a region provides availability zones, it's possible that some services might not support them in that region. Refer to the [Azure service reliability guides](./overview-reliability-guidance.md) to learn about region support for availability zone-enabled services.
+
 ## Next steps
 
 > [!div class="nextstepaction"]

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

@@ -4,7 +4,7 @@ description: Learn which Azure services offer availability zone support.
 ms.service: azure
 ms.subservice: azure-availability-zones
 ms.topic: conceptual
-ms.date: 12/10/2024
+ms.date: 01/16/2025
 ms.author: anaharris
 author: anaharris-ms
 ms.custom: references_regions, subject-reliability
@@ -18,14 +18,13 @@ For more information on availability zones and regions, see [What are Azure regi
 
 Azure is continually expanding the number of services that support availability zones, including zonal and zone-redundant offerings.
 
-
 ## Types of availability zone support
 
-Azure services can provide two types of availability zone support: *zonal* and *zone-redundant*. Each service might support one or both types. When designing your reliability strategy, make sure that you understand which availability zone types are supported in each service of your workload. 
+Azure services can provide two types of availability zone support: *zone-redundant* and *zonal*. Each service might support one or both types. When designing your reliability strategy, make sure that you understand which availability zone types are supported in each service of your workload. 
 
-- **Zonal services**: A resource can be deployed to a specific, self-selected availability zone to achieve more stringent latency or performance requirements. Resiliency is self-architected by replicating applications and data to one or more zones within the region. Resources are aligned to a selected zone. For example, virtual machines, managed disks, or standard IP addresses can be aligned to a same zone, which allows for increased resiliency by having multiple instances of resources deployed to different zones.
+- **Zone-redundant services**: Zone-redundant resources are replicated or distributed across multiple availability zones automatically. For example, zone-redundant data services replicate the data across multiple zones so that a failure in one zone doesn't affect the high availability of the data. For some services you can select the set of zones that your resource uses, while in other services Microsoft selects the zones.
 
-- **Zone-redundant services**: Resources are replicated or distributed across zones automatically. For example, zone-redundant services replicate the data across multiple zones so that a failure in one zone doesn't affect the high availability of the data. 
+- **Zonal services**: A resource can be deployed to a single, self-selected availability zone to achieve more stringent latency or performance requirements. For example, virtual machines, managed disks, and standard IP addresses can be deployed zonally to the same zone. To achieve resiliency with zonal services, you need to design an architecture with separate resources in multiple availability zones within the region, but Microsoft doesn't manage the process for you.
 
 Some services don't use availability zones until you configure them to do so. If you don't explicitly configure a service for availability zone support, it's called a *non-zonal* or *regional* deployment. Resources configured in this way might be placed in any availability zone in the region, and might be moved. If any availability zone in the region experiences an outage, non-zonal resources might be in the affected zone and could experience downtime.