IAM Cloud Status

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Microsoft rollout of RPS Hard Enforcement

Prior to October 20th Per our previous Status Page communications, Microsoft are now moving to permanently enforce deprecation of the legacy authentication protocol Relying Party Suite (RPS).

The original MS communication can be found here: https://mc.merill.net/message/MC1097272

Soft Enforcement commenced August 14th and completed on the 5th September. Impacted IAM Cloud customers had 3 options to protect service during this time;

•    Update v2 to a protected version (v2.23 or greater)
  

•    Remain sub 2.23 but execute the IAM Cloud-provided script which regressed the MS change and allowed communication to continue via RPS
  

•    Migrate to v3
  

20th October onwards Microsoft have now commenced Hard Enforcement of the RPS change; the protocol can no longer be re-enabled and is permanently deprecated.

For IAM Cloud users, this means the following;

•    CDM versions prior to v2.23 are no longer considered as supported. Versions below 2.23 have been rendered non-functional by the RPS change and therefore we cannot continue to provide break fix / troubleshooting support
  

•    For customers now experiencing service disruption on versions prior to 2.23 and who wish to remain on v2, update to v2.25 is required. Customers can follow this link - https://downloads.iamcloud.net/cdm/legacy/releases-latest/setupcdmx64.msi
  

•    Alternatively, customers can migrate to the latest CDM v3 release, which is available via Iris. CDM v3 is unaffected by the RPS changes. However, we do not recommend rushing migration as v3 is different technology to v2 and requires a greater level of pre-deployment testing. More details on CDM v3 can be found here - https://cdm.iamcloud.info/docs/Content/Upgrade/Upgrade_WithTiles.htm
  

We are providing support as normal to all users on v2.23+ and v3. Please also contact us should you require assistance updating or migrating your current version.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Microsoft is currently making a change to its RPS service within SharePoint Online that can stop CDM V2's authentication and ability to map drives.

There are three things you can do to resolve the issue:

