Merge pull request #225600 from spelluru/egridremove0130

removing file as per PM

Author: v-dirichards

articles/event-grid/.openpublishing.redirection.event-grid.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "custom-disaster-recovery.md",
+      "redirect_url": "/azure/event-grid/custom-disaster-recovery-client-side",
+      "redirect_document_id": false
+    },    
     {
       "source_path": "premium-basic-tiers.md",
       "redirect_url": "https://azure.microsoft.com/pricing/details/event-grid/",

articles/event-grid/availability-zones-disaster-recovery.md

@@ -35,7 +35,7 @@ Here are a few reasons why you may want to disable the Microsoft-initiated failo
 - Microsoft-initiated failover is done on a best-effort basis. 
 - Some geo pairs may not meet your organization's data residency requirements. 
 
-In such cases, the recommended option is to [build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md). While this option requires a bit more effort, it enables faster failover, and you are in control of choosing secondary regions. If you want to implement client-side disaster recovery for Azure Event Grid topics, see [Build your own client-side disaster recovery for Azure Event Grid topics](custom-disaster-recovery-client-side.md). 
+In such cases, the recommended option is to build your own disaster recovery plan for Azure Event Grid topics and domains. While this option requires a bit more effort, it enables faster failover, and you are in control of choosing secondary regions. If you want to implement client-side disaster recovery for Azure Event Grid topics, see [Build your own client-side disaster recovery for Azure Event Grid topics](custom-disaster-recovery-client-side.md). 
 
 
 ## RTO and RPO
@@ -45,7 +45,7 @@ Disaster recovery is measured with two metrics:
 - Recovery Point Objective (RPO): the minutes or hours of data that may be lost. 
 - Recovery Time Objective (RTO): the minutes or hours the service may be down. 
 
-Event Grid’s automatic failover has different RPOs and RTOs for your metadata (topics, domains, event subscriptions.) and data (events). If you need different specification from the following ones, you can still implement your own [client-side fail over using the topic health apis](custom-disaster-recovery.md). 
+Event Grid’s automatic failover has different RPOs and RTOs for your metadata (topics, domains, event subscriptions.) and data (events). If you need different specification from the following ones, you can still implement your own client-side failover using the topic health apis. 
 
 ### Recovery point objective (RPO)
 - **Metadata RPO**: zero minutes. For applicable resources, when a resource is created/updated/deleted, the resource definition is synchronously replicated to the geo-pair. When a failover occurs, no metadata is lost.
@@ -61,4 +61,4 @@ Event Grid’s automatic failover has different RPOs and RTOs for your metadata
 > - Geo-disaster recovery is not supported for partner namespaces and partner topics. 
 
 ## Next steps
-If you want to implement your own disaster recovery plan for Azure Event Grid topics and domains, see [Build your own disaster recovery for custom topics in Event Grid](custom-disaster-recovery.md).
+See [Build your own client-side disaster recovery for Azure Event Grid topics](custom-disaster-recovery-client-side.md).

articles/event-grid/configure-custom-topic.md

@@ -63,7 +63,7 @@ When you use Azure portal, you can assign one system assigned identity and up to
     1. Select **Add**. 
 1. Refresh the list in the **User assigned** tab to see the added user-assigned identity.
 
-You can use similar steps to enable an identity for an event grid domain.
+You can use similar steps to enable an identity for an Event Grid domain.
 
 ## Configure data residency
 
@@ -72,7 +72,7 @@ You can use similar steps to enable an identity for an event grid domain.
 
     The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
 
-    If you select the **Regional** option, you may define your own disaster recovery plan. For more information, see [Build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md). 
+    If you select the **Regional** option, you may define your own disaster recovery plan. 
 
     :::image type="content" source="./media/configure-custom-topic/data-residency.png" alt-text="Screenshot showing the Configuration page with data residency settings.":::        
 1. After updating the setting, select **Apply** to apply changes.  
@@ -91,4 +91,4 @@ See the following samples to learn about publishing events to and consuming even
 - [Azure Event Grid samples for Java](/samples/azure/azure-sdk-for-java/eventgrid-samples/)
 - [Azure Event Grid samples for Python](/samples/azure/azure-sdk-for-python/eventgrid-samples/)
 - [Azure Event Grid samples for JavaScript](/samples/azure/azure-sdk-for-js/eventgrid-javascript/)
-- [Azure Event Grid samples for TypeScript](/samples/azure/azure-sdk-for-js/eventgrid-typescript/)
+- [Azure Event Grid samples for TypeScript](/samples/azure/azure-sdk-for-js/eventgrid-typescript/)

articles/event-grid/create-custom-topic.md

@@ -74,7 +74,7 @@ On the **Security** page of the **Create Topic**  or **Create Event Grid Domain*
 
     The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
 
-    If you select the **Regional** option, you may define your own disaster recovery plan. For more information, see [Build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md).
+    If you select the **Regional** option, you may define your own disaster recovery plan. 
 3. Select **Next: Tags** to move to the **Tags** page. 
 
 ## Tags page

articles/event-grid/custom-disaster-recovery.md

@@ -35,7 +35,7 @@ sections:
       - question: |
           How do I recover from a failover?
         answer: |
-          If you opt in "cross-geo" in data residency configuration of the Azure Event Grid topics and domains, event subscription configuration data, also known as "metadata" will be replicated to a predefined secondary region. This allows Microsoft-initiated failover to the paired region if a failure occurs in a region. See [Azure cross-region replication pairings for all geographies](../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) to learn more about the supported paired regions. Otherwise, if you opt in "regional", no data of any kind is replicated to another region by Microsoft. You may define your own disaster recovery plan. For more information, see [Build your own disaster recovery for custom topics in Event Grid](custom-disaster-recovery.md).
+          If you opt in "cross-geo" in data residency configuration of the Azure Event Grid topics and domains, event subscription configuration data, also known as "metadata" will be replicated to a predefined secondary region. This allows Microsoft-initiated failover to the paired region if a failure occurs in a region. See [Azure cross-region replication pairings for all geographies](../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) to learn more about the supported paired regions. Otherwise, if you opt in "regional", no data of any kind is replicated to another region by Microsoft. You may define your own disaster recovery plan. 
 
           Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from the user. Microsoft reserves the right to make a determination of when this option will be exercised. This mechanism doesn't involve a user consent before the user's traffic is failed over.
   - name: Data residency

articles/event-grid/event-grid-faq.yml

@@ -316,12 +316,8 @@ items:
       href: cloudevents-schema.md
     - name: Manage topics with Event Domains
       href: how-to-event-domains.md
-    - name: Disaster recovery
-      items:
-      - name: Build your own disaster recovery plan
-        href: custom-disaster-recovery.md
-      - name: Build your own client-side disaster recovery
-        href: custom-disaster-recovery-client-side.md
+    - name: Build your own client-side disaster recovery
+      href: custom-disaster-recovery-client-side.md
     - name: Track asynchronous REST operations
       href: ../azure-resource-manager/management/async-operations.md?toc=/azure/event-grid/toc.json
     - name: Move