Merge pull request #248854 from anaharris-ms/dr-rmv-nav

Reliablity: DR - Improvement DR for TOC and Content

Author: American-Dipper

.openpublishing.redirection.json

@@ -24482,9 +24482,9 @@
             "redirect_document_id": false
         },
         {
-          "source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
-          "redirect_url": "/azure/azure-functions/functions-bindings-cache",
-          "redirect_document_id": false
+            "source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
+            "redirect_url": "/azure/azure-functions/functions-bindings-cache",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-configure-authentication.md",
@@ -24516,6 +24516,21 @@
             "redirect_url": "/azure/bastion/bastion-connect-vm-ssh-linux",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/app-service/overview-disaster-recovery.md",
+            "redirect_url": "/azure/reliability/reliability-app-service",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-functions/functions-geo-disaster-recovery.md",
+            "redirect_url": "/azure/reliability/reliability-functions",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/hdinsight/hdinsight-business-continuity.md",
+            "redirect_url": "/azure/reliability/reliability-hdinsight",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/reliability/reliability-postgre-flexible.md",
             "redirect_url": "/azure/reliability/reliability-postgresql-flexible-server",
@@ -24536,8 +24551,5 @@
             "redirect_url": "/azure/orbital/overview",
             "redirect_document_id": false
         }
-
-
-        
     ]
 }

articles/app-service/breadcrumb/toc.yml

@@ -1,10 +1,14 @@
+items:
 - name: Azure
   tocHref: /azure/
   topicHref: /azure/index
   items:
   - name: App Service
     tocHref: /azure/app-service/
     topicHref: /azure/app-service/index
+  - name: App Service
+    tocHref: /azure/reliability/
+    topicHref: /azure/app-service/index
     items:
     - name: Web Apps
       tocHref: /azure/active-directory/fundamentals/

articles/app-service/overview-disaster-recovery.md

@@ -2,14 +2,14 @@
   href: index.yml
 - name: Get started
   items:
-    - name: Getting started
-      href: getting-started.md
-    - name: About App Service
-      href: overview.md
-    - name: About App Service Environments
-      href: environment/overview.md
-    - name: Compare web hosting options
-      href: /azure/architecture/guide/technology-choices/compute-decision-tree
+  - name: Getting started
+    href: getting-started.md
+  - name: About App Service
+    href: overview.md
+  - name: About App Service Environments
+    href: environment/overview.md
+  - name: Compare web hosting options
+    href: /azure/architecture/guide/technology-choices/compute-decision-tree
 - name: Quickstarts
   expanded: true
   items:
@@ -383,13 +383,13 @@
           href: app-service-sql-github-actions.md
         - name: Deploy a multi-container WordPress app
           href: tutorial-multi-container-app.md
-- name: Resiliency
+- name: Reliability
   items:
-  - name: About availability zones
-    href: ../availability-zones/migrate-app-service.md
-  - name: About disaster recovery
-    href: overview-disaster-recovery.md
-  - name: About DR backup region
+  - name: Reliability in Azure App Service
+    href: ../reliability/reliability-app-service.md?toc=/azure/app-service/toc.json&bc=/azure/app-service/breadcrumb/toc.json
+  - name: Migrate to availability zones
+    href: ../reliability/migrate-app-service.md?toc=/azure/app-service/toc.json&bc=/azure/app-service/breadcrumb/toc.json
+  - name: Move an App Service app to another region
     href: manage-disaster-recovery.md
 - name: Samples
   items:

articles/app-service/toc.yml

@@ -45,7 +45,7 @@ To complete this tutorial:
 
 ## Create two instances of a web app
 
