---
title: "Solve connection issue for Azure file storage connector"
slug: "solve-connection-issue-for-azure-file-storage-connector"
tags: ["Task topic"]
updated: 2026-03-20T08:19:08Z
published: 2026-03-20T17:44:19Z
canonical: "docs.staedean.com/solve-connection-issue-for-azure-file-storage-connector"
---

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

# Solve connection issue for Azure file storage connector

For an **Azure file storage** connector, you can connect to an Azure file share. To access the Azure file share, you can mount the Azure file share.

For most connectors, when a message is run, a connection is made only for the run. After the run the connection ends. However, for an **Azure file storage** connection with a mounted Azure file share, the connection stays, independent of messages run.

When a related message is run or the connection is tested, a check is done, and an error can occur if something has changed. For example, the connector username or password is changed. In this case, the mounted connection to the Azure file share is no longer valid. To reset the mounting, first remove the connection (see steps). The next time, a related message is run, or the connection is tested, the mounting is restored, for example with the proper username or password.

Usually, messages are run in batch. If you run a message in batch, you can use a batch group to direct a batch task to another server. If a message runs on another server, the connection also stays on the other server. In case of an error or change, this connection is no longer valid. So also, the connection on the other servers must be removed.

For more information, refer to:

- [Use an Azure files share with Windows](https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows?tabs=azure-portal)
- [Batch processing overview](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-processing-overview)
- [Batch processing and batch servers](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-server-overview)

### Steps

1. Go to **Connectivity studio** > **Periodic** > **Cleanup** > **Remove connections**.
2. In the **Connector** field, enter or select the connector for which you want to remove the connection.
3. Sub-task: Define batch settings.
  1. If you use batch groups to direct batch tasks to other servers, also remove the connector connection from these other servers.

Expand the **Run in the background** section.
  2. Select **Yes** in the **Batch processing** field.
  3. In the **Batch group** field, enter or select the batch group that is used to direct batch tasks to other servers.

> [!NOTE]
> **Note**
> 
> Make sure to remove the connection from each of the available other servers to which batch tasks are directed.
  4. Click **OK**.

> [!NOTE]
> **Notes**
> 
> - 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 and password must be used.
> - You can also remove the connection for a specific connector from the **Connector** page. To do so, on the **Action Pane**, on the **Development** tab, click **Remove connections**.
> - Be careful, removing the connection. Only do so when a connection error occurs. Removing a connection can disrupt running processes in batch jobs.
> - Another way to restore the mounting to the Azure file share is to restart the D365 F&SCM environment. However, usually, this is not acceptable in a production environment.

## Related

- [Solve SFTP connection issue with private key](/solve-sftp-connection-issue-with-private-key.md)