This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Saturday, 15 January 2022 12:41 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/15, 12:30 UTC. Our logs show the incident started on 01/15, 07:30 UTC and that during the 5 hours that it took to resolve the issue some customers may have experienced ingestion latency, delayed or misfired alerts and failure performing service management operations in East US region.
-Soumyajeet
We've confirmed that all systems are back to normal with no customer impact as of 01/15, 12:30 UTC. Our logs show the incident started on 01/15, 07:30 UTC and that during the 5 hours that it took to resolve the issue some customers may have experienced ingestion latency, delayed or misfired alerts and failure performing service management operations in East US region.
- Root Cause: The failure was due to a recent configuration change to one of our backend dependency.
- Incident Timeline: 5 Hours - 01/15, 07:30 UTC through 01/15, 12:30 UTC
-Soumyajeet