%3CLINGO-SUB%20id%3D%22lingo-sub-1209573%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2003%2F04%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1209573%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%20Friday%2C%2006%20March%202020%2021%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F06%2C%2020%3A18%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F26%2C%2020%3A00%20UTC%20and%20that%20during%20the%209%20days%2010%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20might%20have%26nbsp%3Bexperienced%20issues%20accessing%20metrics%20data%20after%20renaming%20or%20creating%20new%20AI%20resources.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%209%20days%20%26amp%3B%2018%20minutes%20-%2002%2F26%2C%2020%3A00%20UTC%20through%2003%2F06%2C%2020%3A18%20UTC%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-Sindhu%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2006%20March%202020%2001%3A44%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%20font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3ERoot%20cause%20has%20been%20isolated%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%20Engineers%20are%20currently%20working%20on%20mitigating%20the%20issue.%20Some%20customers%20may%20experience%20issues%20accessing%20metrics%20data%20after%20renaming%20or%20creating%20new%20AI%20resources.%20A%20fix%20has%20been%20deployed%20to%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3ESoutheast%20Asia%2C%20North%20Europe%2C%20East%20Asia%2C%20West%20Europe%20and%20West%20US%202%20regions%20where%20the%20issue%20is%20mitigated.%20It%20will%20be%20deployed%20to%20rest%20of%20the%20regions%20within%2024%20hours.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F07%2002%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Sindhu%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%20Thursday%2C%2005%20March%202020%2005%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3ERoot%20cause%20has%20been%20isolated%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%20Engineers%20are%20currently%20working%20on%20mitigating%20the%20issue.%20Some%20customers%20may%20experience%20issues%20accessing%20metrics%20data%20after%20renaming%20or%20creating%20new%20AI%20resources.%3C%2FDIV%3E%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%2003%2F06%2006%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Satya%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%20Thursday%2C%2005%20March%202020%2000%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Some%20customers%20continue%20to%20experience%20issues%20accessing%20metrics%20data%20after%20renaming%20or%20creating%20new%20AI%20resources.%20Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2002%2F26%20~20%3A00%20UTC.%26nbsp%3B%20We%20are%20still%20investigating%20and%20currently%20have%20no%20estimate%20for%20resolution.%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%2003%2F05%2005%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Sindhu%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%3CDIV%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2004%20March%202020%2020%3A32%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Some%20customers%20continue%20to%20experience%20issues%20accessing%20metrics%20data%20after%20renaming%20or%20creating%20new%20AI%20resources.%20Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2002%2F26%20~20%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FDIV%3E%3CDIV%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%2003%2F05%2001%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Sindhu%3C%2FDIV%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2004%20March%202020%2018%3A18%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issues%20accessing%20metrics%20data%20after%20renaming%20or%20creating%20new%20AI%20resources.%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F04%2022%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.-Sindhu%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1209573%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 06 March 2020 21:38 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/06, 20:18 UTC. Our logs show the incident started on 02/26, 20:00 UTC and that during the 9 days 10 minutes that it took to resolve the issue some customers might have experienced issues accessing metrics data after renaming or creating new AI resources.
  • Root Cause: The failure was due to issue in one of our dependent services.
  • Incident Timeline: 9 days & 18 minutes - 02/26, 20:00 UTC through 03/06, 20:18 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Sindhu

Update: Friday, 06 March 2020 01:44 UTC

Root cause has been isolated to an issue in one of our dependent services. Engineers are currently working on mitigating the issue. Some customers may experience issues accessing metrics data after renaming or creating new AI resources. A fix has been deployed to Southeast Asia, North Europe, East Asia, West Europe and West US 2 regions where the issue is mitigated. It will be deployed to rest of the regions within 24 hours.  

  • Work Around: None
  • Next Update: Before 03/07 02:00 UTC
-Sindhu

Update: Thursday, 05 March 2020 05:41 UTC

Root cause has been isolated to an issue in one of our dependent services. Engineers are currently working on mitigating the issue. Some customers may experience issues accessing metrics data after renaming or creating new AI resources.

  • Work Around: None
  • Next Update: Before 03/06 06:00 UTC
-Satya

Update: Thursday, 05 March 2020 00:51 UTC

We continue to investigate issues within Application Insights. Some customers continue to experience issues accessing metrics data after renaming or creating new AI resources. Initial findings indicate that the problem began at 02/26 ~20:00 UTC.  We are still investigating and currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 03/05 05:00 UTC
-Sindhu

Update: Wednesday, 04 March 2020 20:32 UTC

We continue to investigate issues within Application Insights. Some customers continue to experience issues accessing metrics data after renaming or creating new AI resources. Initial findings indicate that the problem began at 02/26 ~20:00 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 03/05 01:00 UTC
-Sindhu

Initial Update: Wednesday, 04 March 2020 18:18 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience issues accessing metrics data after renaming or creating new AI resources. 
  • Work Around: None 
  • Next Update: Before 03/04 22:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sindhu