Learn Editor: Update storage-task-known-issues.md

Author: sshankMSFT

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

@@ -96,12 +96,16 @@ Storage accounts that have a hierarchical namespace display location information
 ## Moving storage tasks and task assignments
 Moving storage tasks and task assignments across different resource groups and subscriptions isn't supported. This limitation means that any storage tasks and their associated task assignments can't be transferred between resource groups or subscriptions.
 
-## Cleaning up task assignments before moving storage accounts
-Task assignments must be cleaned up before moving storage accounts across resource groups and subscriptions. Specifically, before a storage account is moved from one resource group to another, or from one subscription to another, all task assignments applied to the storage account must be deleted to ensure a smooth transition.
+## Cleaning up task assignments before deleting storage accounts or storage tasks
+- Before deleting a storage account, delete all task assignments associated with that storage account.
+- Before deleting a storage task, delete all task assignments referencing that storage task.
 
 ## Cleaning up task assignments before deleting storage accounts
 Task assignments must be cleaned up before deleting storage tasks or storage accounts. Specifically, before a storage account or storage tasks is deleted, all task assignments applied to the storage account must be deleted.
 
+## Operating on storage accounts in a private network is unsupported in PREVIEW regions
+When applying storage task assignments to storage accounts with IP or network access restrictions, task execution may fail. This occurs because the tasks require access via the public endpoint, which can be blocked by firewall or virtual network rules. To prevent this, ensure your storage account is configured to allow appropriate network access.
+
 ## Storage task runs are stuck in the in progress state
 
 If during the assignment process, you assign a role which doesn't have the required permission, the storage task run will take 14 days to fail. To unblock the task run, you can add the required role to the managed identity of the storage task. Otherwise, the task assignment will be stuck in the **in progress** state until the task run ends in 14 days.