IAM Cloud Outage History

Started Sep 23, 2026, 01:03 PM UTC· resolved Sep 26, 2026, 02:01 PM UTC

1. identified Sep 23, 2026, 01:03 PM UTC

   Microsoft Office & CDM breaking change: We are aware that the latest version of MS Office, released 22nd September contains a breaking change to CDM which could cause work to be lost. Source: Version 2609 , build 20430.20092 was released 22nd September 2026 via Current Channel updates and contains a version of MS Word which does not allow files to be saved correctly through Cloud Drive Mapper. Behaviour: The following workflows are potentially impacted: • Opening a Word document from a mapped drive and using Save As • Creating a document locally and saving it to a mapped drive • Using Save a Copy to a mapped drive Recommendation: Customers who have not yet updated Microsoft Office to Version 2609 (Build 20430.20092) should prevent or defer deployment of this Office build to devices using Cloud Drive Mapper. Customers who have already updated to the affected Office build should roll Microsoft 365 Apps back to the previous build (Version 2608 (Build 20326.20158)) and prevent Office from automatically updating to Version 2609 while the issue is being investigated. Fix: We have raised a Bug which our development teams are working on as a priority. We will provide an update once investigations have concluded as to how we will address the issue. Microsoft release notes for Office are here: https://learn.microsoft.com/en-us/officeupdates/current-channel

2. resolved Sep 26, 2026, 02:01 PM UTC

   Work over the weekend has identified that the issue has been resolved without intervention to CDM. No update to MS Office or changes to CDM are required. We believe a follow up backend fix from Microsoft has caused this behaviour. The incident is therefore considered closed; we will continue to monitor fix stability next week.

