This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Monday, 13 June 2022 04:43 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/13, 03:58 UTC. Our logs show the incident started on 06/13, 03:14 UTC and that during the 44 minutes that it took to resolve the issue some of customers might have experienced issues accessing your data as well as missed or delayed alerts .Some customers using Azure Sentinel may also have experienced data access issues and delayed or misfired alerts in UK South region.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 06/13, 03:58 UTC. Our logs show the incident started on 06/13, 03:14 UTC and that during the 44 minutes that it took to resolve the issue some of customers might have experienced issues accessing your data as well as missed or delayed alerts .Some customers using Azure Sentinel may also have experienced data access issues and delayed or misfired alerts in UK South region.
- Root Cause: The failure was due to backend dependency.
- Incident Timeline: 44 minutes - 06/13, 03:14 UTC through 06/13, 03:58 UTC.
-Srikanth