This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Sunday, 23 January 2022 13:18 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/23, 12:45 UTC. Our logs show the incident started on 01/23, 11:07 UTC and that during the 1 hour and 38 minutes that it took to resolve the issue some customers using Azure Monitor and Azure Sentinel may have experienced issues accessing data as well as missed or delayed Log Search alerts in China East 2 region.
We've confirmed that all systems are back to normal with no customer impact as of 01/23, 12:45 UTC. Our logs show the incident started on 01/23, 11:07 UTC and that during the 1 hour and 38 minutes that it took to resolve the issue some customers using Azure Monitor and Azure Sentinel may have experienced issues accessing data as well as missed or delayed Log Search alerts in China East 2 region.
- Root Cause: The failure was due to one of our dependent service.
- Incident Timeline: 1 Hours & 38 minutes - 01/23, 11:07 UTC through 01/23, 12:45 UTC
-Anmol