adding more details with regards to networking

Author: axisc

articles/event-hubs/event-hubs-geo-dr.md

@@ -7,7 +7,10 @@ ms.date: 07/29/2024
 ---
 
 # Azure Event Hubs - Geo-disaster recovery 
-This article describes the Geo-disaster recovery feature that replicates metadata and is generally available. It doesn't describe the public preview Geo-replication feature, which replicates both data and metadata. For more information, see [Geo-replication](./geo-replication.md).
+
+> [!NOTE]
+> This article describes the Geo-disaster recovery feature that replicates metadata only. For more information, regarding Geo-replication feature, which replicates both data and metadata, see [Geo-replication](./geo-replication.md).
+>
 
 The all-active Azure Event Hubs cluster model with [availability zone support](../reliability/reliability-event-hubs.md) provides resiliency against  hardware and datacenter outages. However, if a disaster where an entire region and all zones are unavailable, you can use Geo-disaster recovery to recover your workload and application configuration. Geo-Disaster recovery ensures that the entire configuration of a namespace (Event Hubs, Consumer Groups, and settings) is continuously replicated from a primary namespace to a secondary namespace when paired. 
 

articles/event-hubs/geo-replication.md

@@ -234,5 +234,23 @@ For Premium namespaces, enabling geo-replication provisions the same number of p
 
 Bandwidth is charged based on the data transferred between the primary and secondary regions.
 
+## Private endpoints
+
+This section provides additional considerations when using Geo-Replication with namespaces that utilize private endpoints. For general information on using private endpoints with Event Hubs, see [Integrate Azure Event Hubs with Azure Private Link](private-link-service.md).
+
+When implementing Geo-Replication for a Event Hubs namespace that uses private endpoints, it is important to create private endpoints for both the primary and secondary regions. These endpoints should be configured against virtual networks hosting both primary and secondary instances of your application. For example, if you have two virtual networks, VNET-1 and VNET-2, you need to create two private endpoints on the Event Hubs namespace, using subnets from VNET-1 and VNET-2 respectively. Moreover, the VNETs should be set up with [cross-region peering](/azure/virtual-network/virtual-network-peering-overview), so that clients can communicate with either of the private endpoints. Finally, the [DNS](/azure/private-link/private-endpoint-dns) needs to be managed in such a way that all clients get the DNS information, which should point the namespace endpoint (namespacename.servicebus.windows.net) to the IP address of the private endpoint in the current primary region.
+
+> [!IMPORTANT]
+> When [promoting](#promotion-flow) a secondary region for Event Hubs, the DNS entry also needs to be updated to point to the corresponding endpoint.
+
+:::image type="content" source="./media/geo-replication/geo-replication-private-endpoints.png" alt-text="Screenshot showing two VNETs with their own private endpoints and VMs connected to an on-premises instance and a Event Hubs namespace.":::
+
+The advantage of this approach is that failover can occur independently at the application layer or on the Event Hubs namespace:
+
+- Application-only failover: In this scenario, the application moves from VNET-1 to VNET-2. Since private endpoints are configured on both VNET-1 and VNET-2 for both primary and secondary namespaces, the application continues to function seamlessly.
+- Event Hubs namespace-only failover: Similarly, if the failover occurs only at the Event Hubs namespace level, the application remains operational because private endpoints are configured on both virtual networks.
+
+By following these guidelines, you can ensure robust and reliable failover mechanisms for your Event Hubs namespaces using private endpoints.
+
 ## Related content
 To learn how to use the Geo-replication feature, see [Use Geo-replication](use-geo-replication.md).