Merge pull request #242082 from Clare-Zheng82/0619-Update_staged_copy

[Supportability] - Update staged copy section

Author: prmerger-automator[bot]

articles/data-factory/copy-activity-performance-features.md

@@ -8,7 +8,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 02/08/2023
+ms.date: 06/20/2023
 
 ---
 
@@ -139,6 +139,8 @@ When you activate the staging feature, first the data is copied from the source
 
 :::image type="content" source="media/copy-activity-performance/staged-copy.png" alt-text="Staged copy":::
 
+You need to grant delete permission to your Azure Data Factory in your staging storage, so that the temporary data can be cleaned after the copy activity runs.
+
 When you activate data movement by using a staging store, you can specify whether you want the data to be compressed before you move data from the source data store to the staging store and then decompressed before you move data from an interim or staging data store to the sink data store.
 
 Currently, you can't copy data between two data stores that are connected via different Self-hosted IRs, neither with nor without staged copy. For such scenario, you can configure two explicitly chained copy activities to copy from source to staging then from staging to sink.