%3CLINGO-SUB%20id%3D%22lingo-sub-353405%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20and%20OMS%20portal%20for%20Log%20Analytics%20-%2002%2F10%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353405%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Feb%2010%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CDIV%3E%0A%20%20%20%3CDIV%3EFinal%20Update%3A%20Sunday%2C%2010%20February%202019%2012%3A24%20UTC%20%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F10%2C%2012%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F10%2C%2011%3A20%20UTC%20and%20that%20during%20the%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20whose%20data%20resides%20in%20South%20East%20Australia%20or%20East%20US%20might%20have%20experienced%20Data%20access%20issues%20in%20the%20Azure%20Portal.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%3CLI%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20systems.%3C%2FLI%3E%0A%20%20%20%20%20%3CLI%3EIncident%20Timeline%3A%2040%20minutes%20-%2001%2F10%2C%2011%3A20%20UTC%20through%2001%2F10%2C%2011%3A20%20UTC%3C%2FLI%3E%0A%20%20%20%20%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20-Varun%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%3C%2FDIV%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-353405%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Feb%2010%2C%202019%20Final%20Update%3A%20Sunday%2C%2010%20February%202019%2012%3A24%20UTCWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F10%2C%2012%3A00%20UTC.%3C%2FLINGO-TEASER%3E
First published on MSDN on Feb 10, 2019
Final Update: Sunday, 10 February 2019 12:24 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/10, 12:00 UTC. Our logs show the incident started on 02/10, 11:20 UTC and that during the 40 minutes that it took to resolve the issue some customers whose data resides in South East Australia or East US might have experienced Data access issues in the Azure Portal.
  • Root Cause: The failure was due to an issue in one of our dependent systems.
  • Incident Timeline: 40 minutes - 01/10, 11:20 UTC through 01/10, 11:20 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Varun