First published on MSDN on Jun 08, 2018
Final Update: Friday, 08 June 2018 01:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/08, 00:52 UTC. Our logs show the incident started on 06/07, 23:33 UTC and that during the 1 hour 19 Minutes that it took to resolve the issue approximately 42% of customers might have experienced failures while running queries on their Log analytics Logs
  • Root Cause: The failure was due to a configuration change.
  • Incident Timeline: 1 Hours & 19 minutes - 06/07, 23:33 UTC through 06/08, 00:52 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Venkat