3. postmortem Sep 28, 2026, 07:26 AM UTC

   MS have confirmed the breaking change and the issue of a fix over the weekend. Microsoft admins can review the service status notification from MS here: [https://admin.cloud.microsoft/?#/servicehealth/:/alerts/OP1478558](https://admin.cloud.microsoft/?#/servicehealth/:/alerts/OP1478558) The text from this Microsoft advisory follows: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations Issue ID: OP1478558 Affected services: Microsoft 365 apps Status: Service degradation Issue type: Advisory Start time: Sep 24, 2026, 7:23 PM GMT\+1 More info This issue is reported to affect Microsoft Word version 2609, and some users report that version 2608 isn't affected. No error is presented and the file is instead saved to the “C:\\Users\\username\\AppData\\Local\\Microsoft\\Windows\\INetCache\\Content.MSO” folder with an incorrect file name. Additionally, this only reported to only impact converting Microsoft Word desktop app documents to PDFs using Save As and SharePoint Online as the location. While we're focused on remediation, users that have the option to save the file locally to their computer may use this to work around the problem. Additionally, using the Export to PDF function works as expected. Scope of impact This event may impact any user on version 2609 attempting to save Microsoft Word desktop app documents as PDFs to SharePoint Online. This information may be updated as our investigation continues. Root cause A recent Microsoft Word change relating to the Save As filename validation path to cloud-backed locations, which prevents the SharePoint save flow from completing and is causing impact. Current status Sep 25, 2026, 8:28 PM GMT\+1 We've confirmed that the issue is related to a recent Microsoft Word change affecting Save As filename validation for cloud-backed locations. This validation issue prevents the SharePoint save process from completing successfully during PDF conversion. We're actively deploying a change to disable the impacting behavior and expect this deployment to be completed by our next scheduled update. Next update by: Monday, September 28, 2026 at 10:00 PM GMT\+1

Read the full incident report →

Started Sep 21, 2026, 12:12 PM UTC· resolved Sep 21, 2026, 12:50 PM UTC

1. identified Sep 21, 2026, 12:12 PM UTC

   Incident Summary: We are aware of an issue with Cloud Drive Mapper authentication. Services affected: Cloud Drive Mapper Current impact: The existing authentication flow has been impacted. Users will be presented with a new Enterprise Application form consent request when logging into CDM. Latest resolution status: We are working on a fix for this issue. Fix ETA: Currently being tested, rollout dependent on test results. Next update 14:00 GMT

2. resolved Sep 21, 2026, 12:50 PM UTC

   Incident Summary: We are aware of an issue with Cloud Drive Mapper authentication. Services affected: Cloud Drive Mapper Current impact: A fix has been released. If an application consent request is showing when you start CDM, please restart and the service should operate as normal. If you are already working normally but have consented an additional Enterprise App, then please restart CDM and the new app can be removed. If you are working normally but have not consented any additional Apps today, then no action is required. Latest resolution status: Resolved

Read the full incident report →

Started Apr 15, 2026, 08:01 AM UTC· resolved Apr 15, 2026, 10:03 AM UTC

1. investigating Apr 15, 2026, 08:01 AM UTC

   Incident Summary: V2 (Legacy) – customers presented with license expiry notification Services affected: CDM v2 (Legacy) Current impact: We are aware of an issue with CDM v2 (legacy) license verification. Customers will be unable to access CDM v2 until a reset operation is performed. Latest resolution status: Impacted customers should raise a ticket via our helpdesk and a reset will be applied. We are working on root cause in order to apply a global fix. Fix ETA: 11:00 BST Next update: 10:30 BST

2. monitoring Apr 15, 2026, 08:44 AM UTC

   Incident Summary: V2 (Legacy) – customers presented with license expiry notification Services affected: CDM v2 (Legacy) Current impact: We are aware of an issue with CDM v2 (legacy) license verification. Customers will be unable to access CDM v2 until a reset operation is performed. Latest resolution status: We are in the process of rolling out a global fix, resolution state is being monitored. Fix ETA: 10:00 BST (complete) Next update: 10:30 BST

3. resolved Apr 15, 2026, 10:03 AM UTC

   Incident Summary: V2 (Legacy) – customers presented with license expiry notification Services affected: CDM v2 (Legacy) Current impact: None. Latest resolution status: The global fix has been applied and v2 customers are working as expected. Root cause investigations will continue. Fix ETA: n/a - fix complete Next update: n/a - fix complete

Read the full incident report →

Started Mar 18, 2026, 05:22 PM UTC· resolved Mar 20, 2026, 10:32 AM UTC

1. investigating Mar 18, 2026, 05:22 PM UTC

   Incident Summary: We are currently observing an elevated rate of 503 'Service Unavailable' responses impacting CDM. Microsoft have confirmed that this is not expected behaviour and forms part of an ongoing investigation within the Microsoft Commercial Cloud service. Root cause is attributed to Microsoft service-side. IAM Cloud Services Affected: Cloud Drive Mapper, v3.x versions Current Impact: Multiple customers are experiencing repeated 503 responses leading to performance degradation. The issue is being experienced globally, although not consistently across all tenancies. It is important to note that this issue is distinct from throttling. Microsoft have confirmed that throttling mechanics have not changed and that excessive calls to MS Graph will still generate 429 ‘Too Many Requests’ responses prior to 503 ‘Service Unavailable’ errors being generated. For users impacted by the current issue, there are no 429 errors returned, and our investigations show that tenancy-level MS traffic limits are not being exceeded. The 503s are unexpected and are abnormal. Resolution Status: We have escalated the issue with Microsoft to the highest possible level based on customer impact. Microsoft has acknowledged the issue and confirmed an active investigation. No estimated time for resolution has been provided. Recommended Action: Please contact our Support Desk if you are being impacted by this issue. We encourage customers to raise support requests direct with Microsoft to ensure their tenant impact is captured as part of the ongoing investigation. When contacting Microsoft Support, we recommend referencing the ‘ongoing internal Microsoft Engineering team investigation into an unexpected increase in 503 responses in SharePoint Online calls in Commercial Cloud beginning in the last week of February’. Fix ETA: As yet Microsoft have not provided a fix ETA. Next update: We are continuing to monitor the situation closely and will provide updates as Microsoft shares further information.

2. resolved Mar 20, 2026, 10:32 AM UTC

   Our telemetry suggests that erroneous 503s and therefore CDM performance have returned to normal levels. Although MS have not confirmed, this strongly suggests that a backend change has been made to correct the issue. We will continue to work with MS to understand what cause the service-side issue, although this may not be conclusive. If you continue to experience issues with 503 errors then please contact our Support Desk.

Read the full incident report →

Started Feb 17, 2026, 02:26 PM UTC· resolved Feb 17, 2026, 05:15 PM UTC

1. investigating Feb 17, 2026, 02:26 PM UTC

   Incident Summary: We are currently investigating an issue with CDM v3.19 and below whereby mapping groups are unavailable. Impacted customers are recommended to update to v3.22 where possible as this version is not affected. Services affected: Cloud Drive Mapper v3.19 and below Current impact: Users on v3.19 and below will not receive their mapping groups when using CDM. Latest resolution status: Critical Incident team is mobilised and are working on a fix. Fix ETA: TBC at present Next update: 15.30

2. resolved Feb 17, 2026, 05:15 PM UTC

   Incident Summary: CDM users on versions v3.19 and below cannot use mapping groups. Services affected: Cloud Drive Mapper v3.19 and below Current impact: None Latest resolution status: Service has been restored by rolling back a Release made this afternoon to our API. Fix ETA: Change rollback completed at 15:10. Next update: N/a. Root Cause Analysis and Critical Incident follow up are initiated.

Read the full incident report →

Started Oct 29, 2025, 04:15 PM UTC· resolved Oct 29, 2025, 10:07 PM UTC

1. identified Oct 29, 2025, 04:15 PM UTC

   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

2. identified Oct 29, 2025, 05:23 PM UTC

   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

3. identified Oct 29, 2025, 07:14 PM UTC

   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

4. monitoring Oct 29, 2025, 09:16 PM UTC

   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

5. resolved Oct 29, 2025, 10:07 PM UTC

   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

Read the full incident report →

Started Oct 09, 2025, 09:30 AM UTC· resolved Oct 09, 2025, 02:17 PM UTC

1. investigating Oct 09, 2025, 09:30 AM UTC

   Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: CDM users will be experiencing a intermittent service with possible degraded performance Iris users cannot use the service to administer users or tenancies Latest resolution status: We are observing a significant Microsoft issue which is impacting IAM Cloud. We are currently monitoring the issue but are reliant on Microsoft to restore service. Fix ETA: Dependent on Microsoft Next update: 12:00

2. monitoring Oct 09, 2025, 09:53 AM UTC

   Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: CDM users will be experiencing a intermittent service with possible degraded performance Iris users cannot use the service to administer users or tenancies Latest resolution status: We are currently monitoring the issue but are reliant on Microsoft to restore service. https://admin.cloud.microsoft/?#/servicehealth/:/alerts/MO1168665 Fix ETA: Dependent on Microsoft Next update: 12:30

3. monitoring Oct 09, 2025, 12:13 PM UTC

   Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: CDM and Iris performance is largely restored to normal following MS rollout of remediation to affected Azure Front Door resources Latest resolution status: MS estimate that 96% of impacted resources have now been recovered. Fix ETA: Dependent on Microsoft Next update: 15:00

4. resolved Oct 09, 2025, 02:17 PM UTC

   Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: Services are available as normal Latest resolution status: MS state that all primary resources are now recovered; Azure customers using Azure Front Door (AFD) should see consistent availability, with slightly higher latencies decreasing as additional resources are recovered Fix ETA: Resolved Next update: n/a

Read the full incident report →

Started Aug 14, 2025, 09:51 PM UTC· resolved Nov 10, 2025, 02:41 PM UTC

1. identified Aug 14, 2025, 09:51 PM UTC

   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.

2. monitoring Aug 15, 2025, 10:55 AM UTC

   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. 3) 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.

