Final Update: Monday, 01 June 2020 22:43 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/1, 21:50 UTC. Our logs show the incident started on 6/1, 12:05 UTC and that during the 9 hours and 45 minutes that it took to resolve the issue 33% of customers experienced possible query execution errors, as well as the misbehavior or alerts configured in Log Search alerts, and Smart Detection alerts.
- Root Cause: The failure was due to a backend service getting into a bad state.
- Incident Timeline: 9 Hours & 45 minutes - 6/1, 12:05 UTC through 6/1, 21:50 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Jeff