This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Saturday, 04 January 2020 21:25 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/04, 18:00 UTC. Our logs show the incident started on 01/04, 12:40 UTC and that during the 5 hours and 20 minutes that it took to resolve the issue some customers experienced delay in receiving log search alerts in Australia East region.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 01/04, 18:00 UTC. Our logs show the incident started on 01/04, 12:40 UTC and that during the 5 hours and 20 minutes that it took to resolve the issue some customers experienced delay in receiving log search alerts in Australia East region.
- Root Cause: The failure was due to one of the backend dependent services not being reachable.
- Incident Timeline: 5 Hours & 20 minutes - 01/04, 12:40 UTC through 01/04, 18:00 UTC
-Jayadev
Initial Update: Saturday, 04 January 2020 14:59 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Customers may not be receiving log Alerts at this time.
-Madhuri
We are aware of issues within Log Search Alerts and are actively investigating. Customers may not be receiving log Alerts at this time.
- Work Around:
- Next Update: Before 01/04 17:00 UTC
-Madhuri