edit

Author: anaharris-ms

.openpublishing.redirection.json

@@ -11803,6 +11803,13 @@
             "source_path_from_root": "/articles/azure-health-insights/response-info.md",
             "redirect_url": "/azure/azure-health-insights/overview",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/networking/disaster-recovery-dns-traffic-manager.md",
+            "redirect_url": "/azure/reliability/reliability-traffic-manager.md",
+            "redirect_document_id": false
         }
+
+        
     ]
 }

articles/networking/TOC.yml

@@ -20,6 +20,12 @@
       href: /azure/architecture/reference-architectures/dmz/nva-ha
     - name: Combine load balancing methods
       href: ../traffic-manager/traffic-manager-load-balancing-azure.md?toc=%2fazure%2fnetworking%2ftoc.json
+    - name: Reliability
+      items:
+      - name: Reliability in Azure DNS
+        href: ../reliability/reliability-dns.md?toc=%2fazure%2fnetworking%2ftoc.json
+      - name: Reliability in Traffic Manager
+        href: ../reliability/reliability-traffic-manager.md?toc=%2fazure%2fnetworking%2ftoc.json
     - name: Disaster recovery using Azure DNS and Traffic Manager
       href: disaster-recovery-dns-traffic-manager.md
     - name: Choose a secure network topology

articles/networking/disaster-recovery-dns-traffic-manager.md

@@ -10,10 +10,11 @@
 ---
 
 
-Disaster recovery (DR) is about recovering from high-impact events, such as natural disasters or failed deployments that result in downtime and data loss. Regardless of the cause, the best remedy for a disaster is a well-defined and tested DR plan and an application design that actively supports DR.  
+Disaster recovery (DR) is about recovering from high-impact events, such as natural disasters or failed deployments that result in downtime and data loss. Regardless of the cause, the best remedy for a disaster is a well-defined and tested DR plan and an application design that actively supports DR.  Before you begin to think about creating your disaster recovery plan, see [Recommendations for designing a disaster recovery strategy](/azure/well-architected/reliability/disaster-recovery). 
+
 
 When it comes to DR, Microsoft uses the [shared responsibility model](../business-continuity-management-program.md#shared-responsibility-model). In a shared responsibility model, Microsoft ensures that the baseline infrastructure and platform services are available. At the same time, many Azure services don't automatically replicate data or fall back from a failed region to cross-replicate to another enabled region. For those services, you are responsible for setting up a disaster recovery plan that works for your workload.  Most services that run on Azure platform as a service (PaaS) offerings provide features and guidance to support DR and you can use [service-specific features to support fast recovery](../reliability-guidance-overview.md) to help develop your DR plan.
 
-When you plan to deploy your application for DR, it's helpful to understand Azure regions and geographies. For more information, see [Azure cross-region replication](../cross-region-replication-azure.md).
+