Final Update: Thursday, 28 January 2021 10:22 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/28, 10:00 UTC. Our logs show the incident started on 01/28, 08:00 UTC and that during the 2 Hours that it took to resolve the issue some customers may have experienced issues with missed, delayed and wrongly fired Log Search alerts and may have experienced difficulty accessing data for resources hosted in USGov Arizona region.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 01/28, 10:00 UTC. Our logs show the incident started on 01/28, 08:00 UTC and that during the 2 Hours that it took to resolve the issue some customers may have experienced issues with missed, delayed and wrongly fired Log Search alerts and may have experienced difficulty accessing data for resources hosted in USGov Arizona region.
- Root Cause: We identified the issue was caused by a recent deployment task with a incorrect configuration setting.
- Incident Timeline: 2 Hours - 01/28, 08:00 UTC through 01/28, 10:00 UTC
-Anmol
Published Jan 28, 2021
Version 1.0Azure-Monitor-Team
Silver Contributor
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity