This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Tuesday, 29 March 2022 13:27 UTC
-Deepika
We've confirmed that all systems are back to normal with no customer impact as of 3/29, 12:00 UTC. Our logs show the incident started on 3/28, 08:00 UTC and that during the 28 hours that it took to resolve the issue some customers may have experienced Alerts loss and did not receive customer notification.
- Root Cause: The failure was due to one of our dependent service.
- Incident Timeline: 28 Hours - 3/28, 08:00 UTC through 3/29, 12:00 UTC
-Deepika