3. monitoring Aug 15, 2025, 06:48 PM UTC

   We are continuing to monitor for any further issues.

4. monitoring Aug 18, 2025, 08:26 AM UTC

   We are continuing to monitor for any further issues.

5. monitoring Oct 21, 2025, 09:11 PM UTC

   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.

6. monitoring Oct 24, 2025, 03:21 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Nov 10, 2025, 02:41 PM UTC

   Microsoft rollout of RPS Hard Enforcement: Microsoft have confirmed that rollout of RPS hard enforcement reached 100% as at 7th November. We are resolving this incident as all impacted, active customers are now using a protected v2 version, or have migrated to v3. We would like to thank our customers for supporting our efforts to minimise the impact of this MS change.

Read the full incident report →

Started Jul 30, 2025, 04:06 PM UTC· resolved Jul 30, 2025, 04:06 PM UTC

1. resolved Jul 30, 2025, 04:06 PM UTC

   Over the coming 4 weeks we are going to be enabling email-based MFA on our Iris portal. This will happen in several phases over the coming weeks. There isn't anything you need to do, as it will be enabled automatically. If you run into any issues, or temporarily need to disable it, please contact our support team at [email protected] Many thanks, The IAM Cloud team

Read the full incident report →

Started Jul 16, 2025, 07:46 AM UTC· resolved Jul 17, 2025, 09:42 PM UTC

