---
title: "Set up Azure file storage connector"
slug: "set-up-azure-file-storage-connector-task"
description: "Set up an Azure file storage connector to exchange data files between D365 F&SCM and other environments, ensuring seamless data integration."
tags: ["Task topic"]
updated: 2026-07-24T04:35:02Z
published: 2026-07-24T04:35:02Z
canonical: "docs.staedean.com/set-up-azure-file-storage-connector-task"
---

> ## 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 Azure file storage connector

Set up a connector of type **Azure file storage**. Use this type to exchange data files between your D365 F&SCM environment (on-cloud or on-premises) and another environment, for example an on-premises environment.

With the **Azure file storage** type connector, you can exchange these external file-based documents: **EDI**, **Fixed text**, **Microsoft Word**, **Microsoft Excel**, **Text**, **XML**, **JSON**.

You can exchange data files using one of these file systems:

| File system | Description |
| --- | --- |
| Azure File Storage | You can use an Azure Storage Account to exchange data files between your D365 F&SCM environment (on-cloud or on-premises) and another environment, for example an on-premises environment. |
| Local folders | If you use Connectivity Studio on a D365 F&SCM (on-premises) environment, you can choose to use local Windows folders to exchange data files. |

> [!NOTE]
> Note
> 
> With this connector type, you exchange files between your D365 F&SCM environment and another environment. If the other environment has no access to the shared folder or local folder, you can use [file actions](/data-management/docs/set-up-file-actions-for-a-connector) to transfer the files to a location where the other environment can access the files.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. Click the **Connectors** tab.
3. Click **New**.
4. In the **Connector** field, type a value.

> [!NOTE]
> **Note**
> 
> You are advised to not include, in the connector name, the name of the application to which you connect. Use the Application field to define the applicable application for the connector.
5. In the **Project** field, enter or select a value.
6. Define the applicable application for the connector. For a staging journal connector, for example, select a 'Windows folder' application.

In the **Application** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> - You can only select an application that is defined for the applicable project. You can define project applications on the **Projects** page.
> - You can type any existing application name, whether it is defined as project application or not. If the typed application is not defined as project application, it is automatically added to the project applications.
7. In the **Connector type** field, select '**Azure file storage**'.
8. Sub-task: Set properties.
  1. You can export connectivity setup and import it in 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 prevent messing up 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 connector properties for each of your environment types. So, each connector can have a different set of properties for each applicable environment type. Which connector 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 connector properties, as defined for environment type **Development** are applicable. In the **Environment types** field, select an option.

> [!NOTE]
> **Note**
> 
> The environment types only apply to connectors of type **Database**, **Azure file storage**, **Blob storage**, **SharePoint**, or **Service Bus queue**.
  2. Expand the **Properties** section.
  3. 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.
  4. Enter the username to be used to access the Azure file share or Windows folder.

To access an Azure file share, the username is the name of the applicable Azure Storage Account.

In the **User name** field, type a value.

> [!NOTE]
> **Note**
> 
> You can only use one username and password combination to connect to an Azure Storage account. So, on all connectors that connect to the same Azure Storage account, the same username must be used.
  5. 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.
> - You can only use one user name and password combination to connect to one Azure Storage account. So, on all connectors that connect to the same Azure Storage account, the same password or password reference must be used.
  6. Enter the path to the **Working folder** of the connector.

If a message:

In the **Working path** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> Manually create the **Working** folder in the defined share.
    - Imports files, this is the source folder.
    - Exports files, this is the target folder.
  7. Enter the path to the **Archive folder** of the connector.

Files are:

In the **Archive path** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> Manually create the **Archive folder** in the defined share.
    - Moved to the **Archive folder** when imported without errors.
    - Copied to the **Archive folder** on export. If you export, the file is first created in the Working folder. When created, it is copied to the Archive folder.
  8. A message is always run for a specific company. Usually, this is the current company. You can store the message files in a separate folder for each company. As a result, if you run a message to:

Select **Yes** in the **Use company folders** field.

> [!NOTE]
> **Note**
> 
> If you use company folders, manually create the company folders.
> 
> Make sure the:
> 
> - Company folder names are exactly the same as the company IDs in D365 F&SCM.
> - Company folders are defined for each path folder of the connector: **Working**, **Archive**, **Error**, **Split** (if applicable), **Copy** (if applicable), and **Move** (if applicable).
    - Import files, it only searches for files in the folder for the company for which the message is run. Example: The message is run for company USMF. Files are only searched for in the [working path]\USMF folder.
    - Export files, the files are stored in the folder for the company for which the message is run. Example: The message is run for company USMF. Files are stored in the [working path]\USMF folder.
