This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 19 February 2020 14:50 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/19, 12:30 UTC. Our logs show the incident started on 02/19, 11:30 UTC and that during the one hour that it took to resolve the issue Customers using Log Search Alerts may have experienced delayed or missed Log Search Alerts or may had issues with creating Log Search Alert rules in West Central US.
-Anusha
We've confirmed that all systems are back to normal with no customer impact as of 02/19, 12:30 UTC. Our logs show the incident started on 02/19, 11:30 UTC and that during the one hour that it took to resolve the issue Customers using Log Search Alerts may have experienced delayed or missed Log Search Alerts or may had issues with creating Log Search Alert rules in West Central US.
- Root Cause: The failure was due to issues with one of the dependent services.
- Incident Timeline: 01 Hours - 02/19, 11:30 UTC through 02/19, 12:30 UTC
-Anusha