%3CLINGO-SUB%20id%3D%22lingo-sub-1725213%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20in%20Activity%20Log%20Alerts%20rules%20and%20Activity%20Logs-%2009%2F29%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1725213%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%20Tuesday%2C%2029%20September%202020%2015%3A44%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F29%2C%2013%3A50%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F29%2C%2003%3A30%20UTC%20and%20that%20during%20the%2010%20hours%2020%20Minutes%20that%20it%20took%20to%20resolve%2C%20Some%20customers%20may%20have%20received%20failure%20notifications%20when%20accessing%20or%20performing%20service%20management%20operations%20such%20as%20create%2C%20update%2C%20delete%20for%20Azure%20Activity%20Log%20Alert%20Rules%20and%20have%20issues%20while%20viewing%20Activity%20Logs%20in%20the%20azure%20Portal.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%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%20issue%20with%20Azure%20Active%20Directory%20service.%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2010%20Hours%20%26amp%3B%2020%20minutes%20-%2009%2F29%2C%2003%3A30%20UTC%20through%2009%2F29%2C%2013%3A50%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-Vamshi%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-1725213%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 29 September 2020 15:44 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/29, 13:50 UTC. Our logs show the incident started on 09/29, 03:30 UTC and that during the 10 hours 20 Minutes that it took to resolve, Some customers may have received failure notifications when accessing or performing service management operations such as create, update, delete for Azure Activity Log Alert Rules and have issues while viewing Activity Logs in the azure Portal.

  • Root Cause: The failure was due to issue with Azure Active Directory service. 
  • Incident Timeline: 10 Hours & 20 minutes - 09/29, 03:30 UTC through 09/29, 13:50 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Vamshi