This template gets the files from your source file-based store. If there are new files arriving at the folder at the moment when your copy activity just completed the copy job but the Delete activity has not been stared, it is possible that the Delete activity will delete this new arriving file which has NOT been copied to the destination yet by deleting the entire folder. It is because you have to make sure that there will NOT be new files arriving into the folder between copying operation and deleting operation. If you want to move the folder by changing the dataset to make it contain a folder path only, and then using the copy activity and delete activity to reference to the same dataset representing a folder, you need to be very careful. The way that ADF pipeline achieves 'moving files' is getting the files from the landing folder, copying each of them to another folder on the destination store and then deleting the same files from the landing folder on the source store.īe aware that this template is designed to move files rather than moving folders.

By creating a schedule trigger, ADF pipeline can periodically move those files from the source to the destination store. One of the common scenarios of using this template: Files are continually dropped to a landing folder of your source store. This article describes a solution template as another approach leveraging ADF flexible control flow plus copy activity and delete activity to achieve the same scenario.

By doing so, copy activity will delete files from data source store after job completion. The way to enable it is to set “deleteFilesAfterCompletion” as true in copy activity. ADF copy activity has built-in support on “move” scenario when copying binary files between storage stores.

How to move files