Is IAM Cloud down?

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

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

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

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.

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.