Merge pull request #243522 from MSFTeegarden/patch-28

Update cache-how-to-geo-replication.md

Author: prmerger-automator[bot]

articles/azure-cache-for-redis/cache-how-to-geo-replication.md

@@ -138,7 +138,7 @@ Be sure to check the following items:
 
 - If you’re using a firewall in either cache, make sure that the firewall settings are similar so you have no connection issues.
 - Make sure both caches are using the same port and TLS/SSL settings
-- The geo-primary and geo-secondary caches have different access keys. If a failover is triggered, make sure your application can update the access key it's using to match the new geo-primary.
+- The geo-primary and geo-secondary caches have different access keys. If a failover is triggered, make sure your application can update the access key it's using to match the new geo-primary. Or, use [Azure Active Directory tokens for cache authentication](cache-azure-active-directory-for-authentication.md), which allow you to use the same authentication credential for both the geo-primary and the geo-secondary cache.   
 
 ### Failover with minimal data loss
 
@@ -149,6 +149,10 @@ Geo-failover events can introduce data inconsistencies during the transition, es
 
 There's no need to run the CLIENT UNPAUSE command as the new geo-primary does retain the client pause.
 
+>[!NOTE]
+>Using [Azure Active Directory based authentication](cache-azure-active-directory-for-authentication.md) for your cache is recommended in geo-failover scenarios because it removes the difficulty of managing different access keys for the geo-primary and the geo-secondary cache. 
+>
+
 ## Remove a geo-replication link
 
 1. To remove the link between two caches and stop geo-replication, select **Unlink caches** from the **Geo-replication** on the left.