Experiencing Data Access Issue in Azure portal for Log Analytics - 04/28 - Resolved

Published 04-28-2021 08:13 AM 599 Views
Final Update: Wednesday, 28 April 2021 14:52 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/28, 14:30 UTC. Our logs show the incident started on 04/28, 13:40 UTC and that during the 50 minutes that it took to resolve the issue some customers may have received failure notifications when performing service management operations - such as create, update, delete - for workspaces hosted in all Australia regions. Customers may have also experienced that deletion of automation accounts and linking automation account with workspace may have failed. Performing queries against the workspaces may also have failed. 
  • Root Cause: We determined that a recent deployment task failed to complete causing impact to service management operations for the service.
  • Incident Timeline: 50 minutes - 04/28, 13:40 UTC through 04/28, 14:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Anmol

%3CLINGO-SUB%20id%3D%22lingo-sub-2302485%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2004%2F28%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302485%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%20Wednesday%2C%2028%20April%202021%2014%3A52%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F28%2C%2014%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F28%2C%2013%3A40%20UTC%20and%20that%20during%20the%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20received%20failure%20notifications%20when%20performing%20service%20management%20operations%20-%20such%20as%20create%2C%20update%2C%20delete%20-%20for%20workspaces%20hosted%20in%20all%20Australia%20regions.%20Customers%20may%20have%20also%20experienced%20that%20deletion%20of%20automation%20accounts%20and%20linking%20automation%20account%20with%20workspace%20may%20have%20failed.%20Performing%20queries%20against%20the%20workspaces%20may%20also%20have%20failed.%26nbsp%3B%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20We%20determined%20that%20a%20recent%20deployment%20task%20failed%20to%20complete%20causing%20impact%20to%20service%20management%20operations%20for%20the%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2050%20minutes%20-%2004%2F28%2C%2013%3A40%20UTC%20through%2004%2F28%2C%2014%3A30%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-Anmol%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
Version history
Last update:
‎Apr 28 2021 08:53 AM
Updated by: