edit

Author: anaharris-ms

.openpublishing.redirection.json

@@ -11806,7 +11806,7 @@
         },
         {
             "source_path_from_root": "/articles/networking/disaster-recovery-dns-traffic-manager.md",
-            "redirect_url": "/azure/reliability/reliability-traffic-manager.md",
+            "redirect_url": "/azure/reliability/reliability-traffic-manager",
             "redirect_document_id": false
         }
 

articles/networking/TOC.yml

@@ -26,8 +26,6 @@
         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
       href: secure-network-topology.md
     - name: Choose a secure application delivery service

articles/reliability/reliability-dns.md

@@ -4,7 +4,7 @@ description: Learn about reliability in Azure DNS.
 author: anaharris-ms
 ms.author: anaharris
 ms.topic: overview
-ms.custom: subject-reliability, references.regions
+ms.custom: subject-reliability, references-regions
 ms.service: traffic-manager
 ms.date: 02/02/2024
 ---
@@ -50,7 +50,7 @@ This article focuses specifically on Azure DNS disaster recovery planning.
 
 The Azure DNS manual failover solution for disaster recovery uses the standard DNS mechanism to fail over to the backup site. The manual option via Azure DNS works best when used in conjunction with the cold standby or the pilot light approach.
 
-![Manual failover using Azure DNS](../networking/media/disaster-recovery-dns-traffic-manager/manual-failover-using-dns.png)
+![Diagram of manual failover using Azure DNS](../networking/media/disaster-recovery-dns-traffic-manager/manual-failover-using-dns.png)
 
 *Figure - Manual failover using Azure DNS*
 
@@ -65,13 +65,13 @@ The assumptions made for the solution are:
 
 1. Create a DNS zone (for example, www\.contoso.com) as shown below:
 
-    ![Create a DNS zone in Azure](../networking/media/disaster-recovery-dns-traffic-manager/create-dns-zone.png)
+    ![Screenshot of creating a DNS zone in Azure](../networking/media/disaster-recovery-dns-traffic-manager/create-dns-zone.png)
 
     *Figure - Create a DNS zone in Azure*
 
 1.  Within this zone, create three records (for example - www\.contoso.com, prod.contoso.com and dr.consoto.com) as show below.
 
-    ![Create DNS zone records](../networking/media/disaster-recovery-dns-traffic-manager/create-dns-zone-records.png)
+    ![Screenshot of creating DNS zone records](../networking/media/disaster-recovery-dns-traffic-manager/create-dns-zone-records.png)
 
     *Figure - Create DNS zone records in Azure*
 
@@ -80,7 +80,7 @@ The assumptions made for the solution are:
 
 1. Once failure is detected, change the record value to point to dr.contoso.com as shown below:
 
-    ![Update CNAME record](../networking/media/disaster-recovery-dns-traffic-manager/update-cname-record.png)
+    ![Screenshot of updating CNAME record](../networking/media/disaster-recovery-dns-traffic-manager/update-cname-record.png)
 
     *Figure - Update the CNAME record in Azure*
 
