---
title: "Release 10.0.49.74 (September 2026) - Connectivity Studio"
slug: "release-10-0-49-74-september-2026-connectivity-studio"
description: "Explore the new features in Connectivity Studio Release 10.0.49.74 for Dynamics 365, including Exchange Online support and improved SQL trigger management."
tags: ["Connectivity Studio", "CS", "Release notes"]
status: "update"
updated: 2026-10-05T11:52:34Z
published: 2026-10-05T11:52:34Z
canonical: "docs.staedean.com/release-10-0-49-74-september-2026-connectivity-studio"
---

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

# Release 10.0.49.74 (September 2026) - Connectivity Studio

Find information on Release 10.0.49.74 (September 2026) of the Connectivity Studio for Microsoft Dynamics 365 Finance & Supply Chain Management.

Version information:

| Product | Version | Minimum version | Latest validated version | Planned next |
| --- | --- | --- | --- | --- |
| Connectivity Studio | 10.0.49.74 | D365 F&SCM 10.0.46 | D365 F&SCM 10.0.49 | December 2026 |

> [!NOTE]
> Note
> 
> Connectivity Studio updates are released as part of the Business Integration Solutions (BIS) release.

> [!WARNING]
> Compatibility warning
> 
> This warning only applies to connectors of type **Service Bus queue**. Starting September 30, 2026, only the AMQP protocol will be supported. If you have not upgrade to BIS version 10.0.49.74 by then, make sure the **Service Bus queue** connector property **Use AMQP protocol** is set to **Yes**. If you upgrade to BIS version 10.0.49.74, the connector property **Use AMQP protocol** is automatically set to **Yes**, and removed from the UI.

## What's new

New or changed Connectivity Studio features in Release 10.0.49.74 (September 2026) - Business Integration Solutions.

### 1. Exchange Online (Microsoft 365) enabled for file actions

Microsoft will deprecate the Exchange server email receiver from October 2026.

The **Email** file action now supports **Exchange Online (Microsoft 365)** as an email receiver and sender option, alongside the existing Exchange server, IMAP server, SMTP server, and D365 F&SCM email options. You connect using an Azure AD app registration, authenticating with a **Tenant ID**, **Client ID**, and client secret, instead of a mailbox password.

This option gives you a supported, app-based way to send and receive files by email with a Microsoft 365 mailbox, so your integrations stay secure and compliant with Microsoft's authentication requirements.

> [!WARNING]
> Compatibility warning
> 
> If you currently use the Exchange server email receiver file action, it will stop working after October 2026.
> 
> Action required:
> 
> - Install the latest version of Business Integration Solution (at least 10.0.49.74).
> - Update the email receiver configuration to use Exchange Online (Microsoft 365).
> - Update the required connection/configuration values with your Microsoft 365 details.
> - Test the email functionality after updating the configuration.

See also: [Set up file action - Email - Exchange Online (Microsoft 365)](/data-management/docs/set-up-file-action-email-exchange-online-microsoft-365)

### 2. File explorer opens the processed file's folder

The **File explorer**, when opened from the **File history** page**,** now opens directly in the folder where your processed file is located.

If the file moves successfully, **File explorer** opens the **Archive** folder. If processing fails, it opens the **Error** folder.

See also: [Use file explorer](/data-management/docs/use-file-explorer)

### 3. Resilient, schedulable SQL trigger recreation

Connectivity Studio now recreates SQL triggers table by table, instead of dropping and rebuilding all triggers at once. Each table is checked and processed independently. A failure or interruption on one table doesn't affect the triggers of other tables.

On installations with many projects and triggers, recreating all triggers in one operation could time out. This could leave your environment with missing or partially recreated triggers. Table-by-table recreation keeps existing triggers intact until each one is safely refreshed.

You can also schedule trigger recreation as a recurring batch job. This lets maintenance run unattended, even on large installations.

See also: [Monitor and recreate SQL triggers](/data-management/docs/monitor-and-recreate-sql-triggers)

### 4. Web service action attributes per environment type

Outbound web service actions can now use a different set of attributes for each environment type. Previously, a web service action had a single, shared attribute list that applied to every environment.

This new feature keeps environment-specific attributes, such as a query parameter or template segment, from leaking into another environment. You export a web service action from your development environment. When you import it into test, acceptance, or production, each environment applies its own attributes.

On **Web service actions** page, in the **Attributes** section, use the **Environment types** field to select the environment type an attribute applies to. To quickly reuse an attribute set, click **Copy attributes** and select a target environment type.

This feature is disabled by default. To enable it, in **Connectivity studio parameters**, on the **Features** tab, set the **Web service attributes per environment type** field to **Yes**.

See also:

- [Set up web service action - Outbound](/data-management/docs/set-up-web-service-action-outbound)
- [Set up Connectivity studio parameters](/data-management/docs/set-up-connectivity-studio-parameters).

### 5. For the Database connector, Azure Service Bus is replaced with Azure Relay

Microsoft retires the Azure Service Bus protocol on September 30, 2026. From this release, the **Database** connector uses Azure Relay instead, so it keeps working after that date.

This is a like-for-like migration. You set up and use the **Database** connector exactly as before.

It uses the same fields, the same shared access key, and gives the same results. Only the underlying network transport changes.

During the transition, the current and the new tunnel run side by side. You point the **Database** connector at the new endpoint when you're ready to cut over.

If needed, you can roll back immediately by pointing it back at the old endpoint.

> [!NOTE]
> Note
> 
> For firewall planning, allow outbound traffic on port 443 from the on-premises host to the Azure Relay endpoint. This tunnel doesn't use the messaging ports associated with Azure Service Bus.

See also: [Set up Azure Relay for Database connection](/data-management/docs/set-up-azure-relay-for-database-connection) (and related articles)

### 6. Clearer user feedback on locked files and unlocking files

The file unblocking experience now provides clearer user feedback:

- Updated error message: The stuck-file error message now explicitly references the **Update file history status** action, guiding you to the correct next step.
- Completion Infolog: After unblocking, an Infolog confirms the result. For example, that unblocking was successful and the number of files that were unblocked, or that no files were picked up to be unblocked.

See also: [Unlock files](/data-management/docs/unlock-files)

### 7. STAEDEAN Common Library

This release includes STAEDEAN Common Library, version 65. These new features are available:

- **Download a license package**: Skip maintenance mode and download the latest license package directly from the STAEDEAN Solution Management workspace.
- **Download a unified package**: Quickly find and download the right unified package for your installed solution, compliant with the N-3 support policy.

See also: [STAEDEAN Common Library](https://docs.staedean.com/pages/staedean-common-library).

## Bug fixes

Bug fixes for Connectivity Studio in Release 10.0.49.74 (September 2026) - Business Integration Solutions.

| Bug ID | Title | Description |
| --- | --- | --- |
| 239780 (CS00239250) | Unblock data process now handles files stuck in the Work folder | The **Update file history status** process (**Connectivity Studio** > **Periodic** > **Unblock data**) now also releases files with a **Message finished** status. Unblocked files move to the correct **Archive** or **Error** folder, and their status is updated so the message can run again without errors. A file locked by another message run now shows a clearer message directing you to run **Update file history status** first. |
| 243995 (CS00240171) | Consistent Blob storage folder naming for company folders | When **Use company folders** is enabled on a Blob storage connector, the target folder name is now based on the DataAreaId value from the DataArea table instead of the casing used in the URL. This keeps the folder name consistent every time the message runs, regardless of how the DataAreaId is cased in the URL. As a result, a company no longer ends up with duplicate folders that differ only in casing. |
| 246764 | Improved inbound file handling after XSLT modifications | History logging and status handling for XSLT-based inbound file transformations are improved, so a failed file move is always logged with a clear error status. Files that fail to move to the **Archive** or **Error** folder no longer show a misleading **Finished** status and are no longer picked up again while still being handled. This gives better visibility when a file move or archive step fails during processing. |
| 250771 | Message history recorded when a batch ends with stuck queue files | When a batch job ended while one or more files remained stuck or locked in the Azure message queue, no **Message History** record was created. A **Message History** record is now created for every batch run, so the outcome is always traceable. |
| 270970 | Files move to the Error folder when history status is Error | When message execution finished with a **History Status** of **Error** (for example due to an invalid archive folder path), the file stayed in the **Work** folder instead of moving to the configured **Error** folder. The file now moves to the **Error** folder as expected. |
| 271298 | Consistent Action entries for the Azure File Storage source connector | Unlike the **Blob Storage** connector, the **Azure File Storage** source connector did not create an Action entry in **File Action History** before the **Read** and **Move** actions. The **Azure File Storage** connector now records the Action entry consistently. |
| 271348 | Clearer error message for a blank Send To Address (Exchange Email connector) | When the **Send To Address** field was left blank on the **Exchange Email** connector, the error message incorrectly stated that the attachment file could not be found. The error message now correctly states that the recipient email address is missing. |
| 272237 | Locked and stuck files are archived and unblocked correctly | When using **Update file history status** to unblock files, locked or stuck files were not always archived or unblocked after the configured timeout elapsed. Locked and stuck files are now archived or unblocked correctly. |
| 272798 | BisMdmAddTaskToBatch can be added to a batch manually | Adding the **BisMdmAddTaskToBatch** task to an existing batch job manually, for example when onboarding additional companies, raised an error and the task could not be added. The task can now be added to a batch job manually as expected. |
| 275604 (CS00241343) | Compare BIS project version no longer crashes | Comparing project versions with **Connectivity Studio** > **Compare** could crash with an error. The project version comparison now runs without crashing. |
| 279921 | Web service action uses the correct Environment attribute value | After enabling environment-specific web service attributes, a **Web service action** could retain the previous environment's attribute value in the URL and in the **Web Request History**. The action now uses the attribute value for the current environment consistently. |

## Known Issues

Known issues for Connectivity Studio in Release 10.0.49.74 (September 2026) - Business Integration Solutions.

| Issue | Description |
| --- | --- |
| Context-sensitive help button | Connectivity Studio forms have a context-sensitive help button. **Example**: ![](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/Relese%20notes-contextsensitive%20help%20button.png) At this moment, the connection between the context-sensitive help button and the new documentation portal is not yet fully established. When clicking the help button, you will be redirected to the main page of Connectivity Studio in the new documentation portal. From there, you can navigate or search to find the information you need. |
| Feature Management Limitations | Microsoft regularly introduces new features via **Feature Management** or directly in the application. Some features are in public preview and will become generally available in future releases. Others are already generally available and can be activated. Compatibility with all new features or combinations is not tested. If issues arise after enabling a feature, contact STAEDEAN support. |
| Form Mapping Recorder Error | Starting the form mapping recorder can cause a fatal error. This occurs when opening the message from the **BIS** workspace. If you open the message from the **BIS** menu, the error does not occur. |
| SQL Trigger Creation Error | Version 10.0.39 enables the "SQL row version change tracking" feature by default, adding the **SysRowVersion** field to all tables. Exclude this field from synchronization triggers in **Connectivity Studio** messages or web services. Do not use version 10.0.39 with a Connectivity Studio version older than 10.0.39.59. |
| Inconsistent Test Results for Azure Blob Storage | In version 10.0.43.66, the **Test** functionality produces inconsistent results when the file action type is **Azure blob storage**. |
| Empty File Creation on Export | When an export message fails, an empty file is created on the target storage. |
| Missing File Action Detail for SFTP Import | In version 10.0.43.66, file action details are missing from file history after import when using the **SFTP** flow action type with the **Azure file storage connector**. |
| Started On Date Not Updated in Project and Task History | The **Started on** date is not being updated in project history and task history, leading to inconsistencies in tracking. |
| Open File Option Not Displaying Records in File Storage Explorer | The **Open file** option does not display records in the **File Storage Explorer**, impacting file visibility. |
| Processed Tile Count Not Displayed for Four-Digit Values | In the **Connectivity Studio** workspace, the **Today processed** and **7 days processed** tile counts are not displayed correctly when the count reaches four digits. |
| Service Bus Dead Letter - Entering 0 Does Not Retrieve All Messages | When receiving dead letter messages from a Service Bus queue, entering 0 in the **Number of messages** field does not retrieve any messages. Entering a specific number works as expected. |
| Incorrect Label Displayed for Certificate Upload | When uploading a certificate in the **Secret reference** setup, the label incorrectly shows **Select private key file** instead of the correct label for certificate upload. |

## Appendix

### 1. Libraries

Libraries in Release 10.0.49.74 (September 2026) – Business Integration Solutions, including Connectivity Studio.

| Library | Publisher | Usage |
| --- | --- | --- |
| AS2EncryptDecryptHandler.dll | STAEDEAN | Used to encrypt and decrypt for AS2 however it is deprecated but still part of the model |
| Azure.Storage.Files.Shares.dll | Microsoft | Standard .net library, the same as what D365 FSCM uses but added because D365 FSCM is not adding it to the default bin directory |
| BIS.Security.OAuth2.dll | STAEDEAN | Own library used to connect to third party web api and azure blob storage |
| BIS.System.Collections.dll | STAEDEAN | Own library used to connect to third party web api and azure blob storage |
| BisDotNetTools.dll | STAEDEAN | Some internal .net functions used by Connectivity Studio |
| BisEmail.dll | STAEDEAN | Own library wrapper for sending and receiving email |
| BisEmailWrapperMailKit.dll | STAEDEAN | Own library wrapper for sending and receiving email |
| BisFileCursor.dll | STAEDEAN | Own library to handle XML documents |
| BisInitFromXSDSchema.dll | STAEDEAN | Own library to handle XML documents |
| BisJsonReader.dll | STAEDEAN | Own library to handle JSON documents |
| BisMsGraphHelper.dll | STAEDEAN | Own Library to handle connection the Share point via MSGraph |
| BisNetworkShare.dll | STAEDEAN | Own library to make connection to a file storage to support direct read and write |
| BisOAuth.dll | STAEDEAN | Own library used to connect to third party web API and azure blob storage |
| BISODBCServiceBusClient.dll | STAEDEAN | Own library to handle the access to an on-premises database |
| BisRunCustomCode.dll | STAEDEAN | Own Library to handle expression in the mapping |
| BisSecureBlackBox.dll | STAEDEAN | Own Library to handle the access to use Secure Blackbox libraries |
| BisServiceBusQueueHelper.dll | STAEDEAN | Own Library to handle the access to service buses / Queue |
| BisStorageExtension.dll | STAEDEAN | Own library to handle the access to blobs storage use bearer tokens |
| BouncyCastle.Crypto.dll | Third party | Used for AS2 and email and encryption |
| BouncyCastle.Crypto.xml | Third party | Used for AS2 and email and encryption |
| BytesRoad.Net.Ftp.dll | Third party | Used for sending FTP |
| BytesRoad.Net.Sockets.dll | Third party | Used for sending FTP |
| ClosedXML.dll | Third party | Used for excel documents |
| DocX.dll | Third party | Used for Word document exports |
| ICSharpCode.SharpZipLib.DLL | Third party | Used in the Zip flow action |
| Microsoft.ServiceBus.dll | Microsoft | Standard .net dll used for service bus Queue. > [!NOTE] > Note > > Though it's retired, you can continue using it. See also: [Azure updates](https://azure.microsoft.com/en-us/updates?id=retirement-notice-update-your-azure-service-bus-sdk-libraries-by-30-september-2026). |
| Microsoft.WindowsAzure.Configuration.dll | Microsoft | Used for Azure blob storage is deprecated and replaced by standard azure.storage.Blobs dll |
| MimeKit.dll | Third party | Use for encryption As2 and for sending email |
| SecureBlackbox.Cloud.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.FTPS.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.HTTP.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.HTTPCommon.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.SFTP.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.SFTPCommon.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.SSHClient.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.SSHCommon.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.SSLClient.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.SSLCommon.dll | Third party | All Secure blackbox dll |
| SecureBlackbox.XML.dll | Third party | All Secure blackbox dll |
| System.Memory.Data.dll | Microsoft | Standard .net |
| Tl.OpenXmlClr.dll | Third party | Library used for excel |
| UtfUnknown.dll | Third party | Library used to detect file encoding in case dynamic encoding is used |