IAM Cloud Outage History
IAM Cloud is up right nowIAM Cloud had 8 outages in the last 2 years totaling 2235h 5m of downtime — averaging 0.3 incidents per month.
There were 8 IAM Cloud outages since August 14, 2025 totaling 2235h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.
Cloud Drive Mapper - issue with authentication
Timeline · 2 updates
- 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
- 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
Legacy (CDM v2) license validation issue
Timeline · 3 updates
- 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
- 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
- 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
Microsoft service issue causing 503 ‘Service Unavailable’ responses from SharePoint API
Timeline · 2 updates
Cloud Drive Mapper - mapping groups unavailable
Timeline · 2 updates
- 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
- 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.
Microsoft : global cloud services failure impacting IAM Cloud
Timeline · 5 updates
Microsoft Azure failure impacting IAM Cloud services
Timeline · 4 updates
- 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
- 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
- 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
- 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