Cloud Drive Mapper (CDM) 3.21

Release date: October 6, 2025

CDM client

New features

You can now create and manage drive collaboration policies in Iris, giving you greater control over how users work with SharePoint documents through CDM-mapped drives. Drive collaboration policies allow you to turn co-authoring on or off in supported Microsoft 365 apps and configure automatic document check-out/check-in preferences to suit your organization’s needs. Learn more

Reference No: 32392
We’ve introduced the CDM Provider Monitoring Service to help improve performance and make troubleshooting easier. The service monitors the connection between CDM and the provider (for example, Microsoft 365) for signs of deterioration, such as throttling. By continuously collecting and analyzing telemetry data, the CDM Provider Monitoring Service can detect throttling early and provide greater visibility into service-related issues. Learn more

Reference No: 34847

Enhancements

CDM now subscribes to changes across all drive types using the Microsoft Graph notification subscription service and accurately maintains subscription states. CDM is not yet configured to consume these notifications.

Reference No: 28149
We’ve optimized CDM co-authoring to reduce local disk usage when working with large documents. This enhancement also resolves a previously known issue, ensuring that copied co-authored files always reflect the latest version.

Reference No: 34647
We’ve improved startup cleanup operations to minimize CDM’s use of local disk space.

Reference No: 35062
We’ve added automatic HTTP trace logging to make diagnosing issues easier. Logs never include authentication details, keeping your data secure.

Reference No: 35413
We’ve updated the CDM Provider Monitoring Service to be configurable within Iris for each mapping group, giving you greater flexibility and control over monitoring.

Reference No: 35996
We’ve improved how CDM interacts with its database, enabling drives to load faster and providing enhanced navigation speeds of large directories in File Explorer.

Reference No: 36112
We’ve moved the CDM Provider Monitoring Service to a new internal framework, ensuring telemetry data is sent in a consistent, authenticated, and resilient way.

Reference No: 36199
We’ve improved deduplication for Dynamic: SharePoint drives, enabling CDM to automatically resolve conflicts when sites and document libraries have the same name.

Reference No: 36201
We’ve made CDM more resilient when mapping custom drives. If an endpoint encounters an issue, CDM continues mapping the remaining drives and automatically retries any that fail due to transient issues until they are mapped successfully.

Reference No: 36289
We've improved cache invalidation for Dynamic: OneDrive shortcut drives, significantly reducing the time it takes for drives to appear after mapping.

Reference No: 36291
We've improved logging across CDM components, making troubleshooting faster and more reliable.

Reference No: 36301
We’ve enhanced security by salting device IDs locally with a key unknown to IAM Cloud or anyone else, further protecting your data during license validation.

Reference No: 36791
CDM version information is now available to the Provider Monitoring Service, helping us make more informed decisions about service availability during throttling.

Reference No: 37002
We’ve added automatic recovery, allowing CDM to restore itself if the database becomes unexpectedly corrupted.

Reference No: 37077
We’ve improved delta recovery so CDM can automatically recover when Microsoft 365 returns invalid data, preventing endless delta refresh loops and ensuring uploads and downloads continue without interruption.

Reference No: 37210

Bug fixes

Customer-reported

We’ve fixed an issue where the file upload progress window stayed open after the upload had finished.

Reference No: 35258
We’ve fixed an issue that prevented Microsoft 365 documents created locally from opening in co-authoring.

Reference No: 36315
Customer-reported

We’ve fixed an issue that prevented Windows from shutting down or logging out properly when CDM couldn’t map drives due to a missing license key or failed authentication.

Reference No: 36786
Customer-reported

We’ve fixed an issue that stopped CDM from mapping drives when the SharePoint document library subsite URL contained square brackets.

Reference No: 37004
Customer-reported

We’ve fixed an issue that caused a recursive delta refresh for newly created co-authoring files.

Reference No: 37187
We’ve fixed an issue that prevented CDM from maintaining authentication to Bifrost, which stopped sessions from closing correctly.

Reference No: 37278

CDM installer

Enhancements

You can now remove CDM Legacy when installing or upgrading CDM v3 through the Command-line Interface (msiexec) or the EXE standalone installer.

Reference No: 28771
We’ve strengthened security by ensuring all CDM and installer components are digitally signed whenever we publish them.

Reference No: 35950
We’ve updated the installer pipeline so the version.txt file now shows only major.minor.patch for production releases. Visible areas display Major.Minor.Patch, while binaries continue to include Major.Minor.Patch.Build.

Reference No: 36319

Bug fixes

Customer-reported

We’ve fixed several issues in the upgrade process that caused running CDM sessions to shut down incorrectly.

Reference No: 35373
Customer-reported

We’ve fixed an issue that caused CDM installations on standalone computers to fail and uninstallations to remove residual data incorrectly.

Reference No: 37282

Important reminder

Microsoft will be permanently deprecating their SharePoint RPS service on 15th October 2025. Please ensure if you are using CDM 2.22 or below that you have upgraded to either 2.24/2.25 or any version of CDM V3 before this date.