Merge pull request #302779 from normesta/storage-actions-4

Adding include for reliability guidance

Author: JillGrant615

articles/reliability/reliability-storage-actions.md

@@ -28,7 +28,6 @@ While the Azure Storage Actions service is regional and doesn’t offer SKUs or
 - **Data plane (task assignment execution) inherits the zonal properties from the parent storage account.** If the storage account is deployed to a failed zone, then the account becomes unavailable and from customer’s perspective, the data plan isn't available. If the storage account is zone redundant, then the account continues to be available, and the service continue to perform operation on the account. 
 
 
-
 ### Zone down experience
 
 In a zone-done scenario, the Storage Action service continues to be available. The progress of tasks depends on the availability zone support of storage accounts against which they are running. If the account is not affected by the downed zone, the tasks continue to make progress. Otherwise, the tasks fail. 
@@ -42,10 +41,7 @@ The Storage Action service isn't zonal, but the storage account is. If the stora
 
 [!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
 
-Storage Action is a regional service, and it runs against accounts in the same region. When a region is down, both the storage account and service are also down.  The service doesn't support disaster recovery across regions. If you trigger a failover of the storage account to a different region, then storage tasks can’t run against the storage account until it fails back to the original region.  So, although you may be able to recover the storage account, the storage task won't be able to run against it. 
-
->[!IMPORTANT]
->If you migrate your storage account from a GRS or GZRS primary region to a secondary region or vice versa, then any storage tasks that target the storage account won't be triggered and any existing task executions might fail.
+[!INCLUDE [Storage Actions continuity after a failover](../../includes/storage-actions-reliability.md)]
 
 ### Outage detection, notification, and management
 

articles/storage-actions/storage-tasks/storage-task-best-practices.md

@@ -93,9 +93,7 @@ Storage Actions perform more reliably in accounts with [geo-redundant storage](.
 
 ### Use geo redundancy for business continuity 
 
-Storage accounts with GRS and GZRS replicate data to a secondary region in the event of storage account failovers. The business continuity of storage actions significantly depends on the redundancy configuration of the target storage account. Storage accounts that are configured with geo-redundancy benefit from an automated failover process. This automatic management ensures that future task assignment run iterations, whether single or recurrent, executes in the secondary region without issues. However, storage tasks that were in progress at the time of failover might encounter failures. New storage tasks and storage task assignments continue to function as expected.
-
-Consistent monitoring of the storage account is crucial. With a failover, you should thoroughly review task reporting and monitoring to verify the successful completion of all blob operations and to identify any discrepancies that need attention.
+[!INCLUDE [Storage Actions continuity after a failover](../../../includes/storage-actions-reliability.md)]
 
 ## Monitoring
 

includes/storage-actions-reliability.md

@@ -0,0 +1,11 @@
+---
+author: normesta
+ms.service: azure-storage-actions
+ms.topic: include
+ms.date: 07/15/2025
+ms.author: normesta
+---
+
+Storage accounts with GRS and GZRS replicate data to a secondary region in the event of storage account failovers. The business continuity of storage actions significantly depends on the redundancy configuration of the target storage account. Storage accounts that are configured with geo-redundancy benefit from an automated failover process. This automatic management ensures that future task assignment run iterations, whether single or recurrent, executes in the secondary region without issues. However, storage tasks that were in progress at the time of failover might encounter failures. New storage tasks and storage task assignments continue to function as expected.
+
+Consistent monitoring of the storage account is crucial. With a failover, you should thoroughly review task reporting and monitoring to verify the successful completion of all blob operations and to identify any discrepancies that need attention.