This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 05 March 2020 08:57 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/05, 08:30 UTC. Our logs show the incident started on 03/05, 07:30 UTC and that during the 1 hour that it took to resolve the issue some of customers may have experienced missed or delayed alerts in North Central US Region.
-Satya
We've confirmed that all systems are back to normal with no customer impact as of 03/05, 08:30 UTC. Our logs show the incident started on 03/05, 07:30 UTC and that during the 1 hour that it took to resolve the issue some of customers may have experienced missed or delayed alerts in North Central US Region.
- Root Cause: The failure was due to one of the back end services.
- Incident Timeline: 1 Hour - 03/05, 07:30 UTC through 03/05, 08:30 UTC
-Satya