1. Upgrade CDM V2 to our latest build CDM 2.24 (download available at https://resources.iamcloud.net). CDM 2.24 doesn't require RPS to authenticate, and is a permanent fix to this issue.

2. If your tenancy has already been hit by the change in the RPS service and you are under pressure to get colleagues back up and running ASAP, there is a simple fix you can do to temporarily resolve the issue: re-enable RPS.

How to re-enable RPS using PowerShell:

Download this script: https://downloads.iamcloud.net/cdm/legacy/scripts/LegacyAuthProtocol.ps1

You need to be a Microsoft 365 Global Admin to run it successully, and please ensure you are using PowerShell version 5.x (not 7.x).

Run the script.

Provide your SharePoint domain prefix (e.g. example for example-admin.sharepoint.com)

The script works by setting the following property on your tenancy using SharePoint REST:

AllowLegacyBrowserAuthProtocolsEnabledSetting $true

Once you've run this, all versions of CDM V2 should start working again. But this is temporary, and will only work until 15th October 2025, when Microsoft have informed us they will start to remove RPS entirely (Hard Enforcement). As such, we still recommend upgrading to 2.24 as soon as possible too.

1. Upgrade to CDM V3 - which is unaffected by these changes. However we don't recommend you rush this, as V3 is different technology to V2 and requires more substantial testing in your environment before deployment.

As such our recommendation would be for all V2 customers to upgrade to 2.24 ASAP, which should be a relatively simple update, then start their journey with testing V3, ready for a potential roll-out within the next few months.

Identified: We are aware of a change Microsoft is making to its RPS service within SharePoint Online that can break CDM V2's authentication and ability to map drives.

We have more information on this coming soon.

Resolved: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Microsoft confirm that mitigation has been applied and recovery is being monitored. At the time of update, this may take another 80 minutes for MS to fully rollout.

The majority of customers report service restoration. A small number may continue to experience service intermittency until global Microsoft recovery completes, which is estimated by 23:20 UTC.

Latest resolution status: Mitigated with full recovery estimated by MS circa 23:20 UTC

Fix ETA: n/a

Next update: n/a. We will review the MS Post Incident Review document once published

Monitoring: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Testing suggests that MS services are recovered.

A number of impacted customers are reporting CDM is now operational following a restart. We cannot definitively conclude global recovery but this would indicate that restoration is in effect.

Iris is now available.

Latest resolution status: Thought resolved - we will continue to confirm with customers who have reported a service impact.

Fix ETA: Thought resolved.

Next update: 22:00

Identified: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Microsoft cloud services are experiencing a significant worldwide outage, including impacts to M365 and Azure.

Microsoft’s Azure status page is citing DNS issues, starting at 16:00.

This service outage has a direct impact on CDM v3 and the availability of the Iris management portal. Users with an active CDM session may be able to continue working with limited functionality. Users without an active session will not be able to use CDM.

Latest resolution status: The MS status page is now up with details on the current service impacts. They state:

"At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025"

https://status.cloud.microsoft/

Fix ETA: 23:20 UTC (MS estimate)

Next update: 21:00

Identified: Incident Summary: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Microsoft cloud services are experiencing a significant worldwide outage, including impacts to M365 and Azure.

Microsoft’s Azure status page is citing DNS issues, starting at 16:00.

This service outage has a direct impact on CDM v3 and the availability of the Iris management portal. Users with an active CDM session may be able to continue working with limited functionality. Users without an active session will not be able to use CDM.

Latest resolution status: Reliant on MS.

We will continue to monitor Microsoft services and conduct internal testing.

Fix ETA: Reliant on MS.

Next update: 19:00

Identified: Incident Summary: Global service impact due to MS Azure failure

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Iris is unavailable
CDM cannot validate license on login; service is therefore unavailable

Latest resolution status: Reliant on MS. This is symptomatic of the previous Microsoft outage on October 9th where Azure Front Door was unavailable.

Fix ETA: Reliant on MS.

Next update: 18:00

Resolved: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Microsoft confirm that mitigation has been applied and recovery is being monitored. At the time of update, this may take another 80 minutes for MS to fully rollout.

The majority of customers report service restoration. A small number may continue to experience service intermittency until global Microsoft recovery completes, which is estimated by 23:20 UTC.

Latest resolution status: Mitigated with full recovery estimated by MS circa 23:20 UTC

Fix ETA: n/a

Next update: n/a. We will review the MS Post Incident Review document once published

Monitoring: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Testing suggests that MS services are recovered.

A number of impacted customers are reporting CDM is now operational following a restart. We cannot definitively conclude global recovery but this would indicate that restoration is in effect.

Iris is now available.

Latest resolution status: Thought resolved - we will continue to confirm with customers who have reported a service impact.

Fix ETA: Thought resolved.

Next update: 22:00

Identified: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Microsoft cloud services are experiencing a significant worldwide outage, including impacts to M365 and Azure.

Microsoft’s Azure status page is citing DNS issues, starting at 16:00.

This service outage has a direct impact on CDM v3 and the availability of the Iris management portal. Users with an active CDM session may be able to continue working with limited functionality. Users without an active session will not be able to use CDM.

Latest resolution status: The MS status page is now up with details on the current service impacts. They state:

"At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025"

https://status.cloud.microsoft/

Fix ETA: 23:20 UTC (MS estimate)

Next update: 21:00

Identified: Incident Summary: Microsoft cloud services : global outage

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Microsoft cloud services are experiencing a significant worldwide outage, including impacts to M365 and Azure.

Microsoft’s Azure status page is citing DNS issues, starting at 16:00.

This service outage has a direct impact on CDM v3 and the availability of the Iris management portal. Users with an active CDM session may be able to continue working with limited functionality. Users without an active session will not be able to use CDM.

Latest resolution status: Reliant on MS.

We will continue to monitor Microsoft services and conduct internal testing.

Fix ETA: Reliant on MS.

Next update: 19:00

Identified: Incident Summary: Global service impact due to MS Azure failure

Regions impacted: Global

Services affected: CDM v3 Iris

Current impact: Iris is unavailable
CDM cannot validate license on login; service is therefore unavailable

Latest resolution status: Reliant on MS. This is symptomatic of the previous Microsoft outage on October 9th where Azure Front Door was unavailable.

Fix ETA: Reliant on MS.

Next update: 18:00