1. investigating Jul 16, 2025, 07:46 AM UTC

   We have received reports of Cloud Drive Mapper V3 not being able to authenticate. Upon further analysis, the problem is with the connection to Microsoft Graph API. We have logged a case with Microsoft and encourage affected clients to do the same.

2. investigating Jul 16, 2025, 08:47 AM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: Multiple regions impacted. A subset of CDM v3 customers are affected. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing. Latest resolution status: Initial investigations suggest a change to the authentication token provision via Microsoft. A support ticket has been raised. Testing is ongoing to further corroborate this analysis. Fix ETA: Dependent on root cause Next update: 11:00 BST

3. investigating Jul 16, 2025, 10:21 AM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: Multiple regions impacted. A subset of CDM v3 customers are affected. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: Investigations suggest a change to Azure AD authentication token provision by Microsoft is causing the issue. We are actively working with Microsoft engineers in order to provide a definitive diagnosis. Fix ETA: Dependent on root cause Next update: 13:00 BST

4. investigating Jul 16, 2025, 12:04 PM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: Multiple regions impacted. A subset of CDM v3 customers are affected. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: Investigations suggest a change to Azure AD authentication token provision by Microsoft is causing the issue. The case has now been escalated within Microsoft following initial meetings between engineering teams. Fix ETA: Dependent on root cause Next update: 15:00 BST

5. investigating Jul 16, 2025, 03:59 PM UTC

   We are continuing to investigate this issue.

6. investigating Jul 16, 2025, 04:09 PM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: The number of affected customers has not changed significantly since our previous update whereby a small subset of the overall customer base is affected. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: A series of meetings have been held with Microsoft engineers. Investigations have confirmed a change to the IDP mechanism for token generation which has caused the impact to M365 authentication through CDM. MS have escalated the case internally to the highest level possible in order to conclude if this is an intentional state or an error. We are continuing to assist MS with their investigations wherever possible and will determine actions required to restore service once MS provide a definitive position on the IDP change. Fix ETA: Dependent on root cause confirmation. Next update: Aligned with Microsoft confirmation of IDP change.

7. investigating Jul 17, 2025, 08:18 AM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: The number of affected customers is incrementally increasing since our previous update, which suggests an MS global change continues to be rolled out. Impact remains limited to a subset of the overall customer base - i.e. is not affecting all customers at this time. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: Investigations have confirmed a change to the IDP mechanism for token generation which has caused the impact to M365 authentication through CDM. No response has been received from Microsoft since the last update, contrary to their committed response timeframes. We are independently developing a hotfix in the absence of definitive information from MS in order to restore service to impacted customers. Fix ETA: Dependent on hotfix completion and successful testing. Next update: 11:00 BST

8. investigating Jul 17, 2025, 10:07 AM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: The number of affected customers continues to incrementally increase. Impact remains limited to a subset of the overall customer base - i.e. is not affecting all customers at this time. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: Investigations have confirmed a change to the IDP mechanism for token generation which has caused the impact to M365 authentication through CDM. Microsoft Product Group have now confirmed that this is a Bug. We are continuing to work with MS to understand their intended approach to address the issue and indicative timescales. We have also asked for MS to formally document and publish information regarding the Bug. Service restoration remains our priority. Although the number of new customers impacted may now slow, we have no indication of fix timescales, therefore we continue to work on a hotfix to supply to impacted customers. Testing will include regressive compatibility to incorporate any MS decision to rollback their change to the previous state. Fix ETA: Dependent on hotfix completion and successful testing. Next update: 13:00 BST

9. identified Jul 17, 2025, 12:28 PM UTC

   Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: The number of affected customers continues to incrementally increase. Impact remains limited to a subset of the overall customer base - i.e. is not affecting all customers at this time. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: Investigations have confirmed a change to the IDP mechanism for token generation which has caused the impact to M365 authentication through CDM. Microsoft Product Group have confirmed that this is a Bug. They have confirmed that it remains under active investigation but have yet to provide timescales for a fix (ETA) or documentation (RCA). Service restoration remains our priority. We are progressing with the development and testing of a fix that can be supplied to impacted customers. Fix ETA: Dependent on hotfix completion and successful testing. Next update: 17:00 BST

10. monitoring Jul 17, 2025, 02:44 PM UTC

    Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: The number of affected customers continues to incrementally increase. Impact remains limited to a subset of the overall customer base - i.e. is not affecting all customers at this time. For impacted customers, CDM cannot be used; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: A fix is now being distributed to all affected customers and will be made available to any customers who are newly impacted from this point. Our Support team is contacting customers individually to provide an updated version. Microsoft Product Group have confirmed that this is a Bug. They have confirmed that it remains under active investigation but have yet to provide timescales for a fix (ETA) or documentation (RCA). We are continuing to work with MS and the case has now been escalated to the Critical Situation Management Team (CritSit). Fix ETA: In distribution. Next update: 17:00 BST

11. monitoring Jul 17, 2025, 04:30 PM UTC

    Incident Summary: Authentication with M365 through CDM is currently failing. Services affected: Cloud Drive Mapper v3 Current impact: A subset of the overall customer base has been impacted by the MS Bug. Affected customers cannot use CDM; signin to the product is possible but the downstream authentication to M365 via MS Graph is failing (MS Graph is rejecting the Azure AD generated token). Latest resolution status: A fix is has been distributed to all affected customers and will be made available to any customers who are newly impacted from this point. Microsoft Product Group have confirmed that this is a Bug. The case remains with the Critical Situation Management Team (CritSit). We will continue to request information concerning the intended response, and for a formal Root Cause Analysis to be published. Fix ETA: Distributed. Next update: As required - we will continue to monitor impacted customers to ensure service has been successfully restored.

12. monitoring Jul 17, 2025, 09:41 PM UTC

    Incident Summary: Authentication with M365 through CDM is failing. Services affected: Cloud Drive Mapper v3 Current impact: None expected. Latest resolution status: Microsoft have confirmed that a global fix has been rolled out. - Customers who did not experience any impact remain unaffected. - Customers who were impacted but did not move to the fix version are advised to restart CDM and resume working as normal. - Customers who mass deployed the fix version will be contacted with our recommended next steps. Fix ETA: n/a - bug fix has been issued by MS Next update: n/a - issue resolved

13. resolved Jul 17, 2025, 09:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Apr 21, 2025, 10:13 AM UTC· resolved Apr 22, 2025, 04:40 PM UTC

1. investigating Apr 21, 2025, 10:13 AM UTC

   This is reoccurrence of the previous issue on the 18th April. Incident Summary: The legacy CDM Portal (portal.iamcloud.net) has been classified as unsafe when using Chrome, FireFox maybe affected too. Services affected: Legacy CDM (v2) Current impact: CDM v2 administrators will be unable to reach the Portal if using Chrome and potentially FireFox. Our suggested workaround is to use a different browser (e.g. Edge). Latest resolution status: A workaround is currently available. We have provided feedback to the browser vendors to inform them that the site has been incorrectly classified as unsafe. Next update: TBC

2. investigating Apr 22, 2025, 10:11 AM UTC

   This is reoccurrence of the previous issue on the 18th April. Incident Summary: The legacy CDM Portal (portal.iamcloud.net) has been incorrectly classified as unsafe by the Google Safe Browsing service when using the Chrome and Firefox browsers. Services affected: Legacy CDM (v2) Current impact: CDM v2 administrators will be unable to reach the Portal if using Chrome or Firefox. Our suggested workaround is to use a different browser (e.g. Edge). Latest resolution status: A workaround is currently available. We have provided feedback to Google to inform them that the site has been incorrectly classified as unsafe. However, due to the issue having surfaced multiple times, we expect that it may reoccur after the next correction is made. We have initiated additional work to provide a permanent fix which we hope to be in place by the end of the week. Next update: 17:00 or when resolved