-You'll need two instances of a web app that run in different Azure regions for this tutorial. You'll use the [region pair](../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) East US/West US as your two regions and create two empty web apps. Feel free to choose you're own regions if needed.
+You'll need two instances of a web app that run in different Azure regions for this tutorial. You'll use the [region pair](../availability-zones/cross-region-replication-azure.md#azure-paired-regions) East US/West US as your two regions and create two empty web apps. Feel free to choose you're own regions if needed.
 
 To make management and clean-up simpler, you'll use a single resource group for all resources in this tutorial. Consider using separate resource groups for each region/resource to further isolate your resources in a disaster recovery situation.
 

articles/app-service/tutorial-multi-region-app.md

@@ -12,7 +12,7 @@ A Container is the atomic unit of storage in the Azure Fluid Relay service and r
 
 You have control of the Azure region where container data is stored. During the provisioning of the Azure Fluid Relay resource, you can select the region where you want that data to be stored at-rest. All containers created in that Azure Fluid Relay resource will be stored in that region. Once selected, the region can't be changed. You'll need to create a new Azure Fluid Relay resource in another region to store data in a different region.
 
-To deliver a highly available service, the container data is replicated to another region. This data replication helps in the cases where disaster recovery is needed in face of a full regional outage. Internally, Azure Fluid Relay uses Azure Blob Storage cross-region replication to achieve that. The region where data is replicated is defined by the Azure regional pairs listed on the [Cross-region replication in Azure](../../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) page.
+To deliver a highly available service, the container data is replicated to another region. This data replication helps in the cases where disaster recovery is needed in face of a full regional outage. Internally, Azure Fluid Relay uses Azure Blob Storage cross-region replication to achieve that. The region where data is replicated is defined by the Azure regional pairs listed on the [Cross-region replication in Azure](../../availability-zones/cross-region-replication-azure.md#azure-paired-regions) page.
 
 ## Single region offering
 

articles/azure-fluid-relay/concepts/data-storage.md

@@ -354,13 +354,11 @@
           href: /security/benchmark/azure/baselines/functions-security-baseline?toc=/azure/azure-functions/TOC.json
     - name: Reliability
       items:
-        - name: Reliability overview 
+        - name: Availability zones and disaster recovery 
           href: ../reliability/reliability-functions.md?toc=/azure/azure-functions/TOC.json
-          displayName: availability zones, high-availability, zone redundancy
+          displayName: availability zones, high-availability, zone redundancy, disaster recovery
         - name: Migrate to a zone-redundant plan
-          href: ../reliability/migrate-functions.md?toc=%2fazure%2fazure-functions%2ftoc.json
-        - name: Geo-disaster recovery
-          href: functions-geo-disaster-recovery.md  
+          href: ../reliability/migrate-functions.md?toc=%2fazure%2fazure-functions%2ftoc.json 
     - name: Monitor function executions
       href: functions-monitoring.md
       displayName: App Insights, Application Insights, logs, logging

articles/azure-functions/TOC.yml

@@ -61,7 +61,7 @@ Data collection rules are available in all public regions where Log Analytics wo
 **Single region data residency** is a preview feature to enable storing customer data in a single region and is currently only available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo and the Brazil South (Sao Paulo State) Region of the Brazil Geo. Single-region residency is enabled by default in these regions.
 
 ## Data resiliency and high availability
-A rule gets created and stored in a particular region and is backed up to the [paired-region](../../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) within the same geography. The service is deployed to all three [availability zones](../../availability-zones/az-overview.md#availability-zones) within the region. For this reason, it's a *zone-redundant service*, which further increases availability.
+A rule gets created and stored in a particular region and is backed up to the [paired-region](../../availability-zones/cross-region-replication-azure.md#azure-paired-regions) within the same geography. The service is deployed to all three [availability zones](../../availability-zones/az-overview.md#availability-zones) within the region. For this reason, it's a *zone-redundant service*, which further increases availability.
 
 ## Next steps
 

articles/azure-functions/functions-geo-disaster-recovery.md

@@ -22,7 +22,7 @@ The Azure NetApp Files replication functionality provides data protection throug
 
 ## <a name="supported-region-pairs"></a>Supported cross-region replication pairs
 
-Azure NetApp Files volume replication is supported between various [Azure regional pairs](../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) and non-standard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B, and vice versa.  
+Azure NetApp Files volume replication is supported between various [Azure regional pairs](../availability-zones/cross-region-replication-azure.md#azure-paired-regions) and non-standard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B, and vice versa.  
 
 ### Azure regional pairs