%3CLINGO-SUB%20id%3D%22lingo-sub-1518452%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2007%2F13%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1518452%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Monday%2C%2013%20July%202020%2016%3A34%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Azure%20Monitoring.%20Some%20customers%20who%20are%20using%20ITSM%20connector%20may%20continue%20to%20experience%20missing%20alerts%20in%20a%20partner%20solution%2C%20for%20example%20ServiceNow.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F12%20~08%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20In%20the%20meantime%2C%20there%20is%20a%20workaround%20available%20to%20you%20if%20you%20follow%20the%20steps%20outlined.%20Please%20note%20these%20steps%20will%20work%20for%20other%20partner%20applications%20as%20well.%26nbsp%3B-ERR%3AREF-NOT-FOUND-%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fplatform%2Fitsmc-resync-servicenow%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fplatform%2Fitsmc-resync-servicenow%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F14%2011%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Sindhu%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3A%20Monday%2C%2013%20July%202020%2012%3A58%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Azure%20Monitoring.%20Some%20customers%20who%20are%20using%20ITSM%20connector%20continue%20to%20experiencing%20missing%20alerts%20in%20a%20partner%20solution%2C%20for%20example%20ServiceNow.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F12%20~08%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20%26nbsp%3BIn%20the%20meantime%2C%20there%20is%20a%20workaround%20available%20to%20you%20if%20you%20follow%20the%20steps%20outlined.%20Please%20note%20these%20steps%20will%20work%20for%20other%20partner%20applications%20as%20well.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fplatform%2Fitsmc-resync-servicenow%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Fplatform%2Fitsmc-resync-servicenow%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F13%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Anmol%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2013%20July%202020%2010%3A53%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Azure%20Monitoring%20and%20are%20actively%20investigating.%20Some%20customers%20who%20are%20using%20ITSM%20connector%20may%20be%20experiencing%20missing%20alerts%20in%20a%20partner%20solution%20(Example%3A%20service%20now).%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F13%2013%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anmol%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1518452%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 15 July 2020 13:52 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/15, 13:13 UTC. Our logs show the incident started on 07/12, 08:00 UTC and that during the 3 Days 5 hours and 13 Minutes that it took to resolve the issue. Some customers who are using ITSM connector may have experienced missing alerts in a partner solution, for example ServiceNow. 
If you continue to experience issues, we recommend following the steps as mentioned on https://aka.ms/d_ZTKY-F80.
  • Root Cause: We determined that a recent configuration regression resulted in the calls being sent from ITSM to be unable to complete.
  • Incident Timeline: 3 Days 5 Hours & 13 Minutes - 07/12, 08:00 UTC through 07/15, 13:13 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Anmol

Update: Tuesday, 14 July 2020 20:52 UTC

We continue to investigate issues within Azure Monitoring. Some customers who are using ITSM connector may continue to experience missing alerts in a partner solution, for example ServiceNow. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/12 ~08:00 UTC. We currently have no estimate for resolution.
  • Next Update: Before 07/15 21:00 UTC
-Sindhu

Update: Tuesday, 14 July 2020 09:19 UTC

We continue to investigate issues within Azure Monitoring. Some customers who are using ITSM connector may continue to experience missing alerts in a partner solution, for example ServiceNow. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/12 ~08:00 UTC. We currently have no estimate for resolution.
-Anmol

Update: Monday, 13 July 2020 16:34 UTC

We continue to investigate issues within Azure Monitoring. Some customers who are using ITSM connector may continue to experience missing alerts in a partner solution, for example ServiceNow. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/12 ~08:00 UTC. We currently have no estimate for resolution.
-Sindhu

Update: Monday, 13 July 2020 12:58 UTC

We continue to investigate issues within Azure Monitoring. Some customers who are using ITSM connector continue to experiencing missing alerts in a partner solution, for example ServiceNow. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/12 ~08:00 UTC. We currently have no estimate for resolution.
  • Next Update: Before 07/13 17:00 UTC
-Anmol

Initial Update: Monday, 13 July 2020 10:53 UTC

We are aware of issues within Azure Monitoring and are actively investigating. Some customers who are using ITSM connector may be experiencing missing alerts in a partner solution (Example: service now).
  • Work Around: None
  • Next Update: Before 07/13 13:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol