This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Monday, 21 March 2022 23:27 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/21, 22:35 UTC. Our logs show the incident started on 3/21, 22:15 UTC and that during the 20 minutes that it took to resolve the issue customers with workspace-enabled Application Insights resources in Australia East may have experienced intermittent log data gaps and incorrect alert activation.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 3/21, 22:35 UTC. Our logs show the incident started on 3/21, 22:15 UTC and that during the 20 minutes that it took to resolve the issue customers with workspace-enabled Application Insights resources in Australia East may have experienced intermittent log data gaps and incorrect alert activation.
- Root Cause: The failure was due to a backend dependency
- Incident Timeline: 20 minutes - 3/21, 22:15 UTC through 3/21, 22:35 UTC
-Eric Singleton