Cloud Drive Mapper (CDM) 3.23

Release date: March 16, 2026

End of Support for pre-release versions

Support for CDM’s pre-release versions (v3.19 and earlier) ended on April 16, 2026. Consequently, break-fix support, and contractual SLAs are no longer in effect. If you are still using a pre-release version of CDM, we recommend updating to the latest version.

 

CDM client

New features

  • CDM now supports Microsoft Graph change notifications, enabling it to detect changes in Microsoft 365 in real-time so that it can retrieve the latest files and folders only when needed. This reduces the need for CDM to send unnecessary delta requests to Microsoft Graph and lowers the risk of throttling across your Microsoft 365 tenant.

    For more information about how CDM uses Microsoft Graph subscription notifications to detect changes in Microsoft 365 and retrieve the latest files and folders, see Subscription notifications.

    For more information about Windows Push Notification Services (WNS) errors, their root causes, and recommended resolutions, see Windows Push Notification Services (WNS) errors.

    Reference No: 25344

  • CDM can now start even when Bifrost (the IAM Cloud API) is temporarily unavailable. Previously, the CDM startup flow relied on responses from Bifrost. This dependency meant that if Bifrost was unavailable due to an outage, CDM would not start until the outage was resolved. Now, in the event of a Bifrost outage, CDM starts regardless, using previously cached data from the last successful session to validate the license, retrieve provider settings, and obtain mapping group configurations. Learn more

    Reference No: 39936

Enhancements

  • We’ve streamlined CDM’s log file cleanup process. CDM will now remove old log files stored in C:\ProgramData\IAM Cloud\Cloud Drive Mapper\Logs folder.

    Reference No: 37460

  • CDM will now be able to apply the maximum concurrent uploads and maximum concurrent downloads settings defined in Bifrost to users across an organization. These are bandwidth policy-related settings that enable organizations to manage how network bandwidth is allocated and used.

    Reference No: 37888

  • Customer Request icon
    Customer-reported

    Application binaries are now digitally signed during the CDM build process, enabling verification by application control systems.

    Reference No: 39215

Bug fixes

  • Customer Request icon
    Customer-reported

    We’ve fixed an issue where the temporary lock file created when saving an Asta Powerproject file on CDM-mapped drives was not automatically deleted.

    Reference No: 31659

  • We’ve fixed the issue that was preventing the Provider Monitoring Service from working when a CDM session extends beyond 12 hours.

    Reference No: 38610

CDM installer

Enhancements

  • When you upgrade to CDM 3.23 from release 3.20 or earlier, the installer will automatically remove configuration data linked to these earlier releases. This ensures that CDM 3.23 starts with clean, release-specific metadata and helps reduce the risk of unexpected behavior caused by legacy settings.

    Reference No: 35855

  • You can now force kill or force terminate all instances of CDM while deploying it silently through the command-line interface using the MSI or EXE file.

    Reference No: 37568