First published on MSDN on Oct 08, 2018
Final Update: Monday, 08 October 2018 11:11 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/08, 10:40 UTC. Our logs show the incident started on 10/08, 07:40 UTC and that during the 3 hours that it took to resolve the issue some customers would have experienced data access issues in Azure and OMS Portal.
  • Root Cause: The failure was due to issues in one our dependent platform services.
  • Incident Timeline: 3 Hours - 10/08, 07:40 UTC through 10/08, 10:40 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Mohini Nikam
Update: Monday, 08 October 2018 09:58 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience data access issues in the Azure and OMS Portal. Initial findings indicate that the problem began at 10/08 07:40 UTC.
  • Work Around: None
  • Next Update: Before 10/08 12:00 UTC

We are working hard to resolve this issue and apologize for any inconvenience.

-Mohini
Initial Update: Monday, 08 October 2018 08:22 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issues in the Azure and OMS portal.
  • Work Around: None
  • Next Update: Before 10/08 10:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Mohini