@@ -93,7 +93,7 @@ The assumptions made for the solution are:
        --record-set-name www \
        --cname dr.contoso.com
     ```
-    This step can be executed manually or via automation. It can be done manually via the console or by the Azure CLI. The Azure SDK and API can be used to automate the CNAME update so that no manual intervention is required. Automation can be built via Azure functions or within a third-party monitoring application or even from on- premises.
+    This step can be executed manually or via automation. It can be done manually via the console or by the Azure CLI. The Azure SDK and API can be used to automate the CNAME update so that no manual intervention is required. Automation can be built via Azure functions or within a third-party monitoring application or even from on-premises.
 
 
 ## Next steps

articles/reliability/reliability-traffic-manager.md

@@ -4,7 +4,7 @@ description: Learn about reliability in Azure Traffic Manager.
 author: anaharris-ms
 ms.author: anaharris
 ms.topic: overview
-ms.custom: subject-reliability, references.regions
+ms.custom: subject-reliability, references-regions
 ms.service: traffic-manager
 ms.date: 02/02/2024
 ---
@@ -26,7 +26,7 @@ This article contains  [specific reliability recommendations for Azure Traffic M
 | Category | Priority |Recommendation |  
 |---------------|--------|---|
 | [**Availability**](#availability) |:::image type="icon" source="media/icon-recommendation-high.svg":::| [Traffic Manager Monitor status should be Online](#-traffic-manager-monitor-status-should-be-online) |
-|  |:::image type="icon" source="media/icon-recommendation-high.svg":::| [TTraffic manager profiles should have more than one endpoint](#-traffic-manager-profiles-should-have-more-than-one-endpoint) |
+|  |:::image type="icon" source="media/icon-recommendation-high.svg":::| [Traffic manager profiles should have more than one endpoint](#-traffic-manager-profiles-should-have-more-than-one-endpoint) |
 |[**System efficiency**](#system-efficiency)|:::image type="icon" source="media/icon-recommendation-medium.svg"::: |[TTL value of user profiles should be in 60 seconds](#-ttl-value-of-user-profiles-should-be-in-60-seconds) | 
 |[**Disaster recovery**](#disaster-recovery)|:::image type="icon" source="media/icon-recommendation-medium.svg"::: |[Configure at least one endpoint within another region](#-configure-at-least-one-endpoint-within-another-region) | 
 ||:::image type="icon" source="media/icon-recommendation-medium.svg"::: |[Ensure endpoint configured to “(All World)” for geographic profiles](#-ensure-endpoint-configured-to-all-world-for-geographic-profiles) | 
@@ -44,7 +44,7 @@ To troubleshoot a degraded state on Azure Traffic Manager, see [Troubleshooting
 
 #### :::image type="icon" source="media/icon-recommendation-high.svg"::: **Traffic manager profiles should have more than one endpoint** 
 
-When configuring the Azure traffic manager, you should provision minimum of two endpoints to fail-over the workload to a another instance. 
+When configuring the Azure traffic manager, you should provision minimum of two endpoints to fail-over the workload to another instance. 
 
 To learn about Traffic Manager endpoint types, see [Traffic Manager endpoints](/azure/traffic-manager/traffic-manager-endpoint-types).
 
@@ -103,7 +103,7 @@ When you have complex architectures and multiple sets of resources capable of pe
 
 In the following example, both the primary region and the secondary region have a full deployment. This deployment includes the cloud services and a synchronized database. 
 
-![Automatic failover using Azure Traffic Manager](../networking/media/disaster-recovery-dns-traffic-manager/automatic-failover-using-traffic-manager.png)
+![Diagram of automatic failover using Azure Traffic Manager](../networking/media/disaster-recovery-dns-traffic-manager/automatic-failover-using-traffic-manager.png)
 
 *Figure - Automatic failover using Azure Traffic Manager*
 
@@ -120,19 +120,19 @@ This scenario is ideal for the use of Azure Traffic Manager that has inbuilt pro
 **To configure the failover with Azure Traffic Manager:**
 
 1. Create a new Azure Traffic Manager profile
-Create a new Azure Traffic manager profile with the name contoso123 and select the Routing method as Priority. 
-If you have a pre-existing resource group that you want to associate with, then you can select an existing resource group, otherwise, create a new resource group.
-
-    ![Create Traffic Manager profile](../networking/media/disaster-recovery-dns-traffic-manager/create-traffic-manager-profile.png)
+    Create a new Azure Traffic manager profile with the name contoso123 and select the Routing method as Priority. 
+    If you have a pre-existing resource group that you want to associate with, then you can select an existing resource group, otherwise, create a new resource group.
+    
+    ![Screenshot of creating Traffic Manager profile](../networking/media/disaster-recovery-dns-traffic-manager/create-traffic-manager-profile.png)
 
     *Figure - Create a Traffic Manager profile*
-
+    
 1. Create endpoints within the Traffic Manager profile
 
     In this step, you create endpoints that point to the production and disaster recovery sites. Here, choose the **Type** as an external endpoint, but if the resource is hosted in Azure, then you can choose **Azure endpoint** as well. If you choose **Azure endpoint**, then select a **Target resource** that is either an **App Service** or a **Public IP** that is allocated by Azure. The priority is set as **1** since it's the primary service for Region 1.
     Similarly, create the disaster recovery endpoint within Traffic Manager as well.
 
-    ![Create disaster recovery endpoints](../networking/media/disaster-recovery-dns-traffic-manager/create-disaster-recovery-endpoint.png)
+    ![Screenshot of creating disaster recovery endpoints](../networking/media/disaster-recovery-dns-traffic-manager/create-disaster-recovery-endpoint.png)
 
     *Figure - Create disaster recovery endpoints*
 
@@ -144,7 +144,7 @@ If you have a pre-existing resource group that you want to associate with, then
     If the Retry is set to 1 and TTL is set to 10 secs, then the time for failover 10 + 1 * 10 = 20 seconds. Set the Retry to a value greater than **1** to eliminate chances of failovers due to false positives or any minor network blips. 
 
 
-    ![Set up health check](../networking/media/disaster-recovery-dns-traffic-manager/set-up-health-check.png)
+    ![Screenshot of setting up health check](../networking/media/disaster-recovery-dns-traffic-manager/set-up-health-check.png)
 
     *Figure - Set up health check and failover configuration*