Cloud Drive Mapper V3 has reached General Availability

Firstly, we’ve got some great news. Cloud Drive Mapper 3.20 is now live

After years of development, beta testing, and pre-release: CDM V3 has now reached General Availability 🎉

If you are already exclusively using CDM V3 then good news – you can stop reading here. But if you are still using CDM V2 (either in full or in part), please read the rest of the post.

This was always going to be an inflection point for us, and the start of a push towards CDM V3. However due to some incoming changes with Microsoft services that impact CDM V2 – the urgency is now higher, and we now recommend starting the first steps on your journey to V3 as soon as you can.

Situation with Microsoft

Microsoft contacted us a few weeks ago to let us know about their plans to deprecate SharePoint’s RPS service. While this doesn’t directly impact WebDAV, it does affect the way that CDM V2 has historically generated cookies for WebDAV’s authentication. Microsoft have now started soft-disabling RPS in phases between now and the end of August. The good news is that RPS can be re-enabled with PowerShell by an admin giving a temporary reprieve (see this article for more information). Microsoft will be permanently removing RPS on October 15th 2025.

If you do nothing, CDM V2 (2.22 or below) will stop working.

However, as well as launching CDM V3.20 in GA, we have just released an update to CDM V2 (CDM 2.24) that uses a different method for generating cookies. We have tested this with RPS disabled on a tenancy, and have confirmed it works successfully.

This fix means CDM V2 (2.24) will continue working even when RPS is removed.

But we want to stress that the interactions we’ve had with Microsoft recently have displayed a significant desire by MS to start shutting down legacy systems and protocols, including the WebDAV service itself. They have confirmed this will not happen this year, but it is now something they are actively planning.

Our recommendations

  1. At the very least, we recommend all CDM V2 customers to upgrade to 2.24 ASAP. Just do some basic testing in your environment to ensure the authentication and drive mapping is working as expected before deployment – then it should be safe to update as nothing else has changed since the previous release.
  2. We then strongly recommend any V2 customers to start testing CDM V3 as soon as possible too. NOTE: This does not necessarily mean launching yourselves into CDM V3 right away. We need to stress that CDM V2 and V3 are different pieces of technology. Please take some time to test V3 properly to ensure it works in the way you expect with your local environment, applications and users. CDM V3 also has some different pre-requisites and configuration steps, so please ensure you consult the V3 documentation https://cdm.iamcloud.info rather than assuming deployment will be the same as V2. The good news is that V3 is in many ways easier to deploy and manage than V2 – so once you have familiarised yourself with V3 and our new configuration portal ‘Iris’ the upgrade itself should be quick and easy.
  3. Once you are satisfied CDM V3 passes your checks, start the deployment. Potentially consider a phased upgrade rather than big-bang if you have a larger environment and the ability to easily control this.When should you do this? Ideally in the next 6 months. Since 2.24 means that CDM V2 will continue working after RPS is removed the immediate pressure has been abated. So please don’t rush. But given the conversations we’ve had lately with Microsoft, it’s clear to us that there is significant uncertainty over the future of WebDAV. Moving to V3 is the only way to become truly future-proofed. And of course beyond mitigating those risks, CDM V3 is just a much more powerful product with an exciting roadmap of new features ahead that far exceed the capabilities of V2. The future is bright.

If you need any assistance please contact our support team at support@iamcloud.com