Home
%3CLINGO-SUB%20id%3D%22lingo-sub-664618%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2006%2F03%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-664618%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%20Monday%2C%2003%20June%202019%2013%3A40%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F03%2C%2012%3A40%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F03%2C%2010%3A40%20UTC%20and%20that%20during%20the%202%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20a%20few%20customers%20would%20have%20experienced%20issues%20while%20creating%20new%20custom%20logs%20in%20France%20Central%20location.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20authentication%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20-%2006%2F03%2C%2010%3A40%20UTC%20through%2006%2F03%2C%2012%3A40%20UTC%3CBR%20%2F%3E%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-Varun%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%2003%20June%202019%2012%3A40%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20France%20Central%20may%20experience%20issues%20while%20accessing%20their%20data%20in%20the%20Azure%20Portal.%3CBR%20%2F%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%2006%2F03%2014%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Varun%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-664618%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 03 June 2019 13:40 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/03, 12:40 UTC. Our logs show the incident started on 06/03, 10:40 UTC and that during the 2 hours that it took to resolve the issue a few customers would have experienced issues while creating new custom logs in France Central location.
  • Root Cause: The failure was due to an authentication issue in one of our dependent services.
  • Incident Timeline: 2 Hours - 06/03, 10:40 UTC through 06/03, 12:40 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Varun

Initial Update: Monday, 03 June 2019 12:40 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in France Central may experience issues while accessing their data in the Azure Portal.
  • Work Around: None
  • Next Update: Before 06/03 14:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Varun