This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 08 May 2020 08:29 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/08, 07:27 UTC. Our logs show the incident started on 05/08, 05:35 UTC and that during the 1 hour 52 minutes that it took to resolve the issue some of customers experienced data access issue in East US region.
-Satya
We've confirmed that all systems are back to normal with no customer impact as of 05/08, 07:27 UTC. Our logs show the incident started on 05/08, 05:35 UTC and that during the 1 hour 52 minutes that it took to resolve the issue some of customers experienced data access issue in East US region.
- Root Cause: The failure was due to one of our back end services.
- Incident Timeline: 1 Hour & 52 minutes - 05/08, 05:35 UTC through M/D, 07:27 UTC
-Satya
Initial Update: Friday, 08 May 2020 07:25 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in East US region.
-Satya
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in East US region.
- Work Around: None
- Next Update: Before 05/08 11:30 UTC
-Satya