This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Thursday, 03 March 2022 16:57 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/3, 15:00 UTC. Our logs show the incident started on 3/3, 13:05 UTC and that during the 2 hours that it took to resolve the issue, customers using Azure Log Analytics in Australia East may have experienced data access issues as well as delayed or misfired alerts.
-Ian
We've confirmed that all systems are back to normal with no customer impact as of 3/3, 15:00 UTC. Our logs show the incident started on 3/3, 13:05 UTC and that during the 2 hours that it took to resolve the issue, customers using Azure Log Analytics in Australia East may have experienced data access issues as well as delayed or misfired alerts.
- Root Cause: The failure was due to a backend storage resource that became unhealthy.
- Incident Timeline: 1 Hours & 55 minutes - 3/4, 13:05 UTC through 3/3, 15:00 UTC
-Ian
Update: Thursday, 03 March 2022 15:57 UTC
Customers using Azure Log Analytics and Azure Sentinel may experience data access issues as well as missed or delayed log search alerts in Australia East region.
Customers using Azure Log Analytics and Azure Sentinel may experience data access issues as well as missed or delayed log search alerts in Australia East region.
- Work Around: None
- Next Update: Before 03/03 20:00 UTC