This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 22 April 2020 10:09 UTC
We've confirmed that all systems are back to normal with no customer impact as of 4/22,08:40 UTC. Our logs show the incident started on 4/22, 06:50 UTC and that during the 1 hour and 50 minutes that it took to resolve the issue some customers in North Central US region may have experienced Data Latency, Delayed or missed log search alerts and issue performing CRUD operations against Log Analytics Workspace.
-Madhuri
We've confirmed that all systems are back to normal with no customer impact as of 4/22,08:40 UTC. Our logs show the incident started on 4/22, 06:50 UTC and that during the 1 hour and 50 minutes that it took to resolve the issue some customers in North Central US region may have experienced Data Latency, Delayed or missed log search alerts and issue performing CRUD operations against Log Analytics Workspace.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 1 Hour & 50 minutes - 4/22, 06:50 UTC through 4/22, 08:40 UTC
-Madhuri