We've confirmed that all systems are back to normal with no customer impact as of 1/24, 22:15 UTC. Our logs show the incident started on 1/24, 21:35 UTC and that during the 40 minutes that it took to resolve the issue some of the customers using Azure Log Analytics and Azure Sentinel might have experienced issues accessing data as well as missed or delayed Log Search Alerts in East US 2 region.
Root Cause: The failure was due to one of the dependent services
Incident Timeline: 40 minutes - 1/24, 21:35 UTC through 1/24, 22:15 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.