3. resolved Apr 22, 2025, 04:40 PM UTC

   This incident has been resolved now, however we're continuing to work on a long term fix.

Read the full incident report →

Started Apr 17, 2025, 10:33 AM UTC· resolved Apr 18, 2025, 06:33 AM UTC

1. investigating Apr 17, 2025, 10:33 AM UTC

   This is reoccurrence of the previous issue on the 7th April. Incident Summary: The legacy CDM Portal (portal.iamcloud.net) has been classified as unsafe when using Chrome & Firefox browsers Services affected: Legacy CDM (v2) Current impact: CDM v2 administrators will be unable to reach the Portal if using Chrome or Firefox. Our suggested workaround is to use a different browser (e.g. Edge). Latest resolution status: A workaround is currently available. We have provided feedback to the browser vendors to inform them that the site has been incorrectly classified as unsafe. Next update: 12:30

2. identified Apr 17, 2025, 11:03 AM UTC

   We have revalidated the domain and are awaiting propagation.

3. identified Apr 17, 2025, 01:25 PM UTC

   We are still waiting for the propagation to replicate. Latest resolution status: Edge can be used. Next update: When the issue is resolved.

4. identified Apr 17, 2025, 02:11 PM UTC

   We are continuing to work on a fix for this issue.

5. identified Apr 17, 2025, 02:16 PM UTC

   We have revalidated the domain with Google. Next update: 16:15

6. identified Apr 17, 2025, 03:31 PM UTC

   No status change. Next update: When the issue is resolved.

7. monitoring Apr 17, 2025, 04:38 PM UTC

   We have revalidated the domain with Google. Googles process documentation states that it can be a couple of days before verification is processed. We will continue to monitor the situation and we ask that affected Admins use Microsoft Edge while this issue persists.

8. resolved Apr 18, 2025, 06:33 AM UTC

   The issue is now resolved and users can access the legacy Portal as normal via Chrome and Firefox. Thank you for your patience whilst Google corrected the unsafe site classification.

Read the full incident report →

Started Apr 02, 2025, 08:26 AM UTC· resolved Apr 02, 2025, 10:21 AM UTC

1. investigating Apr 02, 2025, 08:26 AM UTC

   A Subset of users may experience problems authenticating to the IAM Cloud Platform. Engineers are working to resolve this issue as a priority and we will provide further updates ASAP. We apologise for the inconvenience. IAM Cloud Technical Support http://support.iamcloud.com [email protected] Phone (UK): +44 118 324 0000

2. monitoring Apr 02, 2025, 09:03 AM UTC

   We have rolled out a mitigation and are monitoring the impact. We are working with affected customers to ensure the validity of the fix.

3. resolved Apr 02, 2025, 10:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 01, 2025, 03:32 PM UTC· resolved Apr 01, 2025, 04:55 PM UTC

1. investigating Apr 01, 2025, 03:32 PM UTC

   Users in the US region are unable to login to the IAM Cloud Portal. We are investigating and apologize for any inconvenience caused.

2. identified Apr 01, 2025, 04:12 PM UTC

   The issue has been identified and a fix will be implemented within the next hour.

3. resolved Apr 01, 2025, 04:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 13, 2025, 01:09 PM UTC· resolved Mar 13, 2025, 02:11 PM UTC

1. investigating Mar 13, 2025, 01:09 PM UTC

   We are aware of an issue affecting customers where they are unable to edit mapping groups in our admin portal, Iris. We are investigating this at the moment and the team is actively working on this. Update will be provided in 1 hour.

2. resolved Mar 13, 2025, 02:11 PM UTC

   The team has identified an issue in a release where mapping groups configuration failed via Iris. We have patched the release and validated the fix. We are putting in mitigation for this defect in future release testing. Mapping group editing is now restored on services. Thank you for your patience.

Read the full incident report →

Started Jan 13, 2025, 08:40 PM UTC· resolved Jan 13, 2025, 09:03 PM UTC

1. investigating Jan 13, 2025, 08:40 PM UTC

   A subset of users in the US region may experience problems authenticating to the IAM Cloud Platform. Engineers are working to resolve this issue as a priority and we will provide further updates ASAP. We apologise for the inconvenience. IAM Cloud Technical Support http://support.iamcloud.com [email protected] Phone (UK): +44 118 324 0000

