Merge pull request #293640 from anaharris-ms/reliability-minor-0125

Reliabilty Hub - Minor changes

Author: JamesJBarnett

.openpublishing.redirection.json

@@ -5203,6 +5203,11 @@
       "source_path_from_root": "/articles/reliability/disaster-recovery-overview.md",
       "redirect_url": "/azure/reliability/concept-business-continuity-high-availability-disaster-recovery",
       "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",
+      "redirect_document_id": false
     }
   ]
 }

articles/reliability/TOC.yml

@@ -8,17 +8,15 @@
     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?
     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
+    href: regions-multi-region-nonpaired.md
+- name: Azure availability zones
   items:
   - name: What are Azure availability zones?
     href: availability-zones-overview.md
@@ -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/includes/reliability-transient-faults-description-include.md

@@ -10,7 +10,7 @@ metadata:
   ms.author: anaharris
   author: anaharris-ms
   ms.service: azure
-  ms.date: 07/12/2022
+  ms.date: 01/28/2025
   ms.subservice: azure-reliability
 
 landingContent: 
@@ -21,10 +21,28 @@ landingContent:
         links:
           - text: Azure reliability overview
             url: overview.md
-          - text: Azure reliability guidance by service
-            url: reliability-guidance-overview.md
   # Card
-  - title: Availability zone support
+  - title: Reliability fundamentals
+    linkLists:
+      - linkListType: concept
+        links:
+          - text: Business continuity, high availability, and disaster recovery
+            url: concept-business-continuity-high-availability-disaster-recovery.md
+          - text: Shared responsibility for resiliency
+            url: concept-shared-responsibility.md
+  # Card
+  - title: Azure regions
+    linkLists:
+      - linkListType: concept
+        links:
+          - text: What are Azure regions?
+            url: concept-business-continuity-high-availability-disaster-recovery.md
+          - text: Azure region pairs and nonpaired regions
+            url: concept-shared-responsibility.md
+          - text: Multi-region solutions in nonpaired regions
+            url: regions-multi-region-nonpaired.md
+  # Card
+  - title: Azure availability zones
     linkLists:
       - linkListType: concept
         links:
@@ -41,14 +59,9 @@ landingContent:
           - text: Migrate to availability zone support
             url: availability-zones-migration-overview.md
   # Card
-  - title: Disaster recovery
+  - title: Reliability guides by service
     linkLists:
-      - linkListType: concept
+      - linkListType: overview
         links:
-          - text: Business continuity
-            url: concept-business-continuity-high-availability-disaster-recovery.md
-          - text: Cross-region replication
-            url: cross-region-replication-azure.md
-          - text: Cross-region replication for nonpaired regions
-            url: cross-region-replication-azure.md
-  
+          - text: Reliability guidance for Azure services
+            url: overview-reliability-guidance.md

articles/reliability/index.yml

@@ -32,8 +32,6 @@ The required level of reliability for any Azure solution depends on several cons
 
 Building reliability systems on Azure is a **shared responsibility**. Microsoft is responsible for the reliability of the cloud platform, including its global network and data centers. Azure customers and partners are responsible for the resilience of their cloud applications, using architectural best practices based on the requirements of each workload. While Azure continually strives for highest possible resiliency in SLA for the cloud platform, you must define your own target SLAs for each workload in your solution. An SLA makes it possible to evaluate whether the architecture meets the business requirements. As you strive for higher percentages of SLA guaranteed uptime, the cost and complexity to achieve that level of availability grows. An uptime of 99.99 percent translates to about five minutes of total downtime per month. Is it worth the more complexity and cost to reach that percentage? The answer depends on the individual business requirements. While deciding final SLA commitments, understand Microsoft’s supported SLAs. Each Azure service has its own SLA. 
 
-:::image type="content" source="media/shared-responsibility.svg" alt-text="Diagram showing the shared responsibility model for Azure business continuity.":::
-
 In the traditional on-premises model, the entire responsibility of managing, from the hardware for compute, storage and networking to the application, falls on you. You must plan for various types of failures and how to deal with them by creating a [business continuity strategy](./concept-business-continuity-high-availability-disaster-recovery.md). With IaaS, the cloud service provider is responsible for the core infrastructure resiliency, including storage, networking, and compute. As you move from IaaS to PaaS and then to SaaS, you’ll find that you’re responsible for less and the cloud service provider is responsible for more.  
 
 For more information on Reliability principles, see [Well-architected Framework Reliability documentation](/azure/well-architected/resiliency/).   

articles/reliability/media/shared-responsibility-model.png

@@ -22,7 +22,7 @@ The reliability guidance for most of these capabilities are covered by the [Micr
 
 ## Transient faults
 
-[!INCLUDE[introduction to transient faults](includes/reliability-transient-faults-description-include.md)]
+[!INCLUDE[introduction to transient faults](includes/reliability-transient-fault-description-include.md)]
 
 If a transient fault occurs during ingestion of emissions data, you must manually trigger the job again. You can monitor the ingestion job from the Microsoft Fabric monitoring hub.