This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Sunday, 15 May 2022 13:56 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/15, 13:15 UTC. Our logs show the incident started on 05/15, 12:40 UTC and that during the 35 minutes that it took to resolve the issue, Some of the customers using Log Analytics may have experienced data access issue and delayed or missed alerts in West Europe region. Some customers using Azure Sentinel may also experience data access issues and delayed or misfired alerts.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 05/15, 13:15 UTC. Our logs show the incident started on 05/15, 12:40 UTC and that during the 35 minutes that it took to resolve the issue, Some of the customers using Log Analytics may have experienced data access issue and delayed or missed alerts in West Europe region. Some customers using Azure Sentinel may also experience data access issues and delayed or misfired alerts.
- Root Cause: The failure was due to backend dependent service becoming unhealthy.
- Incident Timeline: 35 minutes - 05/15, 12:40 UTC through 05/15, 13:15 UTC
-Srikanth