%3CLINGO-SUB%20id%3D%22lingo-sub-1686460%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2009%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1686460%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%3EFinal%20Update%3C%2FU%3E%3A%20Saturday%2C%2019%20September%202020%2001%3A13%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22font-family%3A%20%26quot%3BSegoe%20UI%26quot%3B%2C%20system-ui%2C%20%26quot%3BApple%20Color%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Emoji%26quot%3B%2C%20sans-serif%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20for%20our%20USGov%20Virginia%2C%20USGov%20Texas%2C%20USGov%20Arizona%2C%20DoDCentral%2C%20and%20DoDEast%20regions%20of%20the%20US%20Gov%20cloud%20as%20of%209%2F18%2C%2020%3A00%20EDT.%20Our%20logs%20show%20the%20incident%20started%20on%205%2F18%2C%2013%3A00%20EDT%20and%20that%20during%20the%207%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20Diagnostic%20Settings%20to%20export%20logs%20and%20metrics%20to%20Log%20Analytics%20would%20have%20experienced%20data%20loss%2Fgaps%20in%20their%20Log%20Analytics%20workspaces%20during%20this%20time.%20Due%20to%20this%20customers%20may%20have%20also%20experienced%20false%20and%20missed%20alerts.%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20authentication%20issue%20that%20took%20down%20our%20data%20export%20to%20Log%20Analytics.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%207%20Hours%20-%205%2F18%2C%2013%3A00%20EDT%20through%209%2F18%2C%2020%3A00%20EDT%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-Ian%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1686460%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 19 September 2020 01:13 UTC

We've confirmed that all systems are back to normal with no customer impact for our USGov Virginia, USGov Texas, USGov Arizona, DoDCentral, and DoDEast regions of the US Gov cloud as of 9/18, 20:00 EDT. Our logs show the incident started on 5/18, 13:00 EDT and that during the 7 hours that it took to resolve the issue customers using Diagnostic Settings to export logs and metrics to Log Analytics would have experienced data loss/gaps in their Log Analytics workspaces during this time. Due to this customers may have also experienced false and missed alerts.
  • Root Cause: The failure was due to an authentication issue that took down our data export to Log Analytics.
  • Incident Timeline: 7 Hours - 5/18, 13:00 EDT through 9/18, 20:00 EDT
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Ian