This article is contributed. See the original author and article here.

Final Update: Tuesday, 10 November 2020 17:48 UTC

We’ve confirmed that all systems are back to normal with no customer impact as of 11/10, 17:28 UTC. Our logs show the incident started on 11/10, 16:35 UTC and that during the 53 minutes that it took to resolve the issue customers may have experienced intermittent data latency for these data types in the West Central US region: 

HEALTHASSESSMENTBLOB
SECURITYEVENTBLOB
TENANTMICROSOFTAADIAMNONINTERACTIVE
GENERICPERFBLOB
LINUXPERFBLOB
SECURITYCEFBLOB
TENANTMICROSOFTAADIAMSP
TENANTMICROSOFTAADIAMMSI
MICROSOFTOPERATIONALINSIGHTSAUDIT
MICROSOFTSYNAPSESYNAPSEGATEWAYEVENTS

  • Root Cause: The failure was due to a bad deployment.
  • Incident Timeline: 53 minutes – 11/10, 16:35 UTC through 11/10, 17:28 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

%d bloggers like this: