%3CLINGO-SUB%20id%3D%22lingo-sub-1884838%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2011%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1884838%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Friday%2C%2013%20November%202020%2015%3A01%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F13%2C%2014%3A10%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F13%2C%2010%3A30%20UTC%20and%20that%20during%20the%203%20hours%20and%2010%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20some%20customers%20may%20have%20experienced%20intermittent%20data%20latency%20in%20Log%20Analytics%20in%20central%20Australia%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20bad%20configuration%20in%20a%20recent%20build.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2010%20minutes%20-%2011%2F13%2C%2010%3A30%20UTC%20through%2011%2F13%2C%2014%3A10%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Soumyajeet%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%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1884838%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 13 November 2020 15:01 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/13, 14:10 UTC. Our logs show the incident started on 11/13, 10:30 UTC and that during the 3 hours and 10 minutes that it took to resolve the issue, some customers may have experienced intermittent data latency in Log Analytics in central Australia region.
  • Root Cause: The failure was due to a bad configuration in a recent build.
  • Incident Timeline: 3 Hours & 10 minutes - 11/13, 10:30 UTC through 11/13, 14:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Soumyajeet