%3CLINGO-SUB%20id%3D%22lingo-sub-1424465%22%20slang%3D%22en-US%22%3EExperiencing%20Microsoft.Insights%20Resource%20Provider%20Registration%20issue%20-%2005%2F28%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1424465%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%20Thursday%2C%2028%20May%202020%2019%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%205%2F28%2C%2019%3A26%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%205%2F26%2C%2017%3A41%20UTC%20and%20that%20during%20the%202%20days%2C%201%20hour%2C%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%201.2%25%20of%20customers%20experienced%20an%20inability%20to%20register%20with%20Microsoft.Insights%20resource%20provider%20which%20may%20have%20resulted%20in%20failures%20to%20create%20alerts%20or%20other%20anomalies.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20updated%20backend%20service%20configuration%20problem.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Days%2C%201%20Hour%20%26amp%3B%2045%20minutes%20-%205%2F26%2C%2017%3A41%20UTC%20through%205%2F28%2C%2019%3A26%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-Jeff%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%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%2028%20May%202020%2017%3A12%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20a%20configuration%20issue%20with%20an%20ARM%20update%20which%20was%20impacting%20the%20ability%20of%20subscriptions%20to%20register%20with%20Microsoft.Insights.%20To%20address%20this%20issue%20we%20are%20currently%20implementing%20a%20hotfix.%20The%20issue%20began%20at%2005%2F26%2017%3A41%20UTC.%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%2005%2F28%2019%3A30%20UTC%3C%2FLI%3E%3CLI%3E%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3EMitigation%20ETA%3C%2FSPAN%3E%3A%205%2F28%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jeff%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%3EInitial%20Update%3C%2FU%3E%3A%20Thursday%2C%2028%20May%202020%2017%3A05%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20the%20request%20getting%20stuck%20when%20attempting%20to%20register%20with%20the%20Microsoft.Insights%20resource%20provider.%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%2005%2F28%2019%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jeff%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1424465%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 28 May 2020 19:41 UTC

We've confirmed that all systems are back to normal with no customer impact as of 5/28, 19:26 UTC. Our logs show the incident started on 5/26, 17:41 UTC and that during the 2 days, 1 hour, 45 minutes that it took to resolve the issue 1.2% of customers experienced an inability to register with Microsoft.Insights resource provider which may have resulted in failures to create alerts or other anomalies.
  • Root Cause: The failure was due to an updated backend service configuration problem.
  • Incident Timeline: 2 Days, 1 Hour & 45 minutes - 5/26, 17:41 UTC through 5/28, 19:26 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jeff

Update: Thursday, 28 May 2020 17:12 UTC

Root cause has been isolated to a configuration issue with an ARM update which was impacting the ability of subscriptions to register with Microsoft.Insights. To address this issue we are currently implementing a hotfix. The issue began at 05/26 17:41 UTC.
  • Work Around: None
  • Next Update: Before 05/28 19:30 UTC
  • Mitigation ETA: 5/28 20:00 UTC
-Jeff

Initial Update: Thursday, 28 May 2020 17:05 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience the request getting stuck when attempting to register with the Microsoft.Insights resource provider.
  • Work Around: None
  • Next Update: Before 05/28 19:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff