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$$$$$$Weve improved cache invalidation for Dynamic: OneDrive shortcut drives; significantly reducing the time it takes for drives to appear after mapping.$$$$$$Reference No: 36291$$$$$$Weve 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 Request icon$$$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 is

Bug fixes$$$Customer Request icon$$$We’ve fixed the issue where; if an upgrade failed or did not clear down the temp directory properly; it would reinstall an outdated prerequisite; resulting in CDM being unable to start correctly.$$$Reference No: 36501$$$We found a bug in release 3.20 when the same version was silently deployed via MSI more than once. This problem prevents future upgrades and uninstallation; so we have created a solution that allows affected customers to apply this hotfix over their current CDM installation to resolve the issue.$$$Reference No: 36614

Bug fixes$$$Customer Request icon$$$We’ve fixed the issue where; if an upgrade failed or did not clear down the temp directory properly; it would reinstall an outdated prerequisite; resulting in CDM being unable to start correctly.$$$Reference No: 36501$$$We found a bug in release 3.20 when the same version was silently deployed via MSI more than once. This problem prevents future upgrades and uninstallation; so we have created a solution that allows affected customers to apply this hotfix over their current CDM installation to resolve the issue.$$$Reference No: 36614