---
title: "Set up file action - Delete"
slug: "set-up-file-action-delete"
description: "Learn how to set up a Delete file action for an Azure file storage connector, ensuring proper file management across development and production environments."
tags: ["Task topic"]
updated: 2026-09-01T11:10:09Z
published: 2026-09-01T11:10:09Z
canonical: "docs.staedean.com/set-up-file-action-delete"
---

> ## 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 - Delete

You can use the **Delete** file action to delete a file from the Working folder. Usually, the **Delete** file action is the last one to be done.

If the connector is set up properly with a different folder defined for **Working path**, **Archive path**, and **Error path**, a **Delete** file action is not required for direction **Source**. If the direction is **Target**, after the message is run, the created file is deleted from 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 **Delete** file action with direction **Target**.
  1. Click **New**.
  2. In the **Name** field, type a value.
  3. In the **File action** field, select **Delete**.
  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. Close the page.