%3CLINGO-SUB%20id%3D%22lingo-sub-1061979%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2012%2F12%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1061979%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%20Thursday%2C%2012%20December%202019%2008%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2012%2F12%2C%2008%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F12%2C%2007%3A55%20UTC%20and%20that%20during%20the%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2039%25%20of%20customers%20in%20South%20East%20Australia%20Region%20experienced%20data%20access%20issue%20in%20the%20azure%20portal%20and%20queries%20from%20API%20may%20have%20failed.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B%2035%20minutes%20-%2012%2F12%2C%2007%3A55%20UTC%20through%2012%2F12%2C%2008%3A30%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-Monish%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%3CLINGO-LABS%20id%3D%22lingo-labs-1061979%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 12 December 2019 08:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/12, 08:30 UTC. Our logs show the incident started on 12/12, 07:55 UTC and that during the 35 minutes that it took to resolve the issue 39% of customers in South East Australia Region experienced data access issue in the azure portal and queries from API may have failed.
  • Root Cause: The failure was due to an issue with one of our dependent service.
  • Incident Timeline:  35 minutes - 12/12, 07:55 UTC through 12/12, 08:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Monish