This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 01 September 2021 21:01 UTC
We've confirmed that all systems are back to normal with no customer impact as of 9/1, 20:15 UTC. Our logs show the incident started on 9/1, 15:00 UTC and that during the five hours that it took to resolve the issue approximately 450 total customers may have experienced delayed activity log alerts.
-Jack Cantwell
We've confirmed that all systems are back to normal with no customer impact as of 9/1, 20:15 UTC. Our logs show the incident started on 9/1, 15:00 UTC and that during the five hours that it took to resolve the issue approximately 450 total customers may have experienced delayed activity log alerts.
- Root Cause: The failure was due to a Backend service responsible for processing activity logs hitting an operational threshold, which caused a delay in the processing of activity logs.
- Incident Timeline: 5 Hours & 15 minutes - 9/1, 15:00 UTC through 9/1, 20:15 UTC
-Jack Cantwell
Initial Update: Wednesday, 01 September 2021 20:05 UTC
We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed or missed Log Search Alerts.
-Jack Cantwell
We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed or missed Log Search Alerts.
- Next Update: Before 09/01 21:30 UTC
-Jack Cantwell