Final Update: Tuesday, 28 June 2022 14:18 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/28, 12:53 UTC. Our logs show the incident started on 06/27, 15:43 UTC and that during the 21 hours and 10 minutes that it took to resolve the some of the customers using the IT Service Management (ITSM) connector with Azure Monitor in West Europe may have experienced errors or failure notifications. New alerts may not export to ServiceNow and connections to ServiceNow may fail after creation.
-Soumyajeet
We've confirmed that all systems are back to normal with no customer impact as of 06/28, 12:53 UTC. Our logs show the incident started on 06/27, 15:43 UTC and that during the 21 hours and 10 minutes that it took to resolve the some of the customers using the IT Service Management (ITSM) connector with Azure Monitor in West Europe may have experienced errors or failure notifications. New alerts may not export to ServiceNow and connections to ServiceNow may fail after creation.
- Root Cause: The failure was due to a backend dependency service becoming unhealthy.
- Incident Timeline: 21 Hours & 10 minutes - 06/27, 15:43 UTC through 06/28, 12:53 UTC
-Soumyajeet
Published Jun 28, 2022
Version 1.0
Azure-Monitor-Team
Microsoft
Microsoft
