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

Final Update: Wednesday, 27 January 2021 13:35 UTC

We’ve confirmed that all systems are back to normal with no customer impact as of 01/27, 13:00 UTC. Our logs show the incident started on 01/25, 08:00 UTC and that during the 2 Days & 5 Hours that it took to resolve the issue some of customers experienced “No Data found” message or may not be able to get data while looking at the logs.
  • Root Cause: The failure was due to backend service.
  • Incident Timeline: 2 Days & 5 Hours – 01/25, 08:00 UTC through 01/27, 13:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Madhav

Initial Update: Wednesday, 27 January 2021 10:37 UTC

We are aware of issues within Azure Log Analytics and are actively investigating. Some customers may view “No Data found” message or may not be able to get data while looking at the logs.
  • Work Around: The data can be queried from workspace directly incase user have access to it.
  • Next Update: Before 01/27 15:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Mohini

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

%d bloggers like this: