%3CLINGO-SUB%20id%3D%22lingo-sub-1807496%22%20slang%3D%22en-US%22%3EExperienced%20Management%20Operation%20failures%20for%20Activity%20Log%20Alert%20Rules%20-%2010%2F22%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1807496%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Thursday%2C%2022%20October%202020%2009%3A24%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F22%2C%2008%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F22%2C%2001%3A30%20UTC%26nbsp%3Band%20that%20during%20the%207%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20failure%20notifications%20when%20accessing%20or%20performing%20service%20management%20operations%20for%20Azure%20Activity%20Log%20Alert%20Rules.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20our%20dependent%20services.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%207%20Hours%20-%2010%2F22%2C%2001%3A30%20UTC%26nbsp%3Bthrough%2010%2F22%2C%2008%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Activity%20Log%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Sandeep%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1807496%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 22 October 2020 09:24 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/22, 08:30 UTC. Our logs show the incident started on 10/22, 01:30 UTC and that during the 7 hours that it took to resolve the issue some customers may have experienced failure notifications when accessing or performing service management operations for Azure Activity Log Alert Rules.
  • Root Cause: The failure was due to issues with one of our dependent services.  
  • Incident Timeline: 7 Hours - 10/22, 01:30 UTC through 10/22, 08:30 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Sandeep