9. Sub-task: Set read options.
  1. Expand the **Read section**.
  2. If **Search sub folder** is **No**, on import, files are only searched for in the **Working folder**. You can indicate that, on import, files are also searched for in the sub folders of the **Working folder**. **Example:** Files come in from different systems (for example: PLM and webshop) and these files are placed in a separate sub folder for each system (for example: PLM files and webshop files). In this case, set **Search sub folder** to **Yes**.

Select **Yes** in the **Search subfolders** field.
  3. Enter the path to the **Error folder** of the connector.

If, on import of a file, errors occur, the file is moved to the **Error folder**.

In the **Error path** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> Manually create the **Error folder** in the defined share.
  4. Enter the path to the **Split folder** of the connector.

On import, you can split large files with a lot of records. Whether a file must be split is defined in the **Split quantity** field on documents of type **Text** or **Microsoft Excel**. As a result, the original file is put in the **Split folder** instead of the **Working folder**. When the message is run, the original file is split in smaller files based on the split quantity. The smaller split files are put in the **Working folder**. The message processes the split files in parallel.

In the **Split/Temporary path** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> - Manually create the **Split folder** in the defined share.
> - Only use the split functionality for simple (one record level) data. It is not suitable for data with multiple levels (header and line records).
10. Sub-task: Set write options.
  1. On write (creation of files), you can sort and store files in sub folders based on a specific table field value.

**Example:** You want to sort files by customer group. Fill in Table name='CustTable' and Field name='CustGroup'. Customer US-001 belongs to customer group 30. If a file is created for customer US-001, it is added to the [Working path]\30 folder.

Expand the **Write** section.

> [!NOTE]
> **Note**
> 
> - Table field folder sorting is only applied if you run a message for one specific record.
> - Make sure, the table field is also defined for the root record of the applicable document.
> - If you use table field folders, manually create the table field folders. Make sure the table field folder names are exactly the same as the table field values in D365 F&SCM. Also make sure these table field folders are defined for each path folder of the connector: **Working**, **Archive**, **Error**, **Split** (if applicable), **Copy** (if applicable), and **Move** (if applicable).
  2. Define the table for the table field folder sorting.

In the **Table name** field, enter or select a value.
  3. Define the table field for the table field folder sorting.

In the **Field name** field, enter or select a value.
11. Sub-task: Select custom handler.
  1. Expand the **Custom** section.
  2. For an **Azure file storage** type connector, the standard handler class is **BisConnectorWindowsFolder**. This handler class exports data to or imports data from a file.

You can use a customized handler class. To do so, extend the standard handler class.

In the **Handler** field, you can enter or select a custom handler class.
12. Sub-task: Set advanced options.
  1. Expand the **Advanced options** section.
  2. A document can have a query for which cross-company is enabled. If a user, with access to a restricted set of companies, runs a message that uses the document, the cross-company option does not work. If you have this scenario, make sure the cross-company option is enabled for the used connector. Otherwise, you can disable the cross-company option.

Select **Yes** in the **Cross company disabled** field.
  3. Close the page.

> [!NOTE]
> **Notes**
> 
> - You can test the connection. To do so, on the **Connectors** page, in the **Action Pane**, on the **Development** tab, click **Test connection**.
> - To connect to an Azure file share or a local Windows folder, the 'WnetaddConnection' DLL is used. However, it can only make one connection from your environment to a server. So, you can not link to the same server with different users and passwords.
> 
> Example:
> 
> You have two file storages:
>   - d365example.file.core.windows.net/purchase
>   - d365example.file.core.windows.net/sales
> 
> You can not connect to the 'purchase' storage with a user='PurchaseUser' and password='password' and to the 'sales' storage with user='SalesUser' and password='password002'. The WnetAddconnection DLL can only connect with one user to the 'd365example.file.core.windows.net' server.
> - You can change the type of an existing connector. If you do so, also fill in the applicable fields. For more information, refer to the topic about the setup of the newly chosen connector type.
> - You can use the File explorer to quickly access and view the share as defined for the **Azure file storage** connector. The **File explorer** offers limited functionality. You can only view, copy, move, or delete files. To open the **File explorer**, on the **Connectors** page, in the **Action Pane**, on the **Development** tab, click **File explorer**.

## Related

- [Customize connector handler class](/customize-connector-handler-class.md)
- [Set up file actions for a connector](/set-up-file-actions-for-a-connector.md)
- [Set up secret references](/set-up-secret-references.md)