This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 20 March 2020 06:36 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/20, 06:00 UTC. Our logs show the incident started on 03/20, 04:25 UTC and that during the 1 hour and 35 minutes that it took to resolve the issue some customers may have experienced data access, missed alerts, delayed alerts issue in Central US region.
-Madhuri
We've confirmed that all systems are back to normal with no customer impact as of 03/20, 06:00 UTC. Our logs show the incident started on 03/20, 04:25 UTC and that during the 1 hour and 35 minutes that it took to resolve the issue some customers may have experienced data access, missed alerts, delayed alerts issue in Central US region.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 1 Hour & 35 minutes - 03/20, 04:25 UTC through 3/20, 06:00 UTC
-Madhuri
Initial Update: Friday, 20 March 2020 05:51 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience data access, missed alerts, delayed alerts issue in Central US region.
-Madhuri
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience data access, missed alerts, delayed alerts issue in Central US region.
- Work Around: None
- Next Update: Before 03/20 10:00 UTC
-Madhuri