This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 31 March 2022 07:39 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/31, 06:35 UTC. Our logs show the incident started on 03/31, 06:00 UTC and that during the 35 minutes that it took to resolve the issue, customers experienced issues with accessing your data as well as missed or delayed alerts in South Central US region.
-Deepika
We've confirmed that all systems are back to normal with no customer impact as of 03/31, 06:35 UTC. Our logs show the incident started on 03/31, 06:00 UTC and that during the 35 minutes that it took to resolve the issue, customers experienced issues with accessing your data as well as missed or delayed alerts in South Central US region.
- Root Cause: The failure was due to one of our backend dependency.
- Incident Timeline: 35 minutes - 03/31, 06:00 UTC through 03/31, 06:35 UTC
-Deepika