2. resolved Jan 13, 2025, 09:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2024, 10:54 AM UTC· resolved Feb 05, 2025, 02:11 PM UTC

1. monitoring Nov 18, 2024, 10:54 AM UTC

   We have become aware of an upcoming issue whereby users with WebDAV-based mapped OneDrive and SharePoint drives are unable to open .pptx files. This is currently manifesting in Preview Channel MS Office versions progressing through the Microsoft Beta program. This issue is introduced in MS Office version 2411. If you currently use WebDAV-based mapped drives to access networked .pptx files, and are due to receive this Office version as part of Microsoft's standard release process, then our testing indicates that the file access will fail. We have tested our v2.x CDM client (which uses WebDAV) with the upcoming Office version and have found that our service is also impacted; i.e. CDM-initiated .pptx file operations will also fail for users who receive and install Office version 2411. Note that impact to CDM users is conditional on; - The upcoming Office version 2411 - File operations that take place on .pptx file types (earlier PowerPoint files are not affected) Users who do not move to the impacted Office version or do not interact with .pptx files in this way should not be affected. Should our understanding of this impact change through further testing we will inform you via this Status Page. We have reached out to Microsoft through various channels to inform them of this breaking change. At present we do not have an accurate time scale as to when Office users (and therefore downstream CDM users) may be impacted as this is dependent on Microsoft's rollout schedules and your own upgrade processes. You may wish to postpone upgrading to MS Office 2411 if possible to avoid potential impacts, and to provide more time for Microsoft to issue a fix or to plan service migration to CDM v3. For customers who are concerned that they fall within the impacted population we can provide mitigation through migration to our Pre-release v3 client, which is not impacted by the MS Office v2411 change. Customers who wish to migrate will be able to fully test the v3 client to ensure our Pre-release version meets operational requirements. Should you wish to discuss this option then please contact us via [email protected]. For those customers who may not wish to migrate to v3 yet or have functional requirements which are not yet met by v3 there are two main options available; 1) Access .pptx files via a web browser 2) Report issues to Microsoft Support if you become impacted by the Office 2411 version release It is important to note that this issue relates to the relationship between Microsoft’s WebDAV and PowerPoint components and is not specific to CDM v2. CDM v2 is impacted due to its usage of the WebDAV protocol which v3 does not rely on and is therefore not affected. Our summary of the issue is below; this may assist describing the issue to Microsoft should you require; If you open a drive mapped via Microsoft Edge’s "View in File Explorer” function when browsing SharePoint Online (this is the manual way of creating a WebDAV-based drive in Windows), from that drive you cannot open PowerPoint files if you have upgraded to Office 2411. When opening a .pptx you will be given a message stating 'Sorry, PowerPoint can't read 'path and file name'.pptx'

2. monitoring Jan 20, 2025, 02:28 PM UTC

   Update as of 20/01: 2411 and 2412 are now in the current channel. The issues is still present on these versions. We have also tested 2501 and 2502, these still have the issue too. We're still engaging with Microsoft in order to ascertain further information on this issue. The current options are: Use PowerPoint online; Open PowerPoint locally then, Open > Browse > This PC; Use the pre release version of CDM V3. If you are not already in this program let us know and we can get you set up. Details are on - https://www.iamcloud.com/iam-blog/news-cdm-v3-pre-release-update/ and cdm.iamcloud.info. If you have a Microsoft sales or support representative please let them know about this issue linking our status above as an explanation. We would be happy to engage with them and link them to our own open ticket to bring this to a successful resolution. If you have any further questions then please contact [email protected].

3. monitoring Jan 27, 2025, 08:26 AM UTC

   Version 2501 (Build 18429.20088) is now in the current channel, this has been tested and so far it is not affected by the issue. We're continuing to monitor the situation and are still engaging with Microsoft on this. If that version of Office isn't available to you, a work around is to add your tenant address to the registry as instructed in this guide - https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/credentials-prompt-access-webdav-fqdn-sites This allows PowerPoint files to open normally from the mapped drives.

4. resolved Feb 05, 2025, 02:11 PM UTC

   This incident has been resolved.

Read the full incident report →