Merge pull request #30441 from rajeshsetlem/patch-38

Clarification to add geo replication links for mismatch SLO

Author: prmerger-automator[bot]

azure-sql/includes/failover-group-overview.md

@@ -57,6 +57,6 @@ Set the failover policy to Microsoft managed only when:
 - It's acceptable that all databases within the failover group fail over, regardless of their zone redundancy configuration or availability status. Although databases configured for zone redundancy are resilient to zonal failures and might not be impacted by an outage, they'll still be failed over if they're part of a failover group with a Microsoft managed failover policy.  
 - It's acceptable to have forced failovers of databases in the failover group without taking into consideration the application's dependency on other Azure services or components used by the application, which can cause performance degradation or unavailability of the application.
 - It's acceptable to incur an unknown amount of data loss, as the exact time of forced failover can't be controlled, and ignores the synchronization status of the secondary databases.
-- All the primary and secondary database(s) in the failover group have the same service tier, compute tier (provisioned or serverless) & compute size (DTUs or vCores). If the service level objective (SLO) of all the databases in a failover group don't match, then the failover policy will be eventually updated from Microsoft Managed to Customer Managed by Azure SQL service. 
+- All the primary and secondary database(s) in the failover group and any geo replciation relationships have the same service tier, compute tier (provisioned or serverless) & compute size (DTUs or vCores). If the service level objective (SLO) of all the databases don't match, then the failover policy will be eventually updated from Microsoft Managed to Customer Managed by Azure SQL service. 
 
 When a failover is triggered by Microsoft, an entry for the operation name **Failover Azure SQL failover group** is added to the [Azure Monitor activity log](/azure/azure-monitor/essentials/activity-log). The entry includes the name of the failover group under **Resource**, and **Event initiated by** displays a single hyphen (-) to indicate the failover was initiated by Microsoft.  This information can also be found on the **Activity log** page of the new primary server or instance in the Azure portal.