This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 21 February 2020 17:12 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/21, 16:33 UTC. Our logs show the incident started on 02/21, 14:52 UTC and that during the 1 Hours & 41 minutes that it took to resolve the issue some customers may have experienced data access issue in West US region .
-Anusha
We've confirmed that all systems are back to normal with no customer impact as of 02/21, 16:33 UTC. Our logs show the incident started on 02/21, 14:52 UTC and that during the 1 Hours & 41 minutes that it took to resolve the issue some customers may have experienced data access issue in West US region .
- Root Cause: The failure was due issues with one of our dependent service.
- Incident Timeline: 1 Hours & 41 minutes - 02/21, 14:52 UTC through 02/21, 16:33 UTC
-Anusha
Initial Update: Friday, 21 February 2020 16:50 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in West US region .
-Anusha
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in West US region .
- Work Around: None
- Next Update: Before 02/21 21:00 UTC
-Anusha