Merge pull request #291957 from normesta/normesta-reg-updates-14

A quick fix

Author: prmerger-automator[bot]

articles/storage-actions/storage-tasks/storage-task-known-issues.md

@@ -7,7 +7,7 @@ author: normesta
 ms.service: azure-storage-actions
 ms.custom: build-2023-metadata-update
 ms.topic: conceptual
-ms.date: 01/17/2024
+ms.date: 12/13/2024
 ms.author: normesta
 ---
 
@@ -38,6 +38,10 @@ During the preview, Azure Storage Actions can invoke up to 200 million operation
 
 For storage accounts with a hierarchical namespace, Azure Storage Actions can invoke up to 35 million operations per day for a maximum of seven days during the preview. Depending on the proportion of blobs targeted that meet the condition for operations, a task assignment might process between 35 million to 400 million blobs in a day.
 
+## Restrictions on moving a storage task
+
+You can't move a storage task to another region or to another subscription. You can't move a subscription that contains a storage task to another tenant.
+
 ## Overlapping prefix for assignments
 
 Storage tasks don't prevent execution of task assignments on overlapping prefixes. If there are multiple task assignments with overlapping prefixes, blobs might be processed by these task assignments in any order. If the execution order of operations across these task assignments is important, then as you configure the task, ensure that the prefix for assignments doesn't overlap.