Experiencing Data Access Issue in Azure portal in multiple regions- 04/22 - Resolved

Published Apr 22 2020 05:15 AM 1,907 Views
Final Update: Wednesday, 22 April 2020 13:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 4/22, 13:45 UTC. Our logs show the incident started on 4/22, 09:55 UTC and that during the 3 hours and 50 minutes that it took to resolve the issue customers using Log Analytics, Log Search Alerts and/or Metric Alerts may have experienced Data Latency, Delayed or missed log search alerts and issue performing CRUD operations against Log Analytics Workspace and Query failure issues in East US 2, North Europe, East Australia, West US, Central US, South Central US and North Central US regions. 
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 3 Hours & 50 minutes - 4/22, 09:55 UTC through 4/22, 13:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Madhuri

Initial Update: Wednesday, 22 April 2020 12:13 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Data Latency, Delayed or missed log search alerts and issue performing CRUD operations against Log Analytics Workspace and Query failure issues in multiple regions.
  • Work Around: None
  • Next Update: Before 04/22 14:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Madhuri

%3CLINGO-SUB%20id%3D%22lingo-sub-1328472%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20in%20multiple%20regions-%2004%2F22%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1328472%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%20Wednesday%2C%2022%20April%202020%2013%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%204%2F22%2C%2013%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%204%2F22%2C%2009%3A55%20UTC%20and%20that%20during%20the%203%20hours%20and%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20Log%20Analytics%2C%20Log%20Search%20Alerts%20and%2For%20Metric%20Alerts%20may%20have%20experienced%20Data%20Latency%2C%20Delayed%20or%20missed%20log%20search%20alerts%20and%20issue%20performing%20CRUD%20operations%20against%20Log%20Analytics%20Workspace%20and%20Query%20failure%20issues%20in%20East%20US%202%2C%20North%20Europe%2C%20East%20Australia%2C%20West%20US%2C%20Central%20US%2C%20South%20Central%20US%20and%20North%20Central%20US%20regions.%26nbsp%3B%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2050%20minutes%20-%204%2F22%2C%2009%3A55%20UTC%20through%204%2F22%2C%2013%3A45%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-Madhuri%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%20Wednesday%2C%2022%20April%202020%2012%3A13%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%26nbsp%3BData%20Latency%2C%20Delayed%20or%20missed%20log%20search%20alerts%20and%20issue%20performing%20CRUD%20operations%20against%20Log%20Analytics%20Workspace%20and%20Query%20failure%20issues%20in%20multiple%20regions.%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%2004%2F22%2014%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Madhuri%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-1328472%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EService%20Map%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Apr 22 2020 07:06 AM
Updated by: