changes: files-data-protection-overview

Author: stevenmatthew

articles/storage/common/storage-failover-customer-managed-planned.md

@@ -26,19 +26,7 @@ During the planned failover process, your storage account's primary and secondar
 
 This article describes what happens during a customer-managed planned failover and failback at every stage of the process. To understand how a failover due to an unexpected storage endpoint outage works, see [How customer-managed (unplanned) failover](storage-failover-customer-managed-unplanned.md).
 
-> [!IMPORTANT]
-> Customer-managed planned failover is currently in PREVIEW and limited to the following regions:
-> 
-> - France Central 
-> - France South 
-> - India Central 
-> - India West 
-> - East Asia
-> - Southeast Asia 
->
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-> 
-> To opt in to the preview, see [Set up preview features in Azure subscription](../../azure-resource-manager/management/preview-features.md) and specify `AllowSoftFailover` as the feature name. The provider name for this preview feature is **Microsoft.Storage**.
+[!INCLUDE [storage-failover.planned-preview](../../../includes/storage-failover.planned-preview.md)]
 
 [!INCLUDE [storage-failover-user-unplanned-preview-lst](../../../includes/storage-failover-user-unplanned-preview-lst.md)]
 

articles/storage/files/files-data-protection-overview.md

@@ -4,7 +4,7 @@ description: Learn how to protect your data in Azure Files. Understand the conce
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: conceptual
-ms.date: 07/26/2023
+ms.date: 08/04/2024
 ms.author: kendownie
 ---
 
@@ -77,9 +77,11 @@ Azure Files offers multiple redundancy options, including geo-redundancy, to hel
 > Azure Files only supports geo-redundancy (GRS or GZRS) for standard SMB file shares. Premium file shares and NFS file shares must use locally redundant storage (LRS) or zone redundant storage (ZRS).
 
 ## Disaster recovery and failover
-In the case of a disaster or unplanned outage, restoring access to file share data is usually critical to keeping the business operational. Depending on the criticality of the data hosted in your file shares, you might need a disaster recovery strategy that includes failing your Azure file shares over to a secondary region.
+In the case of a disaster or unplanned outage, restoring access to file share data is critical to keeping the business operational. Depending on the criticality of the data hosted in your file shares, you might need a disaster recovery strategy that includes failing your Azure file shares over to a secondary region.
 
-Azure Files offers customer-managed (unplanned) failover for standard storage accounts if the data center in the primary region becomes unavailable. 
+Azure Files offers customer-managed unplanned failover for standard storage accounts if the data center in the primary region becomes unavailable. Customer-managed planned failover can also be utilized in multiple scenarios, including planned disaster recovery testing, a proactive approach to large scale disasters, or to recover from non-storage related outages.
+
+[!INCLUDE [storage-failover.planned-preview](../../../includes/storage-failover.planned-preview.md)]
 
 [!INCLUDE [storage-failover-user-unplanned-preview-lst](../../../includes/storage-failover-user-unplanned-preview-lst.md)]
 

includes/storage-failover-user-unplanned-preview-lst.md

@@ -6,7 +6,7 @@ author: stevenmatthew
 ms.service: azure-storage
 ms.subservice: common-concepts
 ms.topic: "include"
-ms.date: 05/02/2024
+ms.date: 08/04/2024
 ms.author: shaas
 ms.custom: "include file", references_regions
 ---
@@ -18,8 +18,7 @@ ms.custom: "include file", references_regions
 >
 > Because user activities such as creating, modifying, or deleting objects can trigger snapshot creation, any account on which these activities occur after planned failover will not require additional attention. However, accounts having no snapshots or user activity may continue to display a `Null` LST value until system snapshot creation is triggered.
 >
->If necessary, perform one of the following activities to trigger snapshot creation. Upon completion, your account should display a valid LST value within 30 minutes' time.
+>If necessary, perform one of the following activities **for each share within a storage account** to trigger snapshot creation. Upon completion, your account should display a valid LST value within 30 minutes' time.
 >
 >   - Mount the share, then open any file for reading.
->   - Upload a test or sample file to the share.
->   - Create a share snapshot for the share from the Azure portal.
+>   - Upload a test or sample file to the share.

includes/storage-failover.planned-preview.md

@@ -0,0 +1,26 @@
+---
+title: "include file"
+description: "include file"
+services: storage
+author: stevenmatthew
+ms.service: azure-storage
+ms.subservice: common-concepts
+ms.topic: "include"
+ms.date: 08/04/2024
+ms.author: shaas
+ms.custom: "include file", references_regions
+---
+
+> [!IMPORTANT]
+> Customer-managed planned failover is currently in PREVIEW and limited to the following regions:
+>
+> - France Central 
+> - France South 
+> - India Central 
+> - India West 
+> - East Asia
+> - Southeast Asia 
+> 
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+> 
+> To opt in to the preview, see [Set up preview features in Azure subscription](../../azure-resource-manager/management/preview-features.md) and specify `AllowSoftFailover` as the feature name. The provider name for this preview feature is **Microsoft.Storage**.