This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 10 January 2020 01:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/09, 23:40 UTC. Our logs show the incident started on 01/09, 23:10 UTC and that during the 30 minutes that it took to resolve the issue customers in West US2 Region may have experienced issues with data access in Azure portal, Query failures for Log Analytics and delayed or missed alerts in Log Search Alerts.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 01/09, 23:40 UTC. Our logs show the incident started on 01/09, 23:10 UTC and that during the 30 minutes that it took to resolve the issue customers in West US2 Region may have experienced issues with data access in Azure portal, Query failures for Log Analytics and delayed or missed alerts in Log Search Alerts.
- Root Cause: The failure was due to one of the backend services.
- Incident Timeline: 30 minutes - 01/09, 23:10 UTC through 01/09, 23:40 UTC
-Jayadev
Initial Update: Thursday, 09 January 2020 23:52 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in West US2 may experience issues with data access from Azure portal and query failures in Azure Log Analytics.
-Jayadev
We are aware of issues within Log Analytics and are actively investigating. Some customers in West US2 may experience issues with data access from Azure portal and query failures in Azure Log Analytics.
- Next Update: Before 01/10 04:00 UTC
-Jayadev