This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Monday, 06 January 2020 05:39 UTC
We've confirmed that all systems are back to normal with no customer impact as of 2020/01/06, 05:23 UTC. Our logs show the incident started on 2019/12/19, 10:00 UTC and that during the 18 days 19 hours 37 minutes that it took to resolve the issue some of customers in Azure China East 2 Region experienced issue while accessing data through Logs Blade in the Azure Portal.
-Monish
We've confirmed that all systems are back to normal with no customer impact as of 2020/01/06, 05:23 UTC. Our logs show the incident started on 2019/12/19, 10:00 UTC and that during the 18 days 19 hours 37 minutes that it took to resolve the issue some of customers in Azure China East 2 Region experienced issue while accessing data through Logs Blade in the Azure Portal.
- Root Cause: The failure was due to an issue with one of our dependent service.
- Incident Timeline: 18 days 19 Hours & 37 minutes - 2019/12/19, 10:00 UTC through 2020/01/06, 05:23 UTC
-Monish
Initial Update: Monday, 06 January 2020 04:38 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in Azure China may experience issue while accessing the data through the Logs blade.
-Monish
We are aware of issues within Log Analytics and are actively investigating. Some customers in Azure China may experience issue while accessing the data through the Logs blade.
- Next Update: Before 01/06 09:00 UTC
-Monish