Updates

Author: johndowns

articles/reliability/includes/storage/reliability-storage-multi-region-considerations-latency-include.md

@@ -11,4 +11,4 @@
 
 - **Asynchronous replication latency**: Data replication to the secondary region is asynchronous, which means there's a lag between when data is written to the primary region and when it becomes available in the secondary region. This lag can result in potential data loss (measured as Recovery Point Objective or RPO) if a primary region failure occurs before recent data is replicated. The replication lag is expected to be less than 15 minutes, but this is an estimate and not guaranteed.
 
-    Before you perform a customer-managed unplanned failover, you can check the [Last Sync time](/azure/storage/common/last-sync-time-get) to understand how much data could be lost.
+    You can check the [Last Sync time](/azure/storage/common/last-sync-time-get) to understand how much data could be lost if your storage account has an unplanned failover.

articles/reliability/includes/storage/reliability-storage-multi-region-down-experience-include.md

@@ -55,7 +55,7 @@ This section describes what to expect when a storage account is configured for g
 
 - **Microsoft-managed failover**: In the rare case of a major disaster, where Microsoft determines the primary region is permanently unrecoverable, Microsoft might initiate automatic failover to the secondary region. This process is managed entirely by Microsoft and requires no customer action. The amount of time that elapses before failover occurs depends on the severity of the disaster and the time required to assess the situation.
 
+  - **Notification:** Region failure events can be monitored through Azure Service Health and Resource Health. Set up alerts on these services to receive notifications of region-level issues.
+
   > [!IMPORTANT]
   > Use customer-managed failover options to develop, test, and implement your disaster recovery plans. **Do not rely on Microsoft-managed failover**, which might only be used in extreme circumstances. A Microsoft-managed failover would likely be initiated for an entire region. It can't be initiated for individual storage accounts, subscriptions, or customers. Failover might occur at different times for different Azure services. We recommend you use customer-managed failover.
-
-  - **Notification:** Region failure events can be monitored through Azure Service Health and Resource Health. Set up alerts on these services to receive notifications of region-level issues.

articles/reliability/includes/storage/reliability-storage-multi-region-region-support-include.md

@@ -9,4 +9,6 @@
  ms.custom: include file
 ---
 
-Azure Storage geo-redundant configurations use Azure paired regions for secondary region replication. The secondary region is automatically determined based on your primary region selection and cannot be customized. For a complete list of Azure paired regions, see [Azure regions list](../../regions-list.md).
+Azure Storage geo-redundant configurations use [Azure paired regions](../../regions-paired.md) for secondary region replication. The secondary region is automatically determined based on your primary region selection and cannot be customized. For a complete list of Azure paired regions, see [Azure regions list](../../regions-list.md).
+
+ If your storage account's region isn't paired, consider using the [alternative multi-region approaches](#alternative-multi-region-approaches).