--- title: "Set up file action - Copy" slug: "set-up-file-action-copy" description: "Learn how to set up Copy file actions in Azure file storage for efficient file management across development and production environments." tags: ["Task topic"] updated: 2026-09-01T11:09:44Z published: 2026-09-01T11:09:44Z canonical: "docs.staedean.com/set-up-file-action-copy" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up file action - Copy You can use the **Copy** file action to copy a file to another location. If the direction is: - **Source**, before the message is run, the file is copied from a defined folder to the **Working** folder. The original file stays in the defined folder. - **Target**, after the message is run, the created file is copied from the **Working** folder to the defined folder. The original file stays in the **Working** folder. > [!NOTE] > Note > > You can set up file actions for these connector types: > > - **Azure file storage** > - **Azure File Storage (API)** > - **Azure Blob storage** > - **SharePoint** ### Steps 1. Click **Connectivity studio - Integration Design**. 2. Click the **Connectors** tab. 3. In the list, find and select the desired connector. 4. Click **Edit**. 5. You can export the connectivity setup and import it into another D365 F&SCM environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To protect your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the **Environment type** field on the **Connectivity studio parameters**. **Example**: If set to **Development**, the file action properties, as defined for environment type **Development** are applicable. In the **Environment types** field, select an option. > [!NOTE] > **Note** > > For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the **File action** section. 7. Sub-task: Set up a **Copy** file action with direction **Source**. 1. Click **New**. 2. In the **Name** field, type a value. 3. In the **File action** field, select **Copy**. 4. Click **Save**. 5. In the **Direction** field, select **Source**. 6. Define the name of the file to be copied. You can use filtering symbols. Example: CustGroup*.txt. In the **File name** field, type a value. 7. You can (temporarily) disable a flow action. **Example:** In a test setup, the setup to do the file action is not available. To prevent errors during test runs of the message, you disable the file action. In this way, you do not have to change or delete the file action. In the **Skip** field, select an option. 8. Enter the UNC path to the applicable Azure file share or Windows folder. In the **Share** field, type a value. > [!NOTE] > **Note** > > You can only use a Windows folder if it has access control with a user and password defined. 9. Enter the user name to be used to access the Azure file share or Windows folder. To access an Azure file share, the user name is the name of the applicable Azure Storage Account. In the **User name** field, type a value. 10. Define the password or the password reference to access the Azure file share or Windows folder. Whether the password or password reference applies is defined by the **Display secret** field in the **Connectivity studio parameters**. If the **Display secret** parameter is set to: - **Secret**, fill in the **Password** field with the desired password. The password is specific for the current file action. - **Secret reference**, fill in the **Password reference** field with the desired secret reference. The password reference refers to a centrally stored password which makes updating secrets easier. - **Both**, fill in either the **Password** field or the **Password reference** field. In the **Password** field or in the **Password reference** field, type a value. > [!NOTE] > **Note** > > To access an Azure file share, the password is the key, or the password reference refers to the key of the applicable Azure Storage Account. 11. Enter the path to the **Copy folder** of the connector. The file is copied from this folder to the **Working folder**. In the **Working path** field, enter or select a value. 8. Sub-task: Set up a **Copy** file action with direction **Target**. 1. Click **New**. 2. In the **Name** field, type a value. 3. In the **File action** field, select **Copy**. 4. Click **Save**. 5. In the **Direction** field, select **Target**. 6. Click **Save**. 7. You can (temporarily) disable a file action. Example: In a test setup, the setup to do the file action is not available. To prevent errors during test runs of the message, you disable the file action. In this way, you do not have to change or delete the file action. In the **Skip** field, select an option. 8. Enter the UNC path to the applicable Azure file share or Windows folder. In the **Share** field, type a value. > [!NOTE] > **Note** > > You can only use a Windows folder if it has access control with a user and password defined. 9. Enter the user name to be used to access the Azure file share or Windows folder. To access an Azure file share, the user name is the name of the applicable Azure Storage Account. In the **User name** field, type a value. 10. Define the password or the password reference to access the Azure file share or Windows folder. Whether the password or password reference applies is defined by the **Display secret** field in the **Connectivity studio parameters**. If the **Display secret** parameter is set to: - **Secret**, fill in the **Password** field with the desired password. The password is specific for the current file action. - **Secret reference**, fill in the **Password reference** field with the desired secret reference. The password reference refers to a centrally stored password which makes updating secrets easier. - **Both**, fill in either the **Password** field or the **Password reference** field. In the **Password** field or in the **Password reference** field, type a value. > [!NOTE] > **Note** > > To access an Azure file share, the password is the key, or the password reference refers to the key of the applicable Azure Storage Account. 11. Enter the path to the **Copy folder** of the file action. The file is copied from the **Working folder** to this folder. In the **Working path** field, enter or select a value. 9. Close the page. 10. Close the page. ## Related - [Set up secret references](/set-up-secret-references.md)