Microsoft: "Preliminary Root Cause: During the window of impact, an increase in utilisation was observed and this combined with the sudden loss of backend instance meant an operational threshold was reached. This in turn caused failures for customers and Azure services attempting to utilise Storage resources."
Microsoft Tracking ID: PLWV-BT0
Feb 26, 10:23 UTC
Microsoft has identified the underlying cause and are actively pursuing multiple mitigation workstreams and recovery is currently in progress.
We continue to monitor the Viedoc services, which are all as of now Operational.
Feb 26, 07:28 UTC
The issue has been resolved, monitoring and waiting on confirmation from Microsoft.
Feb 26, 07:06 UTC
An issue with Azure storage accessibility in Japan East has been identified at our service provider, Microsoft Azure. Microsoft is currently investigating the issue. https://status.azure.com/en-us/status
The issue impact Viedoc functionality such as export, file upload and PDF generation.
Updated 05:57 UTC
Microsoft has identified a possible root cause and are actively determining mitigation steps.
Updated 06:19 UTC
Feb 26, 05:25 UTC
We are currently investigating this issue.
Feb 26, 04:01 UTC