%3CLINGO-SUB%20id%3D%22lingo-sub-2049954%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2001%2F11%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2049954%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%20Monday%2C%2011%20January%202021%2019%3A50%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F11%2C%2018%3A47%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F08%2C%2003%3A16%20UTC%20and%20that%20duration%20of%20incident%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20only%20254%20subs%20of%20customers%20experienced%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Edata%20access%20issue.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%26nbsp%3B%3CSPAN%20style%3D%22font-size%3A%2014.6667px%3B%22%3Erecent%20deployment%2C%20which%20introduced%20a%20configuration%20error%3C%2FSPAN%3E%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Econtaining%20a%20new%20App%20ID%20responsible%20for%20accessing%20data%26nbsp%3B%3C%2FSPAN%3Ewhich%20was%20impacting%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Eperformance%20tab%20in%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3EAzure%20Monitor%20for%20Virtual%20Machines.%26nbsp%3B%3C%2FSPAN%3ETo%20address%20this%20issue%20a%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3E%26nbsp%3Bdependent%20service%20preauthorization%20was%20required%20for%20the%20new%20App%20ID%20that%20was%20introduced%20in%20configs%20which%20successfully%20allowed%20the%20process%20of%20these%20data%20access%20requests%2C%20mitigated%20the%20issue.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2001%2F08%2C%2003%3A16%26nbsp%3BUTC%20through%2001%2F11%2C%2018%3A47%26nbsp%3BUTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Arish%20B%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%3EUpdate%3C%2FU%3E%3A%20Monday%2C%2011%20January%202021%2019%3A22%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20be%20a%26nbsp%3B%3CSPAN%20style%3D%22font-size%3A14.6667px%3B%22%3Erecent%20deployment%2C%20which%20introduced%20a%20configuration%20error%3C%2FSPAN%3E%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3Econtaining%20a%20new%20App%20ID%20responsible%20for%20accessing%20data%26nbsp%3B%3C%2FSPAN%3Ewhich%20was%20impacting%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Eperformance%20tab%20in%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3EAzure%20Monitor%20for%20Virtual%20Machines%3C%2FSPAN%3E.%20To%20address%20this%20issue%20a%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3E%26nbsp%3Bdependent%20service%20preauthorization%20was%20required%20for%20the%20new%20App%20ID%20that%20was%20introduced%20which%20successfully%20allowed%20the%20process%20of%20these%20data%20requests%2C%20mitigating%20the%20issue.%3C%2FSPAN%3E.%26nbsp%3B%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Eperformance%20tab%20in%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3EAzure%20Monitor%20for%20Virtual%20Machines%3C%2FSPAN%3E%26nbsp%3Bis%20now%20working%20as%20expected.%20Some%20customers%20may%20experience%20residual%20affect%20and%20we%20estimate%20less%20than%2015%20minutes%20before%20all%20residual%20impact%20statement%20is%20addressed.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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%2001%2F11%2020%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Arish%20B%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%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2011%20January%202021%2018%3A20%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3EAzure%20Log%20Analytics%3C%2FSPAN%3E%26nbsp%3B(%20Virtual%20Machine%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3Einsights%3C%2FSPAN%3E)%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20Data%20Access%20issues.%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3EThe%20performance%20tab%20in%20%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3EAzure%20Monitor%20for%20Virtual%20Machines%20is%20returning%20an%20error%20in%20all%20public%20regions.%20Preliminary%20investigations%20point%20to%20a%20service%20component%20authentication%20issue.%3C%2FSPAN%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20or%3D%22%22%20details%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F11%2020%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Arish%20B%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2049954%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 11 January 2021 19:50 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/11, 18:47 UTC. Our logs show the incident started on 01/08, 03:16 UTC and that duration of incident hours that it took to resolve the issue only 254 subs of customers experienced data access issue.
  • Root Cause: The failure was due to a recent deployment, which introduced a configuration error containing a new App ID responsible for accessing data which was impacting performance tab in Azure Monitor for Virtual Machines. To address this issue a dependent service preauthorization was required for the new App ID that was introduced in configs which successfully allowed the process of these data access requests, mitigated the issue.
  • Incident Timeline: 01/08, 03:16 UTC through 01/11, 18:47 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Arish B

Update: Monday, 11 January 2021 19:22 UTC

Root cause has been isolated to be a recent deployment, which introduced a configuration error containing a new App ID responsible for accessing data which was impacting performance tab in Azure Monitor for Virtual Machines. To address this issue a dependent service preauthorization was required for the new App ID that was introduced which successfully allowed the process of these data requests, mitigating the issue..  performance tab in Azure Monitor for Virtual Machines is now working as expected. Some customers may experience residual affect and we estimate less than 15 minutes before all residual impact statement is addressed.
  • Work Around: None
  • Next Update: Before 01/11 20:30 UTC
-Arish B

Initial Update: Monday, 11 January 2021 18:20 UTC

We are aware of issues within Azure Log Analytics ( Virtual Machine insights) and are actively investigating. Some customers may experience Data Access issues. The performance tab in Azure Monitor for Virtual Machines is returning an error in all public regions. Preliminary investigations point to a service component authentication issue.
  • Work Around:
  • Next Update: Before 01/11 20:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Arish B